2019-05-02 Metadata Management Meeting notes

• Holly Mistlebauer updated the group on how she is compiling the results of the gap analysis report. 
• Hkaplaniangave a brief presentation about documentation. He separated documentation types into three groups by user type: Endusers, Sysops staff, Developers.
  • Harry's plan recommended hiring experts in this area to fill this need.
  • Harry's slides: https://drive.google.com/open?id=1xfeP36_Q87kB1ULACpSjxxoDMVvtcFPm
• There was some discussion about inviting non-EBSCO vendors to collaborate and provide input.

Ann-Marie Breaux (Deactivated) I'll miss today's meeting, but a quick update from Data Import. A couple people continue meeting with Filip to finalize the matching and action UI. UI developers are finishing the job profile settings and starting work on the match profile settings. Backend developers have added the SRS UUID to the MARC 999 field, and are almost finished adding the related Instance UUID. I still owe final writeup on the 001/003/035 HRID handling.

MARCCat - MARCCat subgroup group gap analysis was completed and submitted.

Aaron Trehub Laura E Daniels Lisa Furubotten

Laura E Daniels, Jacquie Samples, Christie Thomas

(to be continued)

working document:

https://docs.google.com/document/d/1e6zlt7Gsd50W1HsRWWM6aerClXYe1l7XACaInVuWcoE/edit

Problems:

• If multiple forms of the value are represented in a single JSON object, both scripts have to be included in a single value cell. This limits the search function.
• Chicago is testing graphical representation in FOLIO. Here is an example:
  
  
• See MARC record: https://catalog.lib.uchicago.edu/vufind/Record/8539712/Details#tabnav
• See JSON sample: (Christie will provide)
• Functional requirements need to be built so developers can understand the issues. What would we like to have happen in FOLIO?
• Proposed solution:
  

  • Single JSON object for the property, e.g., Title, with the ability to have an array of values for display (labels).

  • Values should allow for a property that identifies the script.

  • This would allow for the ability to configure displays to include multiple representations or a selection of representations.

Functional requirement: Create an instance record and be able to have multiple graphical representations of the language, or be able to put a non-transliterated title that can be searched in other scripts.

Reporting: in-app and data warehouse (planned for May 16)

Inventory Permissions ( UXPROD-1371 - Getting issue details... STATUS )

Search enhancements - possible also look at more general requirements for defining search, e.g. when to use: Phrase search, Truncating (left and/or right), Stemming, Nested search, Boolean search, etc. (TC and MM task)

Authority Data and Inventory Vision (small group work first)

Discovery

Item record statuses and the apps that affect them

Music / Maps / Media cataloging review of data elements in Inventory

Felix (via chat) "@charlotte: I could ask a colleague (from one of the 180 network libraries) if she/he could review the beta elements from a 'musical' point of view."

Texas A&M may have a music cataloger that can help.

Christie offered to load cartographic and music data from other libraries into their test FOLIO instance.

Jennifer (via chat): We should also look at video as well. Videos have other standard numbers EAN for instance and fields that people like to search and discovery them by

Container Record? - Initial impetus was to provide another level of hierarchy to unite records together in some way. Different institutions could use it to solve different problems. It should be available to be used flexibly. The vision is that it will "live" in the Inventory app. 

https://docs.google.com/document/d/1DakHW6D5_09uKJPQzCSTwycP0gqkPs6E7k35_KpfCxg/edit

Implications of Container and cross-app interactions will need to be discussed with Reporting --

-invite Reporting SIG members to the Package (Agreements) / Container (Inventory) interaction session at the F2F meeting

Felix Hemme

Theodor Tolstoy