2019-12-05 Metadata Management Meeting notes

Chalmers updated the Product Council on their implementation. They discovered an issue with notices not going to patrons, but they have fixed it. Looking for a way to catch these before they are a problem. Lisa from Chalmers presented at FOLIO Day in France. There was a lot of interest.

Sebastian updated the group on Index Data's participation in 2020. EBSCO funding has kept them in the project, but it will be tapering off at the end of this year.  They will focus on other projects such as ReShare and becoming a FOLIO service provider.

Kirstin updated the group on GBV cooperation. OCLC/CBS union catalog and inventory will have an API developed. They are working with an application developer for updates from the LAS:eR ERM tool for consortia into Folio ERM.

Tech Council issued their monthly update. They are working with Chicago and Cornell to work with OCLC for APIs with Connexion. Tech Council is developing a security policy.  

WolfCon's objectives and agenda were discussed. Governance changes will be an issue, post MVP functionality and feature development, sustainability plans.

Reminder: let us know if you will or won't be attending WolfCon here:

https://docs.google.com/document/d/12Qcr3Sm3LfGUEZZonLWlk5w4OzKPHwAAlh_aCqdCv5o/edit

1. Effective call number - The call number in the item record that is either the call number coming from the item record, or holding. Call number prefix, call number, and call number suffix. If nothing is in the item record, all is inherited from Holdings Record.  If there is an empty field, for example the prefix, in the item record, then if there is a prefix in the holdings record, that prefix will populate the item prefix. Something in the holdings trumps nothing in the item.
   
   In the meeting referenced above, no use cases came up where this would be a problem. This is the current behavior. Laura would like to note if someone does think of a use case where this would be a problem.
   
   Cate - If you want to temporarily change the item call number, it is possible, however a field cannot be blanked out. 
   Jacquie - Is this locally configurable? Laura doesn't think that we are thinking of this configurable?
   Christie - For vast majority of materials, they want the prefix inherited. In the edge cases however, that behavior would have to be overwritten. There should be a way to make a call number field null for those edge cases.
   Cate - mock-up that reflects the way holdings/item call numbers work today. The "effective call number" comes from the holdings in this example. 
   
   
   
   Cate - Effective call number type on item record? Cate noted that type affects code for sorting, for one thing. Charlotte noted that they are thinking of having a Call Number type filter in Inventory. Charlotte suggested that the Effective call number type does not need to be included at the top. Cate pointed out the element could be present, but not displayed. It could be present for reporting purposes. 
   
   Shelving Order - Cate said Tod's code works for LC, Dewey. What should be used for call numbers schemas that are local? Sort could be alpha-numeric. Christie said Tod's will work for alpha-numeric. Does Tod's code rely on the Effective Call Number Type for sorting?
   
   Christie offered to load call number data from other libraries into one of Chicago's test server. Send in an email or Slack - a .txt file would be fine. Christie will create dummy records to host these call numbers. (will revisit next week)
   
   
2. Priority of Effective copy number?

use case: large sets, much easier to have copy number inherited from holdings rather than having to enter it on every item record

There will be additional UX features to rank soon related to this

Updates on current work on Q4

• Permissions in Inventory (Basic CRUD is implemented, Q4 2019. UXPROD-1371 CLOSED)
• Inventory Search: Segmented control has been implemented. Search options can be specified for the Instance, Holdings, and/or Item.
  • "Keyword" search expands options - calling up titles that have words within the title, and not in a specific order. A "Title" search will still need a more precise entry to retrieve results. 
  • Staff suppress - suggestion to be able to search by records that are not suppressed - to somehow filter out suppressed records from search results.
  • CQL search is now implemented in Inventory - in all three segments:
    • Documentation/samples on Query language search is gathered on a new Wiki page. See: https://folio-org.atlassian.net/wiki/pages/viewpage.action?pageId=5669744
    • Property names are documented in Inventory Query Search - Inventory Beta - Metadata Elements - see tabs for instance, holdings, item

Alternate Graphical Representations

https://wiki.folio.org/pages/viewpage.action?pageId=78336464

x

VZG

Stanford

Index Data