2019-10-31 Metadata Management Meeting notes

Export Group: Use cases were reviewed. Flowcharts to be reviewed. Starting discussion about export profiles.

MARC-Instance Group will meet next week to try to finalize plans.

Data Import: Ann-Marie Breaux (Deactivated) is interested in feedback on Bib Import Mapping and on the CLI tool for changing the default mappings.

• Updated MARC-to-Instance default mappings
  • We’ve corrected most of the things that were discovered in the first round of testing.
  • New spreadsheet for next round of testing: https://drive.google.com/open?id=1Tm12DGFCLpABOxVcJKMFQUHLSWRx232qNUCgLbhWuPE
  • Try loading files (use folio-snapshot-load), and check to see if instance mappings match your expectations
  • If issues, record on the spreadsheet and take a screenshot
  • Post in folder: https://drive.google.com/open?id=1JMLA10CUk5wgqn_bIker2whgYfZ04wB2

• CLI editing of the default map.
  • This functionality is NOT available in 3.2, but is available on folio-testing, folio-snapshot, and folio-snapshot-load. We’re interested in feedback on:
    • Whether the documentation is clear and sufficient. If not, what else is needed?
    • Whether it works as expected
  • Please test on folio-testing, folio-snapshot or folio-snapshot-load
  • Put a note on the # data-import-batchload Slack channel if you’re changing the mapping rules, and which environment
  • Once you have finished PLEASE use the reset API to change the rules back to their original state
  • All will reset overnight
  • Send feedback to Ann-Marie on documentation and whether it’s working as expected
  • Background
    • Previously Data-import had only hard-coded rules for MARC-to-Instance mapping
    • Now Data-Import provides REST API to edit rules
    • Rules now are tenant-specific; each tenant can set their own mapping rules
    • FOLIO starts with default rules; then each tenant can edit rules in their own way
    • Tenant can restore rules to default if needed
    • Link to default mapping rules: https://github.com/folio-org/mod-source-record-manager/blob/master/mod-source-record-manager-server/src/main/resources/rules/rules.json

• This is how a simple rule looks, taking the value from MARC 001 field and putting it into the Instance HRID field:

"001": [

{

"target": "hrid"

}

]

• Documentation on editing rules: https://github.com/folio-org/mod-source-record-manager/blob/master/RuleProcessorApi.md
• And at last sprint review, one of our Folijet developers gave a brief demo of this just-completed CLI tool for editing these mapping rules: https://www.youtube.com/watch?v=srq5udZgma8&feature=youtu.be (34:25-38:00)

Ann-Marie Breaux (Deactivated)

Charlotte Whitt Laura E Daniels

Recent UX mock-ups show what is called Administrative Data in Instance/Holdings records shown as Item Data in Item records:

https://drive.google.com/file/d/1qvLnIJ_iy5OkiGHL9HKRp2mF_OPjHkRp/view

Is this of concern from an MM perspective? How important is consistency here?

Cate: Work on effective call number logic is being looked at. There will be an accordion for the effective call number. The effective call number block and effective location are being moved up. 

Charlotte: Could this new "Item data" area not be integrated with administrative data. Consistency is sacrificed in this latest UX design.

Laura wondered if keeping the label as "Administrative data" would be the best solution. Sara commented that it is confusing to see duplicate data on one screen - why are elements repeated on the same screen? 

Cate commented that she received a lot of positive feedback about this arrangement.  Charlotte: suggested moving Effective call number block and effective location to the top heading area - outside of accordions.  Cate noted that we do not have this UX pattern at the moment. Charlotte pointed out that it is consistent with having redundant data displayed at the top header area:

Felix: I was suggesting to add the effective call number block into the "permanent" section at the top: https://folio-project.slack.com/archives/GMAPRTZ6V/p1569592118055300

Development is delayed on implementation of Preceding/Succeeding titles in Instance records.
We are looking at a "thin thread" implementation for mvp:

UIIN-809 - Getting issue details... STATUS

UIIN-810 - Getting issue details... STATUS

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.

STCOM-592 - Getting issue details... STATUS

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

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

Felix Hemme

Theodor Tolstoy