...
Data model and architecture
Slides – VBar can you post your slides here or link from Google Drive?Presentation is available here: https://drive.google.com/open?id=1KGlSSa0ajY9XcXb4QWD5_A8TxMVZWjthObRjw6seVnw
In this presentation, Vince reviewed the purpose of the codex and the types of codex data objects included in the current model: instance, holdings/item, coverage, location, and package. He also talked about the microservices approach, which means that each application (or domain) within FOLIO can have its own version of the instance with unique data elements. These instances can be linked across domains. The data stored on the central codex record will be very minimal, with most of the richer data being stored in specific domains.
Questions/Disussion:
Will Codex records referencing many external records/foreign keys (in FOLIO or external KBs)?
...
Kathryn presented an overview of the initial approach to defining metadata elements for codex records and mapping that data from another source. At the beginning phases, this work has been limited the print monographs use case and a MARC environment. E-resources and other metadata schema will be addressed in separate conversations. Kathryn presented two use cases: searching for a title and creating a purchase order for a print monograph. For each of these, she suggested data elements that would be needed to complete the task. She then walked through a more detailed mapping of proposed codex fields and mappings from MARC to the codex.
Questions/Discussion
...
Cate presented a series of wireframes that demonstrated the results of a codex search. She also showed how users would be able to drill down into each search result, displaying additional information and potentially linking into other apps.
Questions/Discussion
...