2022-08-18 Metadata Management Meeting notes

Owned by Felix Hemme
Last updated: Aug 18, 2022
4 min read

Date

around 25

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
Lynne Fors
Announcements


Cancel SIG meeting on Sep 1st due to WOLFcon

WOLFcon 2022

  • Session on Product owner work and recruiting new POs held by Charlotte, Laura, Julie Bickle, and Khalilah - Wednesday 8/31/2022 4:00 PM CET.
  • Session on build and support record deletion will be held by Charlotte and Khaliah - Friday 9/2/2022 11:30 AM CET.
  • Data import subgroup will be held
PC update


2022-08-18 Meeting notes

  • Status update on Course Reserves app
    • very little work done on it since 2019
    • needs a Product Owner

Jennifer Eustis 

From General Channel and Oleskii Petrenko:

All changes are updated at Morning Glory R2 2022 release page - https://folio-org.atlassian.net/wiki/pages/viewpage.action?pageId=5210570
Just to remind, Morning Glory bugfix dashboard - https://folio-org.atlassian.net/secure/Dashboard.jspa?selectPageId=12403.

Morning Glory R2 2022 GA date is shifted forward for 5 weeks.

Below you will find some details:

  1. Morning Glory R2 2022 Bug Fix period is extended up to September 9
  2. Morning Glory R2 2022 Bug Fix deadline is September 9 - middle of Sprint 148
  3. Next 2 weeks are for stabilization testing - September 12 - September 23 (mid Sprint 148 - mid Sprint 149)
  4. Morning Glory GA date - September 26


P.S. Release plan for Nolana R3 2022 is not affected for now. CAP planning group will review Nolana R3 2022 development state at the middle of September.

Impact on Nolana development unknown at this point.

User feedback on field label: "Effective call number string"

+ move shelving order field

Felix Hemme on behalf of Erin Nettifee

Hello Metadata Management! Here with a question: can relabeling this field be reconsidered - from "Effective call number string" to "Effective call number"? I think it would flow a bit better in terms of teaching/training people on what to look for. Thanks for considering!


Shelving order field move:

Link to slide deck


Q1: Display of shelving order. Can it be moved to a different location in the item record?

EN would like to move it to another location on the item record. It's very confusing as to what it is and means. Possibly move to top of screen by effective location and effective call number string? Location accordion? Administrative data accordion?

Also very confusing to catalogers, it looks like a call number but isn't one. 

Shelving order is system generated. Can be helpful for troubleshooting shelving order and call number browse. Used to sort LC call numbers in spreadsheets. Used in LDP reporting (excludes a lot of libraries that don't have access to LDP from their hosting provider).

Do we need to see the system generated shelving order at all?

Could shelving order be exportable?  Not now, but maybe in the future

LD: prefers to be at bottom not near any other data

RS: Could there be a toggle in settings to display or not?

LD: Action > view shelving order? Maybe a permission to hide to most of Cornell's users, only needed for a select few?

Add a information "i" to shelving order to explain what it is would be highly welcome.

Decision: to move the display on the "Item record screen with the effective location for item" and "effective call number string"

What do we do about Holdings records?

  • Shelving order not functional yet
    • MODINVSTOR-274: Add shelving ordering to holding records
    • need to be consistent between holdings and items
  • Shelving title?

UX mockups are needed to make a final decision.  Hope to see in Nolana.  Revisit next week, 25 Aug. 2022

****

Q2: "Effective call number string" vs. "Effective call number"

Move discussion to next week, 25 Aug. 2022

UXPROD-3713 - Bulk Edit - in app approach - item notes

Magda Zacharska 

Related questions:

  1. What are the most common scenarios for updating item notes?
    1. All note types needed
    2. Charlotte: Making sure the language used is consistent
    3. Jackie: Admin notes to series, why we did some sort of action or need to do a particular action, correct legacy notes (update language or delete them)
    4. Ryan: Retention policies for earlier/latest editions of monographs in notes
    5. Robert: Check-in/check-out notes for course reserves linked to temporary locations for reserves
    6. Christie: updating item status and adding a note (ex. withdrawing duplicates project); electronic bookplate (add a code, delete a code, or change a code); staff only
    7. Ann-Marie: I was working with Mich State yesterday on holdings note, but could see a similar use case for item notes: they added a more specific note type and then needed to bulk edit a bunch of records to change the note type from a general note type to the more specific one, but keep the note data the same. Only changing the type.
    8. Christie: Human error - if someone did something wrong for a really long time and it needs to be corrected
  2. Can the support for note types be prioritized?
    1. Administrative
    2. Check-in and check-out notes
    3. Item note types – are there some note types that are used more frequently?
      1. Binding
      2. Copy note
      3. Electronic bookplate
      4. Note
      5. Provenance
      6. Reproduction
      7. How often would the library add their own note type?
  3. What update types will need to be supported? All should be supported, will follow up with a survey
    1. Add new note
    2. Find and replace
      1. Felix: would it include regular expressions?
    3. Find and change
    4. Remove all
    5. Change note type


Magda will follow up with a survey in Slack

Chat: