2025-06-03 FOLIO Implementers Meeting Notes

Date

Jun 3, 2025

Agenda

Housekeeping (5-min.)
Linked Open Data SIG overview and discussion

Homework and Pre-Reads

Useful Resources

Recording

NOTE: IMPLEMENTERS SIG USES ZOOM’S AI NOTES FUNCTIONALITY. If you would prefer that we turn this off for any session you attend, we are happy to! Please alert the convener at the start of the meeting.

Link to Recording:

Attendees

Please add yourself here! @Darsi Rueda @Tara Barnett @Laura E Daniels @Andreas Mace @Maura Byrne @Kate Deibel @Jean Pajerek @Kalli Mathios @Tiziana Possemato @Charlotte Whitt @Bodil Wennerlund @kriolofs @Magda Fathy Gad Jesse Randolph @Marie Widigson @Olga Kalachinskaya @Ray Murray @Thomas Trutt

Notes

Time	Topic	Notes

Time

Topic

Notes

Housekeeping

PCOM is live on FOLIO as of today!

Linked Open Data SIG update

Laura Daniels, Kalli Mathias, Charlotte Whitt, Tiziana Possemato

Laura
slides:

Started as Entity Management Group. Advancing linked data for description, with flexibility for various workflows, storage options, where is source of truth, etc.

MARC is text string based and only used by libraries. URIs and their preferred labels are significant.

Current work is focused on BIBFRAME Works and Instances. BF instance is NOT equivalent to a FOLIO instance. They are not just the Linked Data App. They are about editing LD sure, but also storing and caching data, mapping to and from FOLIO instance, workflows both individual and automated/batch, and Discovery

Beta version of Linked Data Editor in Sunflower. It will generate MARC from the LD when you edit the LD, but then MARC will not be editable. The instance mapping is still done from the MARC. Instance source becomes “Linked Data” (or Libris/Sinopia/JCricket)

Top priority Jira is to have link to source URI in the FOLIO Inventory instance (will come with Trillium). Not editable; populated when record created from the BF. Has a single value constraint (two instances cannot have same URI; and instance can only have one of these)

Andreas
slides:

Work at NL of Sweden. Want to create data in Libris, accessible from FOLIO instance. Want to sometimes cache, but have the possibility of not. Working toward removing double-work that is happening because of MARC and LD both in play. Tracking updates done in Libris so FOLIO instance can be updated from the Linked Data. LD not stored locally in FOLIO. Sinopia and ShareVDE working on similar integrations. NLS won’t be storing MARC in FOLIO at all. This is a good model to support cooperative/shared bibliographic description.

Discovery is almost always currently based on MARC. They want to start addressing this. Some combination of data coming from Instance and Work if not from the LD directly. Should explore an export that is just a general JSON export that combines MARC/LD/instance/Work data as needed to then index for discovery.

Once mapped to MARC, the ability to link relationships is lost (flattened). Cannot map back from MARC to LD.

Bodil: fun fact: Swedish libraries went live with the BIBFRAME-based based cataloquing client exactly 7 yrs ago. By now, most Swedish librarians have lost their understanding of, and feeling for, Marc. I think...

PC Update by @Charlotte Whitt