2023-09-06 quickMARC subgroup

• 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. 

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)