2019-05-09 Metadata Management Meeting notes

Product Council Update

@Former user (Deleted)

How important is Workflow app to MM?

Current proposal (develop manual workflows first): https://docs.google.com/presentation/d/10mJCpeoUEudLgLR5zpsixSNN2PbPNSRaiU01Sprrlck/edit#slide=id.g59cd4f7b69_0_3

• Erin and Laura gave the update. There was a proposal to develop the workflow app first to deal with manual workflows. See link above.

  • How many development resources do we want to develop to the workflow app, considering other developments that are needed?

  • A lightweight development was proposed.

  • "It's hard to think about prioritizing workflow when the pieces for the workflow are not there yet" – Kristin Martin

  •  It was pointed out that the interest of some universities in this surrounds batch operations and the workflows needed to support that. 

  • Laura will put this on an upcoming agenda for a discussion with the larger group.

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:

https://www.eventbrite.com/e/folio-meeting-june-2019-tickets-59544369813

Updated agenda (still in process)

https://docs.google.com/spreadsheets/d/1na2hOx0iHh6U1rhjut1NJnWb6qxJUcHgezK1-oVtHgo/edit#gid=1940789848

Subgroup Updates and Other Updates

No reports

Report on EAD-Inventory Mapping

@Aaron Trehub @Laura E Daniels @Lisa Furubotten

Proof of concept – a few additional proposed elements defined for Container records

Summary report: https://docs.google.com/document/d/17NL62V93O73uOTbHv6LMLf3WdTfcVrT1z-dmYooW-Y0/edit

Mapped from EAD into inventory. Focused on the container record and identified some additional elements that may be useful to add. They proposed new elements/fields to be added to the container record: Language, Physical Description, Access & Use Conditions, and Contributor.

2019-05-09 Metadata Management Meeting notes

Multiple Graphical Representations

@Laura E Daniels, @Jacquie Samples, @Christie Thomas

(to be continued)

working document:

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

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.

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

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

Christie expressed hesitation about being too prescriptive about what the JSON should look like. She suggested spending time on the Functional Requirements. Suggestions for additional functional requirements were added to the Google doc: DRAFT - Multiple graphical representations in FOLIO. (Also linked above.) 

The group also would like to make recommendations as to what this should look like in the FOLIO interface. Example systems that work well?

Future meeting topics

Reporting: in-app and data warehouse (planned for May 16)

Inventory Permissions (https://folio-org.atlassian.net/browse/UXPROD-1371)

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

Item record statuses and the apps that affect them

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

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

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

Aaron Trehub

Auburn

Alice Krim

Ann-Marie Breaux

EBSCO

Ann Kardos

UMass Amherst

@Charlotte Whitt

Index Data

Christie Thomas

Colin Van Alstine

Smith (FC)

Damian Biagi

Dennis Bridges

Stacks

Dennis Christman

Duke University

Dracine Hodges

Duke University

@Felix Hemme

ZBW

Filip Jakobsen

Jacquie Samples

Duke University

Jason Kovari

Jenn Colt

Jennifer Eustis

UMass Amherst

Jessica Janecki

Duke University

Kristen Wilson

Index Data

Laura Wright

U Colo Boulder

Lisa Furubotten

Texas A&M

Lisa McColl

Lehigh University

Lisa Sjögren

Lynn Whittenberger

Martina Schildt

VZG

Mary Alexander

Univ. of Alabama

Nancy Lorimer

Stanford

Natascha Owens

Niels Erik Nielsen

Patty Wanninger

Sara Colglazier

MHC/5C

Sarah Ross

Cornell

Sarah Schmidt

Duke University

Tiziana Possemato

Theodor Tolstoy

Wayne Schneider

Index Data