Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

ItemWhoNotesAction Items
Update from Product CouncilDracine Hodges
  •  
Review of Metadata ModelVince Bareau (EBSCO), Marc Johnson (Knowledge Integration), Ian Ibbotson (Knowledge Integration)
  • Diagram's High Level Goals: (The notes that I was taking did not get saved. I had to log in again, so this first section is sparse. I'll go in and watch the recording when it is available and provide more detail.)
    • Reconciliation of information
    • Referential model of using data
    • 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.
       
  • Inventory Domain
    • 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.
       
  • Questions
    • Lynn asked for clarification on the inventory. Is there a distinction between the "library cataloging" and "inventory"? Vince will probably change labeling in Inventory box from "Physical" to "Local". It can be used to describe an electronic resource.
    • What about instances where we can refer entitlement to local records? Example: Streaming video... Vince - Assumes these are controlled by a third party that delivers a service. Entitlement - What are you entitled to
    • Jacquie - Is there a possibility of making a connection that goes from Entitlement/Holding to Physical Instance box?
    • Could we use a referential model for our print resources? - Vince - "Yes"
    • Anne - Question about definition of "Inventory" - Is "classification" in the sense of call number, or is that word being used to describe forming things into categories? Vince - there will be support for a number of taxonomies and that will contribute toward the inventory.



       
  •  
  
  • Doreen asked if we should continue the discussion offline? Could Vince attend next week? Vince is happy to attend again, receive feedback. This is a proposed model.

...