2024-01-11 Metadata Management Meeting notes

Date

~

Note taker: Laura Daniels, Lynne Fors, Alissa Hafele, Natascha Owens

Recordings of meetings can be found in the Metadata_Management_SIG > Recordings folder on AWS from 2022 onwards: https://recordings.openlibraryfoundation.org/folio/metadata-management-sig/

Discussion items

Announcements


Help is once again needed for documentation of MM-related apps. Reach out to Laura E Danielsand/or Lisa Lorenzo

Confluence space questions: We have our first question from Paul Frank (LoC): 2024-01-11 Metadata Management Meeting notes 😊

Suggestion: brainstorming discussion about how AI might be useful in Inventory FOLIO? Would someone from LoC be willing to be part of such a session?

Rita says: many of these capabilities are likely of more interest in public-facing interface, rather than in the staff interface

Ryan: My initial thought re: AI is using this in conjunction with MetaDB. There could be some real power there

Thomas: making it accessible to LLMs

Alissa: My colleague Jeremy Nelson gave a recent interesting presentation on some possibilities for AI and inventory (think creating brief records with chat gpt). 
I’m sure he’d be happy to share again.

Charlotte: A theme at WOLFcon 2024 (plus one from JE & LD)


Label of the Call number, eye readable indexFelix Hemme 

The German MM group met on 2023-12-11 Besprechungsnotizen MM and talked about the label for the eye-readable call number index (for both Holdings and Item record). We would like to propose to change the name from Call number, eye readable -> Call number, not normalized. The current label of the index has proven to be confusing for our libraries. Changing it to not normalized would set it in contrast to the normalized index. 

-This is not just an issue in translation, "eye readable" doesn't seem to convey meaning well in most languages

-Renaming a label in the UI is a minor fix, if we can agree what to change it to

-New name will be chosen in a Slack poll, then Felix will create Jira for the label change

UPDATE: Slack poll result as per March 11th, 2024:

Please note that the one downvote was only created by Felix as a voting option. We have 8 upvotes and 0 downvotes.

The change has been accepted by the MM SIG.


quickMARC: contextual field help

Christine is gathering requirements for contextual field help (dropdowns of available values per position) of the 008 and the leader, see Contextual Field Help

-For cataloging/editing catalog data in quickMARC

-Please provide feedback

-Where/how can we provide feedback on other quickMARC issues related to 008, e.g., display of blank vs. not present (these display the same so cannot differentiate) fields when editing/trouble-shooting? (Charlotte and Laura think this is a bug!) -Christie and Laura will write up a bug and label for Support

-First quickMARC meeting of the year is on 24 January for anyone who wants to attend


PC update

The Product Council had its meeting today (2024-01-11 Product Council Meeting Agenda and Notes). The Council heard presentations from Charlotte Whitt and Tim Auger. The goal of these presentations was to consider whether these modules are needed.

Charlotte presented on TCR-33 on mod-batch-print functionality. Many German libraries require that print notices be sent out to patrons to remind them to return checked out items. These are reminder notices. Charlotte presented how this works which you can view on the slides. The PC had many questions and will continue the discussion on slack. Hoping this will be approved for inclusion in Quesnelia.

Tim presented on TCR-35, TCR-36, and TCR-37 for the DCB Integration or open source resource sharing and Direct Consortial Borrowing.

Slides are available in the meeting notes (linked above)


Bulk Edit/List Apps Update

The BELA (Bulk Edit and Lists App) group met last Tuesday (2024-01-05 BELA Meeting Notes). There is a lot of functionality coming for Quesnelia such as bulk editing Holdings notes fields or Holdings electronic access fields. This group is also working on instance discovery suppress and staff suppress and working on being able to duplicate a list in the List App.

-Lists and Bulk Edit development is being approached jointly as the functionalities are interrelated

The question of whether users wanted to use the API or UI to make changes to large data sets came up. SME's thought it was important to be able to edit large data sets via the UI. If you have any thoughts, you can use the BELA Slack channel.

This group is also working on how to build queries that search for null/empty values UILISTS-87. If you have any thoughts, add comments to this Jira Issue UILISTS-87. The group is also looking for examples of queries which are being recorded on this wiki page.

-Felix notes that ERM/Dashboards already has the option to search for empty/null values


Data Import Update

The DI working group meet on Wednesday (2024-1-10 Data Import Subgroup meeting). We talked about meeting frequency and thoughts on what we need to discuss for this group. We will continue to meet weekly and incorporate into our discussions looking at bugs as well as new features. We need to work out what it means to work successfully and clarify requirements, expectations, and outcomes that meet our definition of working successfully. Then we looked at MODDATAIMP-879 where in the incoming marc srs duplicate 856s are deleted.

-Also want to work on documentation (currently in multiple different places)

-MODDATAIMP 879 is good example of feature that needs refinement in terms of expectations (e.g., how "duplicate" is defined)


Homework For Next Week's Meeting


Collect use cases for exporting/harvesting instance data direcly from Inventory with more than just abbreviated MARC (e.g. "indexing in discovery / opac"). Please add your use cases in advance to this wiki page: Export Use Cases (following item #16 in the list)


Chat