2025-08-07 Metadata Management Meeting notes

Announcements

MM SIG is back from its July vacation break 🧑‍💻🦸

Felix will update the .ics calendar invite on our main meeting page because it has already expired last December. The meeting duration will be updated from 90 minutes to 30 minutes.

Extending authority file configuration

@Christine Schultz

Christine led a discussion of the Umbrellaleaf feature https://folio-org.atlassian.net/browse/UXPROD-5212 which will expand the configuration of authority file capability.

Presentation included:

• Mockups related to new settings: slide deck:

• Talked through some of the additional feedback collected in this wiki page https://folio-org.atlassian.net/wiki/spaces/FOLIJET/pages/1146159105

Current functionality

• Ability to create local authority files with prefixes and base URLs, which allows users to create new authority records that can be assigned to this file.

Limits of current functionality

• Can’t duplicate prefixes (If a prefix is already used for an existing LC authority file, it cannot be used for a local authority file).

• Logic is looking only for the 001 or 010 for identifiers

Issues for Libraries

• Some libraries do not use LC standard files. (Local authority files may use same prefix as LC. For example, Polish libraries have an authority file with a prefix of “n”. However, LC also uses this prefix, and the current functionality does not allow users to duplicate prefixes or delete LC authority files).

• Some local authority files use more than one prefix. (Currently, users can only use one).

• For some institutions, the URI in the Base URL is not the same as the identifier of the authority source file. (Polish Libraries are examples of institutions that pull the URI from a different MARC field).

• Some authority files do not use a prefix in the Base URL, even though one exists in the identifier. (For example, VIAF includes the prefix “viaf“ in the 001, but the prefix is not used in the URL).

• Some authority files are identified in MARC fields other than 010 or 001. (For example, Universidad de Concepcion will be using the 024 field).

Potential enhancements

• Allow users to pick a MARC field other than 001 or 010 as an identifier

• Allow users to specify which MARC field to look for data for the Base URL

• Allow users to remove authority files with source “FOLIO”

• Ability to use multiple prefixes in one file

User interface with enhancements

• Addition of MARC field, MARC subfield, and MARC prefix fields. The combination of these fields will be used as the match point for the authority files instead of the prefix only.

• Addition of URI field and URI prefix (option to exclude or include prefix)

Slide Discussion

• Regarding the new MARC prefix field, Felix mentioned that GND does not use a prefix, which may be an issue because MARC prefix is a required field.

• Concerns were expressed with authorities in FOLIO being MARC-centric. For example, German libraries do not use MARC records or SRS. (German libraries do not currently use authorities in FOLIO, but this will be an issue if they chose to adopt this functionality in the future).

• Linking instances to authority records without MARC was brought up as a future possibility because the instance record has been enhanced to include authority id elements, such as contributor and subject.

• Christine confirmed that the MARC authority app is to store authority records in FOLIO, but does not preclude institutions from using authorities.

Feedback for https://folio-org.atlassian.net/wiki/spaces/FOLIJET/pages/1146159105

• This document is mostly based upon feedback from a Data Import SIG meeting.

• Christine would like the MM SIG to provide feedback by the end of next week or the Wednesday of the week after that.

• Regarding the 001 being editable, Charlotte mentioned that, in most cases, this field should not editable (definitely not in the UI). There is one use case in which a library switched networks and had to change instance HRIDs. This change was at the database level. (The 001 is like the instance HRID. It is unique, system-generated, and cannot be changed).

• Regarding examples of authority files where the identifier is only in the 001, Sheila mentioned that some local authority files migrated where the identifier was in the 907 field. Sheila’s primary concern is that the identifier is searchable.

Questions

• Q: How is this worked tied in to the Linked data app? (Linked data also has authority data). A: Christine has been talking to Alvaro and will bring in the citation team.

If time allows and someone leads the discussion:

MARC validation rules in Ramsons and their implications when upgrading

tdb and the SIG

This topic was postponed to a future MM SIG meeting.

Product Council updates

Charlotte Whitt

https://folio-org.atlassian.net/wiki/x/AYBWR

House keeping: WOLFcon; and PC meeting structure. Using meeting template.

Update the list of liaision for councils and SIG. Jennifer Eustis will continue as the MM-SIG representative. Charlotte will shift to the ERM SIG (and several other SIGs).

Update on prioritization. Pilot on the dash board. link to the Community Priorities Dashboard Development.

Discussed Community Top 5s. UXPROD-features in draft, must be fleshed out, if any development team is to pick up the work. (Status must be “Open” instead of “Draft”). The planning for Umbrellaleaf is happening right now in the different development teams. The deadline is August 22nd.

Discussion of https://folio-org.atlassian.net/wiki/spaces/PC/pages/931070022

• Several of these tickets are listed as status “Draft”. It is almost impossible for a development team member to pick up a draft ticket. Draft tickets indicates that there are necessary requirements to be discussed. POs must change the status to “Open”.

• Christine mentioned that there may not be time left to update these tickets to be included in Umbrellaleaf.

• Christine said the reorder of item records will be available in Trillium.

BELA (Bulk Edit and Lists App)

Jennifer Eustis

Data Import SIG

Jennifer Eustis