2023-09-06 quickMARC subgroup

Owned by Khalilah Gambrell
Last updated: Sep 06, 2023 by Christine Schultz-Richert
2 min read


























Date

 

Attendees (please add your name) Julia Corrice Raegan Wiechert Mary C Jackie Magagnosc Christine Schultz-Richert Khalilah Gambrell Lisa Lorenzo Lisa Robinson Jeanette Kalchik 

ItemPresenterNotes
AnnouncementsAll
  • Testing: October and November meetings > shift to evening hours to include folks who live in the West Coast, Australia, and New Zealand. 
  • Same meeting frequency and day. Time 4pm ET. 
Development updatesChristine

Sprint Board: https://folio-org.atlassian.net/secure/RapidBoard.jspa?rapidView=40

WOLFcon reflectionsAll
  • Energizing!
  • Lisa had a great presentation about authority control
    • There were questions on the $0 requirement:
      • String matching is not reliable
      • Helps support eventual extension to linked data
  • CSR: Attended a great working group meeting from the cross app interaction SIG on standardizing some search behaviors. Highlighted some gaps that may be filled by the advanced search modal in Inventory, but confirmed that there is UAT needed for the modal, mentioned that it could be "clunky"
Discuss MARC record validationKhalilah

Questions for the group

  1. What are your expectations for MARC record validation capabilities? 

RW:

  • Structural (required/repeatable/non-repeatable) 
  • Warn me but do not force me to change it. (ex. invalid ISBN) – sometimes I do not care if it is perfect 

LR: 

  • Validation on data import (ex. vendor records > Leader 05 issue)
  • Warn me but do not force me to change it  (ex. vendor records > Leader 05 issue) 

JC: 

  • Get a detailed error report 
  • Authority validation > suggestions via automated linking 

MC: 

Related to Authority validation: "I'd love that. too. I've come across a lot of invalid headings that were caused by typoes (ex. administrative laws vs. administrative law). Suggestions for correct strings when something doesn't match could be helpful for resolving these."

2. What is your current MARC record validation workflow? 

RW: OCLC validation with records from OCLC otherwise cross my fingers. 

JK: MARCedit validation before importing records. (Jackie states same for Cornell) 

LR: DI record validation could be a problem. 

3. Do you currently use a third-party tool for MARC record validation?

4. What is a common MARC cataloging error your staff makes that you would like to be solved by MARC record validation? 

JC: Incorrect indicators in 1XX/6XX/7XX fields 

JK: Handling legacy rules/standards must be considered (Lisa R: +1) 

LR: Spelling of subfield 2 codes in genre. (subfield code validation) 

Poppy features demoChristine/ Khalilah
  • Advanced search modal - UXPROD-4424 - Getting issue details... STATUS (CS)
  • Call number browse by type - UXPROD-3569 - Getting issue details... STATUS (CS)
  • Authority Control: Automated support/Heading validation - UXPROD-3874 - Getting issue details... STATUS (KG)

Future meetings agenda items / Action items

  • quickMARC - change to entering subfields (UX?/POC?) - Discuss next steps
  • quickMARC Error Handling overview
  • MARC in FOLIO features table: Update table to include JIRA links to provide more details. (KG)
  • MARC in FOLIO: Create a view that helps to answer this question - Can you implement today? (KG)

Chat