...
| Sinopia/FOLIO integration | Sinopia - A linked data editor developed by LD4P. Sinopia is an open source tool designed to encourage creation of linked data. help.sinopia.io or stage.sinopia.io. Sinopia has been live for 2 years. Sinopia creates metadata in RDF. It is however, not connected to ILS or Discovery Systems. They would like to make those connections. First, they would like to integrate Sinopia with an ILS. At Stanford they are working on developing a connection with Sinopia and Symphony. Middleware - Extract, transform, load. Developing a tool called Apache Airflow is being built to manage the different institutional integration workflows to FOLIO and other ILSs: https: airflow.apache.org. This is intended to work with FOLIO's Inventory. This will support multiple ILSs in a single workflow. Sinopia + FOLIO = "Sinolio" - FOLIO does not now have a linked data editor. Cornell is partnering with Stanford to do this. This is a proof-of-concept. This is an API integration, not a FOLIO module. Manual transfer - one description at a time - not bactch processes. They have started working on the Middleware. They use Airflow in another project at Stanford. Trying to build out a system that is very flexible and tailor workflows from Sinopia into their system. No FOLIO resources are being used. Mellon grant money is being used. Airflow gives a graphic user interface of the workflow. They will be adding in email notifications. Sinolio progress - Will have something to show by October 15. bit.ly/sinolioboard to check progress (need a Github account to see)
_________________ They would be willing to give an update in October. Ann-Marie: "I love the idea of having the editing tool for RDF as an external, but easily synchronized, application. It makes my head spin to think about having metadata editors for umpteen types of bib metadata in FOLIO" Jeremy: right now Sinopia supports RDF, but could be extensible. Christie: How do we do this in a ecosystem where this is one source of data. Not everything will have a representation in Sinopia, and not have MARC for some resources. How does that co-exist? How does VuFind know the difference between MARC. How are these integrated, or communicated? That is a practical challenges in thinking about this. Michelle believes that having examples will help answer some of Christie's questions. Charlotte commented that this work is great since FOLIO is intended NOT to be MARC-centric
Ann-Marie (via chat) - "One of the key things (I think) is articulating the requirement -- we have bib metadata in multiple formats that needs to be communicated to our discovery systems. And once that is articulated clearly, then the "how" and the details become part of design and development" Christie (via chat) - "I was thinking about that Ann-Marie and if there is no source record stored in FOLIO, then does the source = FOLIO or does the source = Sinopia / Sinolio? Maybe that depends on where and how the data that is created in Sinopia is stored. It could be stored in FOLIO and then sent back to Sinopia for editing. There could be many potential models for how the data flows." Jeremy will follow up with Charlotte- interested in getting from FOLIO back to Sinopia. Felix: "Answer to Q2: GBV, a library network in Germany has connected their union catalog to Inventory as record source (instances, holdings, and items). It's using PICA+ as internal and Pica3 as cataloging format." "Q1: Transformations are done using XSL transformations and then the Inventory XML records are converted to JSON." Michelle: Is there a model for MARC to FOLIO mapping? Ann-Marie: Felix (via chat) - @Christie a long time ago there was a proposal to split the "source" field into 2 fields: Nancy Lorimer - Would it make sense to take the mapping we have now and try to use it for the Sinopia to FOLIO mapping. Laura shares everyone's enthusiasm. What other FOLIO groups would be interested?
| |||||||||||||||||||||||||||||||||||||
| PC update | Discussion on agenda setting. Laura sets the agenda based on input from the group, particularly from the various product owners. Anyone can reach out to Laura at any time if they have an agenda item they would like to discuss. Discussion in meeting about open vs. closed SLACK channels. | |||||||||||||||||||||||||||||||||||||
| Other updates/announcements | In case you missed it: Call Number Browse Use Cases (please add to this list) We may have a PC liaison. Name to be announced. Use cases for call number browse - Magda is looking for use cases. | |||||||||||||||||||||||||||||||||||||
| Default MARC-Instance mapping for Identifiers | Ann-Marie Breaux (Deactivated) |
Add MARC-Instance field mapping for New identifier types Ann-Marie does not see many examples of 024$c$d$q$2 For mappings default, should these all be included. Ann-Marie recommends that the $q is retained. Others? - Nancy - Would also only consider keeping the $q. | ||||||||||||||||||||||||||||||||||||
| Deriving MARC bibliographic records in FOLIO – use cases (if time allows) | discussion/demo Cornell's primary use case: Thesis records being created. Sometimes Proquest records are not obtained and the records have to be created locally. They created templates in FOLIO. Elements in template demoed:
|
Regular Attendees
(alphabetical by first name)
...