2019-04-11 Metadata Management Meeting notes

2019-04-11 Metadata Management Meeting notes

Date

Apr 11, 2019

Attendees

  • please put an 'x' next to your name in the list below the "Discussion items" if you are attending. Thanks!

 

Discussion items

Item

Who

Notes

Item

Who

Notes

Product Council Update

@Laura E Daniels

Q1 Summary and Q2 Planning

Bellis Release Notes: Q1 2019 (Bellis) Release Notes

An intermediary release (Q1.1) is also planned for mid-late May.

EPIC Prioritization Process – survey will be going out soon

Face to face meeting planning

@Laura E Daniels

Meeting dates: June 17-19, Location/Hotel: DoubleTree by Hilton Hotel Washington DC - Crystal City,

300 Army Navy Drive, Arlington, VA 22202

Attendance fee: ~$100 ; Target number of attendees: ~120

Registration link should be out shortly – will be added here

https://docs.google.com/spreadsheets/d/1JELsHTfu_xYA1yTsyRCorZzEVofd8Njsg1Lo32rm_3s/edit#gid=1803978717

-see in particular the "Meeting List" sheet – plan to attend, as possible, based on these topics

If you are unable to attend in person and are invested in a particular topic (or more than one), let Laura know – we will find a way to set up a Zoom option

WOLFCON being planned for January 2020

Subgroup Updates and Other Updates

 

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.

UUID-HRID

@Ann-Marie Breaux (Deactivated)

UUID-HRID Handling Overview presentation: https://docs.google.com/presentation/d/1wFUCRYgbLQeuWnwtIYYnSrZD4qnhHPfLs2C941I_LMk/edit?usp=sharing

UUID-HRID Handling DRAFT: https://docs.google.com/document/d/1kgHxFNUrLb6xjDp1AcyUFhfdUL8VP1U6zknhjUxuBRs/edit?usp=sharing
UUID-HRID examples: https://docs.google.com/spreadsheets/d/1BcCvbzusARM0P7xq2pCAAVPNH-qAYbRP1awiGnhSuUc/edit?usp=sharing

Multiple Graphical Representations

@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.

Note: Charlotte has added following feature description (UXPROD) in Jira: 

https://folio-org.atlassian.net/browse/UXPROD-1646

Serials receiving, items, etc.

for reference only

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

https://folio-org.atlassian.net/browse/UXPROD-1146

https://folio-org.atlassian.net/browse/UXPROD-193 - Dennis recommended looking at this Feature and its stories (linked below).

https://folio-org.atlassian.net/browse/UIOR-159

https://folio-org.atlassian.net/browse/UIOR-161

https://folio-org.atlassian.net/browse/UIOR-167

https://folio-org.atlassian.net/browse/UIOR-173

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.

 

Future meeting topics

 

Mapping to Inventory beyond MARC (being worked on by EAD mapping subgroup)

Authority Data (for June working meeting?)

Discovery

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)

Item record statuses and the apps that affect them

 

Charlotte: Music cataloging review of data elements would be helpful.

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

present?

Name

Organization

present?

Name

Organization

x

Aaron Trehub

Auburn

      

Alice Krim

 

x

Ann-Marie Breaux

EBSCO

 

Ann Kardos

UMass Amherst

regrets

@Charlotte Whitt

Index Data

x

Christie Thomas

 

 

Colin Van Alstine

Smith (FC)

 

Damian Biagi

 

x

Dennis Christman

Duke University

 

Dracine Hodges

Duke University

regrets

@Felix Hemme

ZBW

 

Filip Jakobsen

 

x

Jacquie Samples

Duke University

x

Jason Kovari

 

 

Jenn Colt

 

x

Jennifer Eustis

UMass Amherst

 

Jessica Janecki

Duke University

 

Kristen Wilson

Index Data

x

Laura Wright

 

x

Lisa Furubotten

Texas A&M

 

Lisa McColl

Lehigh University

 

Lisa Sjögren

 

x

Lynn Whittenberger

 

regrets

Martina Schildt

VZG

x

Mary Alexander

Univ. of Alabama

 

Nancy Lorimer

Stanford

x

Natascha Owens

 

 

Niels Erik Nielsen

 

 

Patty Wanninger

 

x

Sara Colglazier

MHC/5C

x

Sarah Ross

Cornell

 

Sarah Schmidt

Duke University

 

Tiziana Possemato

 

 

Theodor Tolstoy

 

 

Wayne Schneider

Index Data