2023-01-26 Metadata Management Meeting notes
Date
Attendees
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
Notetaker | Christie | |
Announcements | ||
PC update |
| |
Review of the parking lot | Continued from last week MM SIG Parking Lot (restructured) The previous MM SIG Parking Lot (Old) has been renamed and moved under the new parking lot. Discussion about whether the topics are still relevant and need to be added to a future agenda. Possibly create an archive for the topics that are retired from the list Referential cataloging - term used early in the project - copy cataloging / pointing to external cataloging. We have already made a lot of decisions that have moved us away from this model of cataloging within FOLIO. Suggestion that we remove this from the list and if we do need to revisit it the SIG should redefine our needs based on the current cataloging ecosystem / roadmap within FOLIO. Where does discovery come from - Is this done or are there other discussions around suppression and where discovery data comes from. There are future questions about non-marc sources of data and what elements are missing for Discovery. Maybe reach out to the discovery working group in FOLIO for periodic updates? Maybe MM Sig needs a liason to the discovery group to make sure that communications and discussions are in sync. Is there anyone in the MM Sig who is on the discovery working group. (Confirm with Jenn Colt that she will provide updates to MM Sig from the Discovery group.) Discovery Integration Subgroup (Is the group still active? Anecdotal evidence suggests it is though the wiki page suggests that the group was intended to end late in 2022.) Protecting local edits - There are system wide protected fields and the ability to over. Still a discussion topic for data import subgroup. Not yet is there the ability to protect a field just in one load, nor are there protected fields for editing in quickmarc or inventory. Multiple graphical representations - this is still important. There are still questions about how exactly we want this implemented. Perhaps we need to involve technical council and entity management? And our FOLIO colleagues in China? How do we have a single entity with multiple scripts available. Right now we have to represent the two scripts as two different scripts. We need more discussion in MM SIG before bumping this up. Once we have the discussion we can determine who we need to push the discussion out to. Linking fields and bound withs - Is there ongoing work? Some of the relationships are working. We should revisit to collect all relations that we could have so that we identify relationships that are missing. Question: How does this relate to requesting items? Make a new topic for related instances and loop in the PO for requests? Inventory search / symbols - from before elastic search was implemented. Still a discussion, but maybe we need to wait until after Orchid to see if still a problem. Need to consider this from the perspective of languages other than English. Syncing holdings and item data with bibliographic data - Has not been addressed. Maybe a future discussion and possibly referred to entity management. Search result display issues - We all know that this needs to be discussed and that Charlotte is actively working on some aspects of this. Results display needs to be given more development resources. Work also needs to be done at the tenant level if not the individual user level. Topic should be escalated to the PC so that it is high on their list when they are defining the roadmap. Potentially also reach out to the implementers SIG. Current implementation is thin-thread implementation from 5 years ago. It is blocking a lot of feature development. Ordering of holdings and items on records - Many different opinions on what the default sort order should be and it should be decided by the tenant rather than the FOLIO community. Also an issue about sorting repeatable properties within the holdings and item records. (Also true for instance records?) | |
Preliminary item status work | (OLD ACCOUNT) Erin Nettifee | - UXPROD-3475Getting issue details... STATUS Questions about keeping Data import and Inventory behavior in sync - Data import item status restrictions
There is no identified release or identified resources for this. Defining issues in Jira provides a framework for identifying the resources and that is what is being done now. It is not possible to change an item status to Available from within Inventory. There are use cases for this. Changes are to the Inventory UI and would allow to change to Available when item record status is in the list. Two stories: one for Inventory behavior and one for permissions. There is a question about whether this work may be more complicated given any dependencies on the underlying item statuses. Given the focus on using check-in to make items available, should we consider leveraging the check-in api from within Inventory to check something in? Another question came up about the business logic associated with receiving - on order to in process. Will this impact any of that business logic? Breaking workflows is also the possibility for other statuses that have workflows associated with them. Another concern was raised about the prescriptive nature of this. If there are no system-wide ramifications then maybe we should implement in a way to allow institutions to determine their workflows rather than they system. |