2024-07-25 Metadata Management Meeting notes
Meeting time: 11:30 AM ET, 05:30 PM CET, 04:30 PM GMT
Meeting URL: https://zoom.us/j/527543204 . The meeting password can be found here.
Date
Jul 25, 2024
Note taker
Laura Daniels, Lynne Fors, Alissa Hafele, Natascha Owens
Recordings
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
Item | Presenter | Notes |
---|---|---|
Announcements | From Christine in Slack:
The WOLFcon session list has been published: https://wolfcon2024.sched.com/ | |
E-resources in Inventory and their connection to the ERM apps |
| Continuation from MM SIG meeting June 13th, 2024. Result of this meeting: ERM and Inventory should be more closely connected to support use cases of the FOLIO libraries. Plan for this meeting: Presentation of concept that has been discussed in the App Interaction SIG https://folio-org.atlassian.net/browse/UXPROD-4785 App Interaction SIG - Linking between Inventory and Agreement lines working group (WIP) (@Sara Colglazier , @Charlotte Whitt , @Owen Stephens) and discussion/feedback in our SIG. Sara shared need for connecting records in Inventory to Agreements & Licenses; Orders don’t always exist for the resources represented by the Inventory records Overview of proposal: these links would be appropriate in Holdings records, new accordion would be added toward bottom of Holdings, called “ERM information,” it would look similar to existing Electronic access with slightly different elements & would not be intended to be public facing; repeatable, could be populated manually or via Data Import -this approach leverages a lot that’s already in place, could be added to Elastic Search/as filter, could be incorporated into Bulk Edit & Lists
Christie asks: Charlotte: Owen had proposed a look-up option, but that is not what’s seen as needed now and would add more complexity Jennifer: in case where there are multiple agreements for the same holdings, would like stronger connection than a note; would prefer to see us manage resources like this as sets rather than via individual holdings Christie: thinking about workflows for batch loading and wants to highlight Felix’s comment; storing and displaying the URL is confusing, would expect it to store the UUID to represent this relationship, just like is done to connect, e.g., a holdings to a PO – several of us agree with this -Sara says that storing the URL is much less complicated; also, this is not intended for management purposes, rather for, e.g., trouble-shooting; will work with batch processes Christie: concerns about scalability; e.g., for collections that are frequently updated, with records that may be part of more than one collection, how would we build something that would match to the right agreement lines? This feels like a thin thread, not a viable long term solution for the community -Chicago’s current workaround (based on workflows from UMass Amherst & Cornell): file of records from WorldShare collection manager, updates from multiple collections – use a MARC 9xx field to identify each collection, mapped to a Collection ID (local Inventory identifier), use same names for the agreement lines & collection IDs. Inventory link for all titles in each collection embedded into agreement line. This doesn’t provide a direct link from Inventory to Agreements. Felix adds: We are doing something similar as demoed by Christie: We store the ISIL code as dedicated instance identifier and also use the ISIL as the agreements alternative name. It is not ideal, but at least tells our staff the agreement through which we have access to the resource. Felix asks: from a workflow perspective, to you add the same URIs to all the records in a file? And would this be something that could be added via BulkEdit in future? -Yes, if file has mix of platforms, would need to set up task in MarcEdit to add different URL depending on which agreement. And yes, ideally we could retrieve a set of results via Lists and add or update these URLs via Bulk Edit (rather than round tripping records) Ryan: has been reviewing the feature & the slides (both linked above); needs better understanding of use cases and how this might be approached on the implementation side; from what’s been presented today, it sounds simple at a high level, but complication could come in based on how to best support common use cases; also curious how some work Owen has done in Agreements might be similar Khalilah: also wants to think about this more, understand all the components that would be needed, and other questions, e.g., does the order of these links matter? what happens when a holdings is moved? should this impact discovery? Jennifer: I think disclosing the terms found in licenses is useful for discovery and patrons Sara: related issue: URL relationship element is not searchable via query search (occurs in Instances, Holdings, and Items) Next steps: Khalilah and Ryan will think further about the request for connection between Inventory & Agreements/Licenses and bring back any further questions to individuals or the SIG; don’t anticipate getting to this in a near future release
|
|
|
|
|
|
|
PC updates | @Charlotte Whitt | 2024-07-25 Product Council Meeting Agenda and Notes Announcements: New PC co-chair is Caitlin Stewart (LOC). Alexis Manheim (Stanford) continues to be the other co-chair. WOLFCon PC meeting agenda planning: Planning for this years PC shoulder-to-shoulder meeting by following similar approach as last year. The PC will revisit and re-group the work on FOLIO PC Sub Group Supporting Enhancements and Improvements Updated list with all SIG Liaisons. There was a talk about the Sprint Review Demos (which we used to do) versus that some SIGs (e.g. MM and RA) invites the POs to come and do demo of new feature development in advance of a given flower release. The PC would be interested in being notified by the PC liaisons on when new functionality was presented, and then the PC members can watch the recording. Future topics: No news at this point
|
BELA (Bulk Edit and Lists App) | Jennifer Eustis | Bulk Edit and Lists App are implemented the process for community input:
|
Data Import Working Group | Jennifer Eustis | No meeting this week. |
quickMARC Subgroup update | Raegan Wiechert | All meetings for June and July have been cancelled |
Chat