[Koha] Ideas wanted for cataloging QA utilities

[Bales (US), Tasha R]

Thanks Carlos!  I guess I just need to find the time to work on this idea, and will probably do a combination of real-time checking and reports.  At least it's easy to avoid leaving mandatory fields blank in Koha!


Tasha Bales


-----Original Message-----
From: Carlos Lopez <clopez at dml.vic.edu.au> 
Sent: Wednesday, November 2, 2022 17:12
To: Bales (US), Tasha R <tasha.r.bales at boeing.com>; koha at lists.katipo.co.nz
Subject: [EXTERNAL] RE: Ideas wanted for cataloging QA utilities

EXT email: be mindful of links/attachments.



Hi Tasha

Bite your tongue! Fixing errors in old records kept me busy during the 2020 lockdowns!

Honestly I think this would be a good idea, even if the interface only showed some kind of alert according to a (predefined) set of rules. The MARCEdit MARCValidator is a good example (it even reports on invalid tag indicators). As you say, we can always write SQL reports to pull individual (repeated) errors, but it would be nice to spot these 'live' too.

With kind regards from the Dalton McCaughey Library Team

Carlos Lopez

Dalton McCaughey Library | 29 College Crescent, Parkville, VICTORIA 3052
Ph: 03 9340 8888 ext.1 | library at dml.vic.edu.au | library.dmlibrary.org.au 

-----Original Message-----
From: Koha <koha-bounces at lists.katipo.co.nz> On Behalf Of Bales (US), Tasha R
Sent: Thursday, 3 November 2022 1:05 AM
To: koha at lists.katipo.co.nz
Subject: [Koha] Ideas wanted for cataloging QA utilities

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.


Good morning,

I'm interested to know if anyone has developed tools to help copy catalogers quality check their work in real time.

For example, at a long-ago conference, I saw a librarian present Windows batch scripts they'd created to check cataloging in Millennium.  I don't recall the specifics, but for my purposes, I'd be interested in doing checks such as the following:


  *   Compare 260 to 008
  *   Check for the presence or absence of important fields in both bib and item record
  *   Check for agreement between item type and notforloan value

I could do the above with SQL, but I'm trying to get closer to first-time quality by catching the errors as they occur (maybe I could use jQuery to link a prebuilt report that would check the bib I'm currently viewing?).

Options might be Jupyter notebooks, or jQuery.  This is my first time working with a staff client that is a web application, so I'm not sure what is realistically possible or what anyone has already come up with (Google is not helping).

Any food for thought is welcome.  Even if I only "caught" errors such as impossible publication dates (e.g., 2039, 202, etc.), that would be a help.

Thanks for your time and consideration,


Tasha Bales


_______________________________________________

Koha mailing list  https://urldefense.com/v3/__http://koha-community.org__;!!DVrgiXjqvl2yLjg!ZWXEShPXQpMgfNVPNXBmLGI1jXVHXieyFdvpzDpP9v1W5YBw2ROfyN_Un9bLWiEWrRktJE-VEiEVkXRKnleTpherYdgH$
Koha at lists.katipo.co.nz
Unsubscribe: https://urldefense.com/v3/__https://lists.katipo.co.nz/mailman/listinfo/koha__;!!DVrgiXjqvl2yLjg!ZWXEShPXQpMgfNVPNXBmLGI1jXVHXieyFdvpzDpP9v1W5YBw2ROfyN_Un9bLWiEWrRktJE-VEiEVkXRKnleTplSiTy28$