2024-12-12 Metadata Management Meeting notes

Announcements

No SIG meetings December 19th, 26th 2024 and January 2nd 2025.

App Interaction (Cross App) reviewed our requirements for multiple graphical representations (https://folio-org.atlassian.net/issues/UXPROD-4856) and the Proposed Data Model. No additional concerns were raised. It was suggested that other POs be given as much lead time as possible, when changes like this (i.e., changes to the data model) are implemented, to figure out if/what changes are needed in other apps. Of note: we have been talking about this in MM since at least 2019.

Reordering of Holdings and Items

@Laura Daniels

Slides

Items

Item default sort is by barcode

We can do an on the fly sort which we can't save and is not currently working as well as it once did (see slides for examples)

Enumeration needs to sort properly before we can tackle the other needs we find necessary

We need to be able to sort items effectively 

We don't want being able to manually reorder items be used as a work around for sorting effectively 

We want some sort of icon/indication that sort order has been changed  and saved

With the paging that was introduced (100 at a time), in order to sort effectively we will need to be able to pull up a view of all associated items; in that view we need the same sorting options we have now, some way to manually reorder items; option to save the order 

Additional requirements: need permissions associated with this because we don't want everyone to be able to change the saved order

Khalilah: can you describe the pain points of not having this functionality available for items? Answer: this is an issue for people who work with material with multiple items; someone is receiving a serial and is adding new items but can't put items in a logical order — difficult to see if there are gaps or duplicates; at Cornell, what our patrons see in public catalog is how items are ordered in FOLIO; 

Jennifer: display summary is new with new serials app (new item property)—would this be included in our sorting? Answer: we had not considered but yes it should be

Jennifer: if you find that you want to sort something in folio, is the goal to have that sort preserved in your discovery system? Answer: yes, this order needs to be able to be communicated to external entities like discovery. Jennifer: noticed that UIIN 2688 is the only one scheduled, none of the others have been. As a group what is our priority for these tickets considering other tickets that also are considered a priority. Answer: This is exactly why we are raising this, these are not scheduled and we are trying to gauge interest in the community and the possibloity of funding this as a group since this is a huge pain point for staff.  

Felix: If the item records would contain some kind of occurrence element, it would be good to have a way to change it directly, w/o having to move them around with the arrows or via drag and drop.

kay:Re: pain points: At Stanford, we have serials with hundreds of items, sometimes approaching 1000 items. Staff processing gifts of older material are trying to check the items to see if the gift is a duplicate. The default sort order and the inability to sort by enumeration correctly makes this task extremely difficult. To the point that it can take half a day to check items for 1 or 2 titles

Nicole: discovery subgroup; this is a huge pain point for them right now, so this is of great interest to them.  Consider a box that says 'save for discovery'.

Nicole: Is the order of bound withs being considered? Answer: we did not talk about it, but it should be considered at some point—probably out of scope for now

Felix: regarding bound-withs—we have considered if it should be possible to reorder but it has been put on the backburner--there is a workaround by removing a bound-with and then adding it again to change the order

Holdings

Currently there is no default for ordering; we want to know which elements would be desirable to sort on? 

We also want to be able to sort these manually and save the order

We don't necessarily need a column list sort like we do with items; just being able to sort manually would be sufficient

Holdings statement

Display in the order they are created—want to be able to move them up/down (perhaps like we can do with fields in quickMARC)

Not certain which JIRAs should be focused on?

Sorting Items (which of these?): UIIN-2688: Refine scenarios and verify sorting of items enumeration by numberBlocked

MODINVSTOR-1142: Item sorting is not working for some columnsDraft

Reordering item records: https://folio-org.atlassian.net/issues/UXPROD-1625

Reordering holdings records: UXPROD-1635: Order/sequencing of holdings on an instance record. Re-order Holdings recordsDraft

Reordering holdings statements:

UXPROD-3178: Inventory. Holdings record. Reorder holdings statements, and holdings statements for supplements, and for indexesOpen

Reminder: we can now vote as individuals on these JIRAs

If anyone thinks the JIRAs need improvement, plese let Laura know

Also, feel free to make comments directly on slide deck

Khalilah: if we had a team to work on this, is the "next steps" slide listed in prioritized order?  Not necessarily but fixing sort as it used to work is top prioroty, then manually sorting items comes next (so item sorting is more of a pain point than sorting holdings)

Ramsons Update

@Christine Schultz-Richert

Ramsons release recap

MARC record validation rules: tenant level, can be configured via api; specify which rules should create a warning and which should fail to update record; help hyperlink next to error messages can also be configured at tenant level

010 validation (LCCNs): by default, this feature will be disabled ; if turned on, prevents duplicates; new icon next to 010 to search by LCCN; validation of structure of the identifier (gives fail error if not structured correctly)

Browse by classification on instance record - looks similar to all other browse instances; supports use cases like shelf listing on bibliographic call number; can browse all classifications or split by LC and Dewey

Sorting and filtering by dates: three new fields in the schema; new column called 'date' in results list that can be sorted ascending/descending; also, a new filter by date

Diacritics and case insensitivity support; sorting is now working as expected regardless of diacritics

Subject granularity - browse; adding subject source and type to schema; added to filters

New index for place of publication 

Additional updates:

from view source you can now go directly to edit marc and export record;

new keyboard shortcuts

PC updates

@Charlotte Whitt

2024-12-12 Product Council Agenda & Meeting Notes

Announcements:

Presentation on Linked Data App by @Doug Loynes - [link to slide deck - shared with the Linked Data SIG]

Doug presented the planned work on Linked Data App for the PC back in April. Today Doug showed real work in the developer environment. The Linked Data editor use web forms for editing. The editor is in sync with Inventory. The current work is limited to monographs only, so work like serials, motion pictures etc. will be possible beyond Sunflower.

FOLIO 18-month roadmap:

Insert screens with editing screens Inventory. Only records original catalogued in the Linked Data app (source ID = LINKED_DATA) or records with underlying MARC records (source ID = MARC), can be edited in the Linked Data app. Records with source ID = FOLIO can not be edited.

It is possible to create instances i 3 ways:

• blank form

• edit an instance

• duplicate an instance

Linked Data app will be incl. in the Bugfest Sunflower environment. End user documentation will be available in docs.folio.org.

Linked Data app to be integrated with the MARC Authority app.

Linked Data app and Locate (EBSCO’s discovery solution) is sync’ed up. Discovery solutions like BlackLight and VuFind can access the Inventory APIs for Instance records. This will be enhanced at a later phase.

The BibFrame Lite in Data Graph Storage. BibFrame Lite is now renamed to Builde. The code is documented on GitHub. Builde can be integrated with other Linked Data editors.

As follow up on today’s demo Doug and Gloria will send out a demo with a clean version of the current workflow.

From Laura:

Encourages everyone to watch the recording of this meeting

And if anyone has questions/comments about Linked Data in FOLIO, remember that we have the LoD (Linked Open Data in FOLIO) SIG now. You are welcome to join any of our meetings!

Linked Open Data In FOLIO

the next meeting is tomorrow at 10am Eastern

BELA (Bulk Edit and Lists App)

Jennifer Eustis

2024-12-10 BELA Meeting Notes

Data Import Working Group

Jennifer Eustis

No meeting