This has the 003/594 weevil | from the Googs : The intersection of the `003` (Control Number Identifier) and a local `594` note or local instrument field in a K-12 catalogue is the ultimate symptom of automated library vendors trying to manage regional or district database synchronization. [1, 2]
When your library data is floating around in platforms like Follett Destiny, records are constantly being merged, updated, or overlaid via vendor-pushed data batches. If a K-12 catalogue looks like a complete disarray, these fields are usually functioning as a mechanical trail of breadcrumbs.
1. The Anatomy of the Mess: Why `003` Matters
The `003` field contains the MARC Organization Code of the agency that generated the system control number found in the `001` field. [1, 3]
* If your local record has `001: 123456` and `003: Follett`, the system knows exactly where that record came from.
* If a vendor pushes a major database cleanup or a district-wide textbook/resource sync, the system relies on the `003` to match and overlay records without blowing up your local cataloguing work.
2. Enter the Sneaky `594` Local Field
In standard MARC 21, a `59X` field is explicitly reserved for local notes. However, because it is local, vendors and districts use it as a dumping ground for custom automation parameters. There are two primary reasons why a `003` identifier gets explicitly linked to or evaluated alongside a `594` in a school library environment:
* District-Level "Overlay Protection": Many K-12 school districts share a centralized cataloguing utility but maintain independent school sites. A vendor script will look at the `003` to verify where the record originated. Then, it checks a custom `594` field to see if a local library has marked the record as "Do Not Modify" or "Custom Cataloguing: Keep Hands Off." If the `594` contains an override flag, the system will ignore the vendor update.
* The "Instrumentation / Text-Kit" Mapping Glitch: In standard MARC, a `594` is technically the Instrumentation Note for music materials. However, older automated cross-walking scripts used in K-12 systems often repurpose the `594` tag to track localized text-kit pieces, reading-level groups, or specific kit components. The script pairs it with the `003` to ensure that if a teacher at a specific school alters the local kit description, the main vendor authority file (`003`) doesn't accidentally overwrite the item breakdown during a system refresh.
3. The Centralized "Disarray" Problem
In a K-12 cataloguing environment, you are constantly battling automated profiles that think they are helping.
1. A book vendor ships a shelf-ready box with a minimal, generic record.
2. The automation uses the `003` to merge it into your main catalogue.
3. The software creates a local `594` field to house specific local data (like processing codes or specialized tracking data). [1]
If the script breaks down or experiences a mismatch, you end up with hundreds of records stuck with orphaned `003` codes pointing to legacy databases, directly paired with random `594` text fields that no human cataloguer ever typed out.
If you want to purge these or safely isolate them so they stop cluttering your search indexes, I can give you a global delete criteria guide for your software. Would you like to map out a global deletion strategy to clean out these specific local `59X` fields?
[1] https://help.oclc.org
[2] https://catalog.iavalley.edu
[3] https://www.oclc.org