-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
035 is mislabelled #1723
Comments
I'd phrase it the opposite way: It's the right label, but maybe the wrong MARC field. We need a field for local numbers. |
A local number on a Print source doesn't make sense, though, right? What's it local to? It makes sense if it's a local control number, since this would refer to a control number in an external system, but local call numbers don't belong in 035. For MS, a local call number should probably go in the 852 somewhere, right? And RISM numbers should go in 510. |
The A/I numbers in 035 were put in 035 at the beginning of the A/I import (ca. 2015) but probably aren't relevant to 035 any more. It was "local to RISM" I guess you can say. 510 is the relevant field for that, but we'd have to cross-check before deleting. |
Here's a list of the top 100 values in 035, along with the number of times they occur.
Not sure what to do about them, but I think we don't need to decide that before we decide to change the label to match MARC21. |
MARC21 calls 035 a "System Control Number": https://www.loc.gov/marc/bibliographic/bd035.html
However, Muscat calls it the (much more vague) "Local Number". Thus it can be confusing about what to put in this box (which should be limited to system numbers, and not local call numbers or other identifiers.)
For example, RISM series numbers should not be put in this box, but have been: https://muscat.rism.info/admin/sources/992004614/edit (You may need to check the modification history if it's been corrected.)
There are a lot of problem entries in this field, so cleaning it up would be a problem. Deciding whether to actually tackle the entries in this field can be a separate issue. Validation of this field (it should always start with an open parenthesis indicating the type of control number can also be part of that issue.
As a first step, though, can we re-label this field to match MARC21?
The text was updated successfully, but these errors were encountered: