2019-11-14 Metadata Management Meeting notes

2019-11-14 Metadata Management Meeting notes

Date

Nov 14, 2019

Attendees

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

Discussion items

Product Council Update

@Laura E Daniels

Ingolf Kuss presented the Report of the Reporting Data Privacy Working Group

Report of the Reporting Data Privacy Working Group - Maintaining privacy in the LDP. Sensitive reports were recommended to be "in app". "In app" reports are not restricted to one app, unfortunately. More accurate: "In FOLIO" report. 

Discussion around WolfCon Planning - In addition to Resource Management proposals there will be a discussion of "Item States" or "Item Statuses". 

Subgroup Updates and Other Updates

 

  • MARCCat group has not been meeting. Laura notes progress in the testing environment.

  • Export subgroup continues defining requirements.  During last meeting we concentrated on creating Export mapping and job profiles and discussed importance of consistency in the behavior between import and export apps.  Today we plan review and prioritize features currently associated with Metadata Export epic.  Notes from last week meetings: https://drive.google.com/drive/folders/1_HlVrD4gWyBPWWjnqS_dcvb4u2pNlL8Q

WOLFcon proposals update (Nov. 18 deadline to submit)

 

https://docs.google.com/spreadsheets/d/1VEVZT4U8IO9Wztx72xR2zmuLz5A-dlhvgARmdA7DvUU/edit#gid=0

(RM list contains some MM-related sessions as well: https://docs.google.com/spreadsheets/d/1fu-vzvWV1YTQp1HgWLm3qSLqOSGG0w2biXZthIBgKdQ/edit#gid=0)

Please add notes stating your opinions on the worthiness of these proposals.

Feature ranking/new features?

 

If your institution has not ranked https://folio-org.atlassian.net/browse/UXPROD-2002 (Implement Normalized Call Number for Sorting), please do so. This helps with capacity planning prioritization.

MARC 655 mapping into Instance

 

Resolved for now, based on the Doodle poll results:

Command Line MARC to Instance Editing Demo

@Lisa McColl

https://github.com/folio-org/mod-source-record-manager/blob/master/RuleProcessorApi.md

Tool: Postman (freely available, downloadable app)

Connect to a version of FOLIO on a server

Only API options needed are POST, GET, and PUT

POST to get a token; GET the mapping rules

Mapping rules (in Body) are displayed in JSON:

copy entire JSON and paste it into the edit window

Then can change MARC fields, delete, or can add MARC fields if they aren't part of the default

PUT command to send the changes – need to be aware of which version of FOLIO the changes are being sent to

Can use GET to retrieve new rules and verify if changes were made

Cheat Sheets for the Beginners Among Us:

Quick way to get a token (much quicker than the cheat sheet method): https://folio-testing.aws.indexdata.com/settings/developer/token (Thank you @Jenn Colt)

Future meeting topics

 

External integrations (e.g., Caiasoft for off-site storage management) and updates to FOLIO. Where/what is the "source of truth"? --possibly to be addressed at WOLFCon

@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 consitency with MARCcat.

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

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.

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)

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 Council

Item record statuses and the apps that affect them

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://wiki.folio.org/pages/viewpage.action?pageId=78336464

present?

Name

Organization

present?

Name

Organization

 

Aaron Trehub

Auburn

      

Alice Krim

 

 

Ann-Marie Breaux

EBSCO

 

Ann Kardos

UMass Amherst

x

@Charlotte Whitt

Index Data

x

Christie Thomas

Chicago

 

Colin Van Alstine

Smith (FC)

 

Damian Biagi

 

 

Dennis Bridges

Stacks

 

Dennis Christman

Duke University

       X

Douglas Chorpita

Goethe Uni Frankfurt

 

Dracine Hodges

Duke University

x

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

x

Laura Wright

Cornell

 

Lisa Furubotten

Texas A&M

 

Lisa McColl

Lehigh University

 

Lisa Sjögren

Chalmers

 

Lynn Whittenberger

 

x

Magda Zacharska

EBSCO

Regrets

Martina Schildt

VZG

x

Mary Alexander

Univ. of Alabama

 

Nancy Lorimer

Stanford

x

Natascha Owens

Chicago

 

Niels Erik Nielsen

 

 

Patty Wanninger

EBSCO

X

Rita Albrecht

HeBIS-Verbundzentrale

 

Sara Colglazier

MHC/5C

 

Sarah Schmidt

Duke University

 

Tiziana Possemato

 

 

Theodor Tolstoy

EBSCO

 

Wayne Schneider

Index Data