2020-04-16 Metadata Management Meeting notes

New Zoom Policy

@Laura E Daniels

FOLIO Zoom meetings now 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)

Representatives from "Knowledge Where Technologies" demoed multi-lingual support tools for FOLIO: http://folio.maktabat-guides.com/. They demonstrated FOLIO's Instance in Arabic, using their software. The Product Council will await an assessment from the Tech Council for a recommendation on the feasibility of incorporating this into an upcoming release.

Subgroup & other updates?

• Item Status Group: The group is meeting. They are having good conversations. They will give feedback. 

Data Export

@Magda Zacharska

updates/demo

Laura asked all POs to give demos to the MM group as well as talk about prioritization.

Magda thanked the data export group for their work. 

Slides - post here. Demonstration done in snapshot load environment.

Drag Excel file of UUIDs, prompting export of MARC records.

Can gather records to be exported by typing query search. Once record results are what is desired, record set can be exported. The process is that the identifiers get exported, then that file gets used to export a MARC file.  (Note: There is a page that demos CQL queries - Search - using PostgreSQL (all releases up to Juniper)) There is also a link on this page: MARC Mappings Information

The query can be exported.

In Q1, if some records do not have underlying MARC records, the entire job will fail.

In later versions, the job will not entirely fail, it will provide a report that allows the ones with underlying MARC to export and others reported in a different file.

Q1 is AWS specific. Q2 will be hosting agnostic. 

There are plans to export records without MARC as well.

In the future (Q3 or Q4), formats such as JSON will be supported for export.

Future MM meetings

Add thoughts, questions here:

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

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

      x

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