2025-01-30 Metadata Management Meeting notes

Announcements

Call for new volunteers for note taking rotation.

• Contribute to the community in an easy way! With the rotating schedule, you only take notes about once a month. Sometimes less if meetings are canceled! It's pretty easy to get coverage if you have a conflict on your designated meeting day with your cohort of notetakers.

Alissa Hafele has made a Quesnelia Release Notes page for MM areas and would like feedback

Version history

@Christine Schultz-Richert

Questions about representation of repeatable fields in version history

Option 1: Bulleted list – will move forward with this option, with more mock-ups in future

Some of us find the bulleted list format easier to read

comment: changed from/changed to is a bit confusing, this aspect is clearer in the delimited version

Option 2: Pipe-delimited all on one line (clarification – pipe is not part of data itself, just part of display)

Some prefer the view with the pipe display since it mimics a MARC record structure.

concerns: pipe is sometimes part of our data; pipe as delimiter is known to cause issues (from other systems)

Questions & comments:

Could it highlight the changes somehow? So that the user can see that the name value has changed, but not the relationship for example. (this suggestion got several thumbs up)

 Is it possible to not include the bullet if nothing has changed? (for ease of reading)

I'm also wondering if it should not just display the field and value, but also the "subfields", or fields of an JSON object.

Does the modal show complete history? No – just what was changed at that time

Will it be possible to make version history optional? Yes, it can be enabled or disabled.

How far back will the history go? Is there a retention period? The retention period will be configurable.

Will there be a way to export the history? Audit log could be queried via API

How many changes are listed in the UI? Will that be configurable? Yes, will be configurable in settings.

(From Ryan) To clarify: number of changes shown on the modal will not be configurable and will show all changes in a version update. However, the default number of version history cards that load on the 4th pane will be configurable in settings (and the will always be a 'load more' button in the UI if there are more cards available)

--any idea how this might impact performance (number of logs has significant impact in DI, for example)

Will it be included if change was made by an individual user vs by another app. e.g., Data Import or Bulk Edit? (This suggestion got several thumbs up) Source is not part of the data captured <need to clarify this>

What does the order in the pipe delimited list mean? It’s a little confusing. Especially for subject examples. Right now it’s the order it appears in the Instance data.

Would this include $0’s in MARC? Yes, intention is to have same functionality for MARC data.

For the UI in the detailed view, I would prefer to have the data element type (ISSN), (Personal name) in a new column and not in the same field. It looks a little busy.

Review of parking lot topics (what needs to be moved to implementers page)

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

MM SIG Parking Lot

issues in Parking Lot that are still open will be moved to new Implementers Topics page (if they are not already there)

PC updates

Charlotte Whitt

2025-01-30 Product Council Agenda and Meeting Notes

Announcements:

• SIG Reports 2025-01-20

• Update on Sunflower release schedule Sunflower (R1 2025)

Draft statement on Eureka timeline:

• PC has shared their draft statement on Eureka timeline with the CC. The CC’s text is posted here.

• The PC and CC want the statements to be aligned. With the timeline for Sunflower being postponed to end of April, there is time for the Early Eureka adopters (GBV, Index Data, TAMU) to wrap up their test on implementation.

Revisit ways to leverage Jira to support PC’s workflows for endorsement of new functionality:

New Jira project: Product Council Endorsement (PCE)

Jira KanBan board: Product Council Endorsements

The PCE tickets can be raised by Product owners, or by PC members/PC liaisons. The PC has the strategic responsible for new functionality in FOLIO. The PC will review this new process in 6 months.

BELA (Bulk Edit and Lists App)

Jennifer Eustis

No Meeting this week.

Data Import Working Group

Jennifer Eustis

No meeting this week.