Questions submitted to date:
- What is the scope of the MARCeditor app that @Cult will be building?
Answer: This is more than a MARC editor. It is a cataloging module.
- One specific question related to this: will the work include loaders and mapping tables that allow you to load an external MARC file, act on it (with a template or default edits) and then have that file do other things besides create MARC records (e.g. create holdings or items automatically)?
Answer: Yes. In the left section of the screenshot below you can see the plans to have a tool for import and connecting metadata. There are plans to create a flow that will check for duplicates within the system. There are also planned tools to provide a tool to export data.
"So, it sounds like the cataloging module will have a separate import/export loader from the batch import that Charlotte and the Inventory Team is working on? Could you describe the relationship between the two?" – Christie, Natascha, et all
"Good question. It seems like we would end up with lots of complexity if MARC files would need to be imported to both the Inventory app and the Cataloging app. Are MARC files maybe imported to Cataloging and then somehow flow up to Inventory?" – Ann-Marie Breaux
- Will the work include CRUD for authority records?
Answer: Yes. The module already manages authority records.
- What will the development process look like? Is the thinking that there will be an alpha version; beta version; etc. & what is the projected timeline? How can the MM SIG be involved in the development process?
Answer: @Cult is following 2 routes: Working with the National Library of Hungary as well as FOLIO. They hope to follow the timeline of FOLIO. The National Library of Hungary would like to release the first version of their system at the end of 2018. Step 2 of that timeline, the end of 2019. They are meeting with the National Library of Hungary to solidify the requirements for each deadline. In February they will have a clearer picture of their timeline. If they do not get the contract with teh National Library of Hungary, they will discuss the timeline for FOLIO. The Metadata Interest Group will be consulted about the timeline.
- The demo of WeCat showed a lot of functionality (deep indexing, authority linking, linked data referencing) - is the plan to have all of that functionality available in the FOLIO MARC editor? Or some portion of that functionality?
Answer: All the functionality shown will be ported into FOLIO.
- What are the implications for the MARC storage infrastructure for access to MARC source data via other apps?
Asked for clarification. Does this mean, will the data stored in @Cult, be accessible by other apps in the FOLIO environment? Answer: All relevant services will be available through Okapi. The storage will not be exposed directly. Okapi is a logic layer that is stored on top of the storage. The clients will be able to access the Okapi layer.
- What kind of documentation is available/planned?
Documentation will be provided. The formats could come in the form of a wiki, or some other form.
- How will @Cult's work relate to the instance/holdings/item prototype work that Filip has shown? Once you find a record in inventory and want to edit it, will it stay in the general screen structure that Filip has shown or will it change to something else?
Referring to Diagram 1 below, Tatiania empasized the importance of avoiding the cataloger having to duplicate data. She would like to discuss "Flow E and Flow H to update and align data, with the MM SIG group.
____________________________________
- The existing @Cult system will be integrated into the FOLIO system. They have begun to share their knowledge and technology with the developers at FOLIO. They are working with the National Library of Hungary. They have started to move the entire cataloging module into the FOLIO platform.
- Tatiana shared her screen that demostrates the outlines a scenario to integrateDiagram 1:
The diagram shows a "Common" area of information sharing, and then a local area of information storage.
Diagram 2:
