2022-03-31 Metadata Management Meeting notes

Date

~ 30 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
General
No subgroup updates
PC update


  • Notes from 2022-03-31 meeting
  • Thomas Trutt, member of the Prioritization Process Working Group, presented on the new proposed prioritization model → Presentation | Flow Chart:
    • Community ranking + PO ranking + SIG ranking, each rankings in one of the groups would be added, so that we end up with:
      • Institutional ranking: One of R1-R4
      • PO ranking: Will continue to do the PO ranking using a number value, e.g. 150 - 0. Charlotte explained that above 100 is highly ranked feature (when it comes to Inventory. The POs do use these number ranks a little differently.
      • SIG ranking: One of R1-R4
    • Qs: 
      • Does each individual get a vote, or each institution? → still in discussion
      • What about consortia? → Jacquie Samples could you please add your answer here? 
        Each member of a consortia is also a member of the FOLIO community, so to increase equity in ranking, the PPWG suggests that individual institutions should be able to participate in the Institution Ranking portion of the proposed process.  Discussions are still ongoing, but especially among the large consortia, there is interest in institution/library participation.  We are aware that individuals can also participate in SIG ranking, but that is not seen as a problem at this point.
      • what is the definition of "new request” what does that cover? → Gap in the list of features identified – covers new features and updates to existing features, e.g. change to existing functionality
      • The focus is on epic and feature level 
  • Felix suggest to circle back to this proposal in a couple of weeks
  • MM SIG liaison to PC. Call for a volunteer.

SIG membership. SIG charge document: Special Interest Groups

  • Talk about minimal criteria for MM SIG membership. Confluence Wiki account, regular meeting attendance
Release Notes/Changes

MM SIG Release Note & Other Highlights.

Add/Delete OCLC holdings

https://github.com/lehigh-university-libraries/folio-oclc-holdings 

The tool does three things:

(insert screendump here)

At Lehigh it's running every night at 2 AM ET. 

Configuration is detailed explained in the README.md file

  • Qs:
      • The instance status of "set" is applied by staff
      • Does it work with only 1 OCLC account
      • uChicago has a query to do this update
      • Do you have a check that the OCLC number is not on another record that is not withdrawn
      • issues with multiple OCLLs in the records. After single record import there will be multiple OCLC numbers in the record with and without the prefix. Lehigh is only taking the first one into account 
      • Lehigh is stripping the leading part of the OCLC number, and only search on the digits
      • Search on OCLC number is a known issue, and in Inventory it will be improved with Morning Glory
      • Instance status ...
      • Could you have the tool to pull records changed in the last 3 days? So there's an overlap so if it fails on day it would catch that record the next two days. Lisa answered: I'm pretty sure the answer is "yes". And Maccabee Levine agreed: You would just manually run the script for each day, passing in the date. See more in the paragraph Instructions in the READme file. 
      • The OCLC API will tell if you are giving it an old OCLC number. Do you report that out or doing anything else with it?
      • When you set your holdings, what does that mean? This is OCLC Connexion language, and means: Lehigh has send into OCLC, and OCLC has  recorded that Lehigh has this instance. 
      • Felix added that the German libraries do the same for international ILL via WorldCat but don't have to send holding by ourselfs as this is taken care by the Union Catalog provider

Community-created video documentationLaura E Daniels 

See App Interaction Meeting Notes for more information

  • Idea of community created video documentation brought to App Interaction from Acquisitions SIG
    • Specifically focused on cross-app workflows
  • Current documentation group is a working group and focused on written documentation
    • This sort of work is outside their scope
    • Is a Documentation SIG needed? (a broader discussion point, but feedback welcomed) - yes, it's a permanent task, and all agreed in that a new Documentation SIG would be great. Christie Thomas warned about ratifying thin thread implementations, or even work arounds. Many features still need to be enhanced and further developed. 
  • Short, targeted videos would be preferable to longer ones:
    • easier to create
    • easier to update if functionality changes
    • multiple shorter videos can be grouped together to represent more complex workflows
  • These are more appropriate for the wiki than as formal documentation (lower barrier to contribution)
  • There is value to sharing existing local documentation, no matter the language or local configuration

Does MM SIG want to contribute to a list of topics for which this sort of video documentation would be helpful?

Felix mentioned that such a list already exist in docs.folio.org - here you see the table of content, in the right pane. See e.g. https://iris.docs.folio.org/docs/metadata/inventory/

If so, would anyone in MM be willing to create/collaborate on video documentation?

Each given video documentation will need to be labeled with the given release and possible hotfix #

Will work on having a shared structure for these videos, and also wrap up the video explaining whether the work is thin thread, and is planned to be enhanced at a later point. 

Raegan asked if we could arrange a training session on doing demos. And Laura said that this could also be an excellent hands on session at WOLFcon.




Chat