2024-05-30 Metadata Management Meeting notes

Announcements

• UAT for Ramsons

  • Updates to 035 OCLC normalization in Data Import Processing (UXPROD-4081)

  • Updates to Diacritics for Inventory & MARC Authority Search (UXPROD-4694)

  • UAT runs from May 24th, until Wednesday, June 5th

  • A form with testing instructions and details can be found here:
    https://forms.office.com/r/BkuZLyvQUD

• App Interaction SIG will discuss the requirement to make item material type optional

  • If you are interested and can find the time please join the discussion on June 3rd at 12pm ET. AI will meet here: https://zoom.us/j/869183544.

  • Agenda: https://folio-org.atlassian.net/wiki/x/EAApD

• From Charlotte: If you are interested in participating in improving our reference environments FOLIO Snapshot with real looking and more complete high quality sample data, consider joining a small and fast moving working group with ~ 4-6 SMEs from FOLIO libraries. So if you'd be interested in participating in this work, then please reach out to me and/or @Yogesh Kumar - we hope to kick start the work in week 25 (June 17 - 21)

008 dropdowns work

@Małgorzata Gajkiewicz

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

Dependent on record type and bibliographic level in LDR - dropdowns in 008 change accordingly and validation rules are applied. Mandatory character positions are in red, optional in gray.

If you have an invalid value in an 008 field and you try to save the record, this will prompt an error message and you will have to fix the invalid character position which will be noticeable by a red box surrounding the character position. We can still import records that have invalid 008’s. If we perform batch updates on records with invalid 008’s via data import (i.e. overlaying an existing record), this should also work. In these cases, how will we know that the 008 is invalid? Data import has very minimal validation rules so the error message will only come up while editing via quickMARC.

Story related to handling bad 008s imported - https://folio-org.atlassian.net/browse/MODQM-329

Feedback:

It is difficult for some people to see the red outline on the invalid 008 units.

Being able to differentiate between no data in a character position versus it being intentionally blank (in the UI they both show up as backslash which differs from how this would display in the raw mark). Blank should be blank, not a backslash. From chat: Christie, with regards to your question: Am I understanding correctly that you sometimes use / to indicate "empty position" and sometimes to say "not coded"? Correct. You can have a |, \, or ' ' (an empty space).

Issue where some records have too many bytes on the 008 fields in their records - you can now edit records that have errors in 008 which would include this scenario.

Templates would be helpful to solve many of our concerns.

Tenant level MARC validation rules requirements

@Khalilah Gambrell

Requirements overview document

Feel free to add comments to Khalilah’s slide deck.

For Ramsons release. Give you the ablility to define validation rules for bib and authority records. Ramsons--via API, future release will provide a UI for defining these validation rules.

System field rules (e.g. LDR, 245) a tenant cannot override (at least for the initial release). Standard field rules (e.g. 520) - you can define if it is required, you can define indicator codes and subfield codes. Local fields (e.g. 019) - you can define anything you want.

Validation error messages will show inline.

Questions (people can respond directly in slide deck - see slide 12; respond by June 6th):

How to handle: Cataloger adds MARC bib field 227 and library/tenant has not defined a validation rule. User hits Save button.

Would your library prefer to continue to use the current MARC validation rules? If so, why?

What requirement has not be covered in this slide deck that you feel is critical to be implemented for Ramsons release? 

PC updates

@Charlotte Whitt

2024-05-30 Product Council Agenda and Meeting Notes

The Quesnelia Release is still targeted for end of this week.

Today the PC discussed how to effectively draw out action items from the document “Things that could be better in FOLIO”. PC is using this spreadsheet as an example.

The spreadsheet will be reviewed at the meeting in two weeks.

BELA (Bulk Edit and Lists App)

Jennifer Eustis

2024-05-28 BELA Meeting Notes

For Ramsons, more work will be done on bulk editing instance notes.

For the Bulk Edit Queries, the working group would like to prioritize work on the Electronic Access and in particular being able to query all of the fields (URL Relationship, URI, Link text, Materials Specified, Public Note).

Data Import Working Group

Jennifer Eustis

The next meeting is June 12. On June 12, the working group is going to discuss open issues added to the Data Import Topic Tracker that have yet to be discussed, 2024-7-10 Data Import Subgroup meeting .

quickMARC Subgroup update

Raegan Wiechert

quickMARC meetings will be cancelled for the month of May.