2019-07-25 Metadata Management Meeting notes

Laura E Daniels Charlotte Whitt Ann-Marie Breaux (Deactivated)

Use cases for batch editing needs both within and across apps:

1) Identification & selection of records to be acted on

2) Definition of edits to be made (and implementing those changes)

e.g., find/replace; delete field

UXPROD-120 - Getting issue details... STATUS

Where/how should the identification & selection occur?

Where/how should the editing occur?

USE CASES SPREADSHEET

Laura E Daniels, Jacquie Samples, Christie Thomas

STILL ON HOLD for future meeting (possibly with representative members from Tech Council)

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.

Source of truth (SRS). Review the FOLIO metadata flow based on test of the newly implementation of edit freeze of records in Inventory when having only SRS and Inventory installed. Is the freeze to happen between SRS and Inventory, or freeze of Inventory is only when there is a MARCcat equivalent of the Inventory record?

Rename the Notes accordion in Instance, Holdings, Item and Container record to be renamed, in order to distinguish between the new Notes app (https://docs.google.com/presentation/d/1BMitl09O4C_cg2cN34T5ofZ88Xg3ub3RysDfS6Vue20/edit#slide=id.p) and the notes we have in the metadata records.

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 – need to clarify sources of data for discovery vs. data needed for operations; this needs to be documented for the entire FOLIO community and direction should come from Product Counil

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

Felix Hemme

Theodor Tolstoy