Page Comparison

Charlotte Whitt, Felix Hemme, Natascha Owens

Image Modified

Image Modified

Image Modified

FOLIO snapshot stable will show these developments tomorrow. In relation to the

screenshot above, Charlotte asked if the relationships should be explicitly labeled.

Example of a labeled screen:

Image Modified

The question as to whether or not this could be optional to display

was asked. Jacquie could see how this would be very useful to some staff members, but possibly too much information for others. Natascha noted the redundant information in the screen above.

Natasha mentioned that the group has to still discuss the issue of how analytics and bound withs will be displayed at the item level.

Laura E Daniels, Felix Hemme, Charlotte Whitt

"Resource" and "Format type" in Inventory did not correlate with EBSCO's KB terminology.

Felix introduced a list used by the German libraries of format type terminology and their applications:

Felix Hemme has translated the core terms of rda 7.2.1.3 D-A-CH.: **NEW** https://docs.google.com/

spreadsheets/d

/1ZeQJCyPM5P1oXacJaycYWOBM7bgorNPpOlztu5jEgu4/edit?usp=sharing

The discussion that followed illuminated pros, cons, and nagging questions surround the adoption of a vocabulary list like this:

Pros

• A list, established vocabulary like this, would make an easy place for programmers working with a discovery layer to access format information.
• Solves the problem between current metadata in cataloging records and EBSCO KB terminology
• Solves the problem of identifying and exposing Theses and Dissertations as a format.
• Good for filtering
  
  

Cons

• Seems to be duplicative - Information for this exists in our metadata already. (To which
• Too EBSCO specific (since need is being driven by a different vocabulary in EBSCO's KB.) Other KBs will have their own vocab. Is this solution the right way to solve the problem?
• This may not line up with established vocabulary in libraries that seek to define content.

Nagging Questions

• What data store will the discovery layer draw from? (Lisa texted Demain, who developed the VuFind connector to FOLIO. She will post an answer on the MM Slack channel, if one comes)
• What exactly is the intention or expectations for the Codex? Laura defined the Codex as being a federated search for resources both held by the library and outside of the library. Charlotte offered that while the Codex is intended initially for internal use, that could shift later.

Agreements

• Everyone agreed there is an issue with inaccurate description of formats in discovery layers. What is the best way to solve this.
• Group will think about this
• It would be helpful to see this "in action" live in FOLIO. It may help us better inform our decision. Charlotte is going to ask if that can be done. Jacquie cautioned that this would give us part of a picture, but not the entire picture of the ramifications of this added thesaurus.
• It will be useful to look at the VuFind/FOLIO demo: http://vufind-folio.scanbit.net/