2020-04-09 Metadata Management Meeting notes

New Zoom Policy

@Laura E Daniels

In April 2020, all FOLIO Zoom meetings will require a password to join.  Unless otherwise specified for a particular meeting, the password is "folio-lsp".  If this password needs to be changed, come to this page to see the new meeting password.  All FOLIO Special Interest Groups remain open to all—whether or not you are associated with an institution that is implementing FOLIO.

FOLIO Meetings with Zoom

Product Council Update

@Former user (Deleted) @Laura E Daniels

PO needs, Development resource needs

• Updates from SIG conveners

• Updates from Tech Council specifically related to architectural issues and security team

• Briefly discussed Fameflower, scheduled to come out tomorrow or after weekend.

• Check minutes

• Use of "MVP" as a marketing term. Communicating 

• Technical skills are needed for parts of the project. If you know of anyone who may have additional time or willingness to contribute to development, let Jesse, Chair of Product Council know. Need for product owners

Minutes: https://docs.google.com/document/d/12Fmk45bYQ4W4Ohx-F21Wt88ZG30igp64mbSKEpCJOUE/edit

Subgroup & other updates?

Data Import: See notes in Fameflower release page: Q1 2020 (Fameflower) Release Notes

QuickMARC is moving along quickly. This is different from "Quick Add". QuickMARC is a lightweight MARC editor that takes a user from an Instance record to the MARC record that may be behind it. 

There's a new Z39.50 group. Charlotte is the PO for that group. 

HRIDs in Inventory, implementation decisions

Thinking through ramifications of how HRIDs are implemented (e.g., prefixes or not, continuation of numbering from previous ILS) & documenting implementation decisions

Does this information belong in Tips & Tricks? somewhere else?

Some background (thanks to Ann-Marie):

Here is the most recent documentation on HRIDs: https://docs.google.com/presentation/d/1D4yEPVhFbD8ZXlyKfInRafnJUfQWM8syakLu7v6_c8U/edit#slide=id.p1.

Migration is mentioned on slide 4. 001 handling is mentioned on slides 6-7. The Jiras that detail the SRS HRID handling for MARC Bibs are https://folio-org.atlassian.net/browse/MODSOURMAN-206 https://folio-org.atlassian.net/browse/MODSOURMAN-249

See # metadata-management Slack discussion starting on March 20th

Christie reported: Chicago was building their processes based on an older model of FOLIO in which the HRID did not have a prefix. Now, they do contain a prefix. Concern - one HRID associated with two UUIDs. Concerned about the implications. There is no structured relationship that used the HRIDs. What are the implications of not making use of prefixes on HRIDs in Inventory Instance, Holdings, and Item. Also concerned about documentation becoming outdated without knowing it is outdated. Need a formal, codified documentation. How do we make this and other decisions meaningfully?

What other changes are occurring in the FOLIO ecosystem that we are not aware of?

Ann Kardos - 5 Colleges - experienced using outdated mapping documentation that she was told to use, causing a problem with migration and having to redo work.

Ann-Marie - Suggested "Tips and Tricks" is the best place to put the most updated documentation. 

Laura echoed concerned about not having a best practices place. This goes beyond MM SIG. We need to make our way to the "most definitive, latest information available".  Suggestion of linking to GitHub. 

Point made that development and changes are constant, so communication is the key to keeping up to date.

999 field contains UUID for Source Record and Instance that link the two together. They do share the same HRID.

Once an HRID is assigned, can it be changed? As far as Ann-Marie knows, it's not editable. 

UXPROD-1752 - "Optimistic locking" as well as transaction

Future meetings format & structure

@Laura E Daniels

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

Future MM meetings

Do we want to start formally splitting meetings between development and implementation discussions? Have a more organic structure? Something else entirely? What future topics would you like to discuss?

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

Please think about this over the next week. 

We could keep a running list of ideas on a Google Spreadsheet. 

Future meeting topics

Upcoming priorities for development (Inventory, Data Import, Data Export, MARCcat?, quickMARC)

Demos: Data Import, Data Export, quickMARC

https://folio-org.atlassian.net/browse/REP-234 (overlap analysis) need to collaborate with RM – Chalmers is interested as well (incorporates Inventory & e-Holdings plus ???) see also https://folio-org.atlassian.net/browse/REP-92

Statistical codes: type = "Action" – create list of recommended values

Refine the result list - work planned for development Q3 2020

https://folio-org.atlassian.net/browse/UXPROD-1634 and slide deck about hierarchical display of result list

@Filip Jakobsen suggests to use Message banner (a new component) to display if an instance record is marked as: Suppressed from discovery, Staff suppress, or Previous held, or holdings/item is marked Suppressed for discovery. This use is intended as a MVP solution: https://ux.folio.org/docs/guidelines/components/message-banner/ Post-MVP we aim for ux consistency with MARCcat.

https://folio-org.atlassian.net/browse/STCOM-592

Source format (FOLIO, MARC and more) and Source of truth (SRS, LIBRIS, K10Plus and more). 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. https://folio-org.atlassian.net/browse/UXPROD-2249

Inventory, MARCcat, Data Import Permissions interaction review

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)

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

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

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 Council

Item statuses and the apps that affect them - https://docs.google.com/spreadsheets/d/19_aA7bhRIxhcC6Gz-rK_LrfOtz8F5VaOmOcsFsdGU8I/edit#gid=2006676577

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

https://folio-org.atlassian.net/browse/UIIN-864

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

https://folio-org.atlassian.net/browse/REP-234

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

Aaron Trehub

Auburn

Ann-Marie Breaux

EBSCO

Ann Kardos

UMass Amherst

@Charlotte Whitt

Index Data

Christie Thomas

Chicago

Christin Seegert

hbz

Colin Van Alstine

Smith (FC)

Damian Biagi

Dennis Bridges

Stacks

Dennis Christman

Duke University

Douglas Chorpita

Goethe Uni Frankfurt

Dracine Hodges

Duke University

Felix Hemme

ZBW

Filip Jakobsen

Jacquie Samples

Duke University

Jason Kovari

Cornell

Jenn Colt

Cornell

Jennifer Eustis

UMass Amherst

Jessica Janecki

Duke University

Kristen Wilson

Index Data

Laura Wright

Cornell

Lisa Furubotten

Texas A&M

Lisa McColl

Lehigh University

Lisa Sjögren

Chalmers

Lynn Whittenberger

Magda Zacharska

EBSCO

Martina Schildt

VZG

Nancy Lorimer

Stanford

Natascha Owens

Chicago

Niels Erik Nielsen

Patty Wanninger

EBSCO

Rita Albrecht

HeBIS-Verbundzentrale

Sara Colglazier

MHC/5C

Tiziana Possemato

Theodor Tolstoy

EBSCO

Wayne Schneider

Index Data