Last edited 3 weeks ago
by Anna Lionetti

Integration with third parties

Revision as of 08:02, 18 November 2024 by Anna Lionetti (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)


Background and overview

The global library community is exploring what will replace MARC-based copy cataloging as the cataloging paradigm of the future. While BIBFRAME stands as the most likely replacement for MARC today, this change challenges many existing library practices and interconnections. The LOD Platform technology implemented by the Share Family of initiatives is experimenting with new strategies to improve interoperability to bridge the gap between traditional cataloging workflows and emerging, collaborative entity management practices.

The evolution of the LOD Platform technology encompasses the ability to mutually integrate the data produced with external systems, notably with local ILS and Library Service Platforms and authority sources. New data workflows are being analysed to support this use of the LOD Platform, whereby its linked data ecosystem can simultaneously operate on its centralised knowledge base as well as on local library systems using libraries’ own tools, and share and cooperatively edit linked data resources across different environments using the JCricket entity editor and LOD Platform APIs.

This is being achieved through the integration of the LOD Platform tools with local ILS and LSP, or cataloguing modules:

  • Alma: connection to circulation processes established; exploration of CRUD APIs together with Alma libraries is in course;
  • FOLIO: pilot integration in progress with Lehigh University (Share-VDE member and FOLIO adopter); initial tests are completed for the automated data flow from JCricket into FOLIO’s Inventory module;
  • Sinopia LD4P BIBFRAME cataloguing module: connection to Sinopia and parsing of Sinopia-generated data has been completed; after the testing phase, Sinopia data will be included in the LOD Platform CKB - Cluster Knowledge Base.

This initiative aims to facilitate a hybrid cataloging environment that retains support for existing MARC-based integrations while developing the flexibility and interconnectedness offered by Share Family-maintained entities. By automating this process, this integration project not only enhances the metadata management capabilities of libraries but also paves the way for seamless collaborative cataloging within the Share Family community.

JCricket and FOLIO Inventory use case

JCricket is the Linked Data Entity Editor developed by the Share Family community, a tool designed for collaboratively curating entity data living in the CKB - Cluster Knowledge Base, the database of linked data entities. Conceived as a live source of authoritative data, JCricket opens new forms of cooperation: through JCricket editor, member institutions engage in collaborative entity management and in a new way of performing authority control. Entity editing and curation capabilities are designed to support both manual as well as machine-to-machine workflows, not only for sharing entities’ data, but also to perform original cataloging.

The solution to connect JCricket and FOLIO Inventory module offers a dual-pathway approach, allowing different records to maintain their own source of truth in FOLIO LSP’s Inventory app, thereby supporting a gradual transition towards a linked data ecosystem.

The larger vision is to create a combined solution that will support a number of different approaches to bibliographic description, from conventional MARC-based copy-cataloging and authority control flows all the way to shared entity management, and to provide migration paths and alternatives to allow different libraries to adapt the technologies to support local needs while still working in a shared space.

The technical strategy under development to connect JCricket and FOLIO Inventory module has already achieved early results with several steps being piloted:

  • the LOD Platform deduplicates, groups, clusters, and merges data contributed by participant institutions and produces a uniform, enriched, linked, and integrated Cluster Knowledge Base (CKB);
  • the entire JCricket curation feature is exposed through a documented set of APIs that external systems like FOLIO can use to embed these capabilities;
  • JCricket users manage entities within the Cluster Knowledge Base and automatically synchronize instances in the Inventory module, enhancing data efficiency and consistency.
Integrations 1729264793035.png

The output of this integration will be available in real time in a bi-directional workflow:

  • from the LOD Platform to FOLIO (in piloting phase);
  • from FOLIO to the LOD Platform (to be developed).
Integrations 1729264956711.png

As a result, an integrated ecosystem is offered that supports linked data entity curation and sharing in the Share Family common space, allowing at the same time autonomous bibliographic descriptions at local library level through FOLIO LSP that benefit from the enrichment provided by Share Family Cluster Knowledge Base.

References

This integration scenarios have been presented in several conferences and events: