Skip to end of banner
Go to start of banner

2022-10-27 Metadata Management Meeting notes

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 26 Current »

Date


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
Lisa McColl
Announcements


Sharon Wiles-Young is our new PC liaison

Charlotte Whitt  reported that yesterday there was a meeting of the Entity Management Working Group. The group discussed how to plan and organize. The result was the creation of two subgroups: a group that will do an environmental scan and another that will work on updating the list of use cases.

The group will report bi-weekly to the MM SIG

PC update
  • Duke and GBV are funding new work on Serials Management.

Owen Stephens did a great demo of the planned work. Slides are at

Scope: They will start with print serials in the area of predictive check in and receiving. Action item: They will meet with the Acquisitions SIG. 


  • Community Council report: Paula S. reported that the FOLIO finances are in good shape and added a wiki page reporting finances; met with the LOC about engagement with FOLIO project and slides are here 
  • Documentation: Marcia's contract is over. The Community Council will fund her for another six months. Martina will be the liaison to that documentation team. The team will work on a succession plan.
  • The CC is looking at onboarding people involved in the project - get more testers, more POs. 
  • Kirstin mentioned the resourcing group is meeting. They have three scenarios to propose to keep FOLIO sustainable
  • Volunteers to host WolfCon?
  • TC - needs to redo the review process due to growth of FOLIO scale
  • Harry talked to group about dashboards and Jiras and releases/bug fixes. Check Support SIG for more info.

Thank you Sharon for updates from multiple councils! 


MM SIG Release Note & Other Highlights


Misc. bugs and issues related to the implementation of Holdings Source ID property. This element was implemented to support the new work on maintaining Holdings record in MFHD format in quickMARC. The implementation of Holdings Source ID (not required, not repeatable) is different from the original work on Instance Source ID (required, not repeatable).
It will be helpful to get a small MM-SIG working group to review, and decide on if any change of the spec should be pursued.

Just a fyi too: a holdings source identification and cleanup script was created by the Folijet development team for Kiwi or later. This script can be found on on the FOLIO wiki - see: https://wiki.folio.org/display/FOLIOtips/Scripts+for+Inventory%2C+Source+Record+Storage%2C+and+Data+Import+Cleanup

with additional details here: https://wiki.folio.org/pages/viewpage.action?pageId=79466342 


UIIN-2208 - Holdings source ID bug discovered by the bulk edit working group. Hope is to get this fixed in the next couple of weeks. If created in the UI then the source is set.  "But only in the UI. It will still be null in the data." (Christie via chat) Charlotte suggests the that SIG members propose a solution to present to the developers. Volunteers: Jenn Colt, Jacquie Samples, Christie Thomas.

Christie added the migration script will not correct all of the problems. Holdings created by the following do not get the correct source

    • Lehigh Order Import app
    • NCIP holdings creation
    • Fast adds

Causes problems in Inventory UI. Causes reporting issues.

Christie In chat, "that is a good question. right now we can edit all of our holdings in the ui regardless of what the holdings source is."

Jenn in chat, "It translates null to what the instance had. But you can still edit them in ours."

MODSOURCE-559 - If you use OAI-PMH this will affect you.

Inventory UX

Topic 1: Review UX mock up, and gather possible new requirements on Inventory hierarchical display (UXPROD-491) > slide deck with proposed UX mockups:

Kimie Kester  was not able to attend the meeting, but will listen to the recording.

  • The mockup above was created a year ago.
  • Felix added that there are currently no resources to go towards this, so this is preliminary work. Christie, via chat, "That is a really good point. I don't think there is a development team for inventory any longer? How is the project going to address that?"

  • Jacquie (in chat) - "So, we can change all of those older choices and update our vision altogether since nothing has moved forward in development, right?"
  • Rita ask about the sorting of holdings and items. 

Chat comments:

From Sara Colglazier (MHC/5C) to Everyone 12:08 PM
Could the Holdings Statement info be displayed even when collapsed?


From Christie Thomas (she/her) to Everyone 12:09 PM
I may be getting ahead of this, but I cannot remember if we will be able to sort by the different instance / holdings / items properties?


From Natascha Owens (she/her) to Everyone 12:11 PM
I've always been very apprehensive about the "card" display--I find it very difficult to hone in on the info that I might need depending on my search.  With a multicolumn list I think it would be easier to sort and see what I am looking for.


From Marmot User Services to Everyone 12:12 PM
+1 Natascha


From Felix Hemme (ZBW) to Everyone 12:13 PM
Sara, we'll make sure your question will be included in the notes!


From Jenn Colt to Everyone 12:13 PM
HRID


From Christie Thomas (she/her) to Everyone 12:13 PM
+1 to HRIDs.

Sara suggested adding an option of "Open all the item" as well as included volume an enumeration details. 

Christie's comments in chat (received many +1)
"I still do not understand how we will be able to sort the results list.
Which information is displayed should be customizable by the institution since we do not all use the same properties in the records."

Rita noted that we have not talked about sorting holdings.

Christie - How will we make sure the results are relevant - when wanting a list of items, the current results list instances, for example.

Jenn wondered if approaching the "direct" search first would be the best way. Example of "direct" search result




Chat:

From Jenn Colt to Everyone 12:19 PM
When we refresh the 
From Ryan Tamares (he/him) to Everyone 12:20 PM
to what Sara commented on— we have some titles in our collection that have as many as 8000 items, so the consideration of information displayed is super crucial
From Jessica Janecki to Everyone 12:20 PM
Is there any easy way to dump an item list (with item data) into excel?
From Ryan Tamares (he/him) to Everyone 12:21 PM
*I stand corrected, some titles have over 10k items
From Colin V. (he/him) to Everyone 12:24 PM
I feel like the card result approach works best for Instance searching.  When I'm searching for holdings or items, I might only be interested in a subset of holdings or items attached to an Instance. This subset bit makes display and sorting in those segments tricky.
From Jessica Janecki to Everyone 12:25 PM
Charlotte, are you saying a known item search takes you directly to the item?
From Jenn Colt to Everyone 12:26 PM
If searching an HRID or barcode took me directly that record it would solve 90% of my problems because I get sent hrids constantly for troubleshooting
From Christie Thomas (she/her) to Everyone 12:26 PM
+1 Jenn Colt
From Jessica Janecki to Everyone 12:27 PM
Jenn, my team does this sort of troubleshooting in our current system constantly.
From Natalie Sommerville to Everyone 12:27 PM
+1 Jessica
From Jamie Jesanis to Everyone 12:27 PM
It would be useful to maybe have buttons for "Select All Items", "Select All Holdings" on the search results screen. Or maybe the ability to display only items or only holdings.


"Those of us at Chicago rely heavily on search results to assess our data and bring our attention inconsistencies in that data.  We are not necessarily looking to zone in on a given title.   As someone who works with serials held in various formats,  it's very helpful to have a clear list of results that includes identifier, title, corporate body, date, format, that I can sort."

"Customizable multi-column list" result was expressed as a desired result. Christie asked can we implement this in a way that institutions could decide what display

"Would a multicolumn list be better for holdings/items and card results for Instances?"

Should there be a different UI for different types of searches

Charlotte will talk to Kimie about listening to this recording. Incorporating UI standards from other apps. 

Action: Please go over the slides one more time and give feedback. Felix suggested in addition to looking at the slides, perhaps propose high level requirements, such as cross entity searching (search in Instance, Holdings, Items together)



Topic 2: Identify records in result list > issues and pain points 













Chat:


  • No labels