Vince Bareau (EBSCO), Marc Johnson (Knowledge Integration), Ian Ibbotson (Knowledge Integration)
Diagram's High Level Goals:
Blue boxes, or domains considered.
Demonstrates the idea of not duplicating efforts.
FOLIO Codex Domain
Contributions to FOLIO Codex will be made dynamically through APIs so information is always up to date.
Vince clarified that this is not a federated search approach. Even though the FOLIO Codex is not where the searching will be happening, Vince stated that we are first establishing a controlled vocabulary. Therefore reconciliation will happen in essence locally, before the search is indexed.
Circle represents a gate. If some other system is being used to represent a portion of your collection. We don't want to copy the data over if we don't have to. Example: If library has access to 12,000 journals, 300 identified that are high use, can be entered into the Folio Codex.
Folio Codex Domain Details
Labeling is similar, but not the same as bib frame.
Instance represents the resource itself. The descriptive metadata is specific to the resource itself, regardless of how it is access, or the rules.
Holding - Describes the relations that institution has with the instance, for example coverage, or rules like embargos
Location - This could be coordinates for a physical item or contain an URI. It's a location object so it can be used to describe a number of properties, for example platform information
Lynn - Why is location connected to Instance instead of Holding? Vince - There may be multiple locations associated with an Instance. At the highest level of user experience, consumption is most important.
Customization allowed of selected fields.
This is there to serve same purposes as cataloging. This is shown on the right side of the diagram. This is about local resources, local information and notation. Physical instance. These records will originate from source records (often MARC). Reconciliation of multiple, possibly conflicting authorities.