-
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
Validation in MARC tags with multiple subfields #1128
Comments
Editing this to include more fields that have subfields. Catalogers sometimes fill out a function (700$4, 710$4) or a literature reference (690$n, 691$n) but forget the person or book, and they would appreciate a warning here so that they can fix it. So: 710: 690: 691: 510: 596: |
For 700 and 710 I cannot reproduce the bug, as leaving $a empty will always trigger an error for me - is there a special way this is done? |
I was thinking of the error reports that had the empty $a. Maybe it was only in old records. You're right, I'm getting errors (as expected) too. |
* develop: Fix #516, make sure the + sign is only in the first element Show all subtags for 852, remove the partial, it was used for linking but that is done automatically now. Fix #1128, properly show errors on select items #1128 Add validations Fix #1138, implement validation to avoid 787 and 773 pointing to themselves.
Was this implemented, or is it yet to come? We had an empty 856$u recently (https://muscat.rism.info/admin/sources/1001171784). |
Oh, I realized I implemented all of them except 856$u |
I will move this to 8.1, the problem is that a field can be validated only by one rule, and 856 $u already has a |
Giving this a boost because there are also some records where just one subfield in 856 is filled out, likely just through misclicking.
The validation should catch such cases and we should add it to the health report. We'd also need a list of 856s missing multiple fields so we can fix them. |
Also relevant: People: Validation for 024 #1498 |
Just noticed that some people are filling out 856 $z and $x even if there is no URL in $u. So we need a validation that looks at the whole field - if 1 subfield is filled out, then all 3 need to be filled out.
The text was updated successfully, but these errors were encountered: