2019-04-11 Metadata Management Meeting notes

Laura E Daniels

EAD/Inventory Mapping subgroup met last week and is meeting again today. Looking at mapping from EAD to Instances or Containers.

Search and Inventory Vision groups will be meeting for the first time in near future.

Laura E Daniels, Jacquie Samples, Christie Thomas

Still need to continue this discussion from April 4 meeting (not addressed April 11):

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

Christie stated that this is a working document that she hopes everyone will read and respond to.

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.

Ann-Marie (via chat):

"So is that functional requirement 1) to transliterate on the fly, then close the window and it's gone or 2) to transliterate on the fly and then store that transliteration into the Instance/SRS?"

Group: This may be too limited. There is a search and display issue.

Laura: Please comment on this document throughout the week. Charlotte suggested consulting a Niels as a next step.

Review of planned functionality in orders. User stories for Metadata Management needs?

Dennis Bridges can meet with us April 18 to discuss what is planned and what has been implemented for receiving and checking in materials.

See

UXPROD-1146 - Getting issue details... STATUS

UXPROD-193 - Getting issue details... STATUS - Dennis recommended looking at this Feature and its stories (linked below).

UIOR-159 - Getting issue details... STATUS

UIOR-161 - Getting issue details... STATUS

UIOR-167 - Getting issue details... STATUS

UIOR-173 - Getting issue details... STATUS

Laura asked that anyone who has questions surrounding serials receiving look at these JIRAs. If the questions are not answered by these stories, please keep it in mind for the discussion with Dennis.

Ann-Marie - The basics are in place for serials receiving. Right now receiving is not related to MARC records. If MARC is required, then an explanation needs to be provided. Jacquie emphasized that print serials continue to be a large component of research libraries. Christie said Chicago checks in serials without MARC Holdings. They still have a need to see what they have and when they received it.

Laura has created a Google Doc where we can record use cases and functional requirements that we are thinking of from an inventory/metadata perspective: https://docs.google.com/document/d/18F68B1OjG0kgrsSpbHov_WhUzsr0cFYUPXSOBrj4T_E/edit#

Christie pointed out that this is in the Inventory Data Model "Display received issues on a holdings record" is described on the Inventory Data Model. This is planned for Q2.

Felix Hemme

Theodor Tolstoy