I have been made aware of a bug in MARC::Lint, dealing with 880 field and
with linked subfields (subfield 6). 880 indicator valid values are currently
improperly parsed, so 'Same' are the only allowed values (as in 'Same as
associated field'). For subfield 6, it should always be the 1st subfield
according to MARC 21 specifications. This conflicts with Lint.pm's
validation of the 245 (and with several check_xxx methods in
MARC::Lintadditions), which currently requires that subfield a should be the
1st subfield.
I have begun working on fixes to these problems. I'm thinking I'll modify
check_record in "for my $field ( $marc->fields ) {" to check the 880 for
repeatability, and then, if the tagno is 880, reassign $tagrules =
$rules->{$tagno_880}, where $tagno_880 = #the 1st 3 characters of subfield
_6--the tag for the associated field. This should allow the field to be
checked as if it were the associated field.
At 'my $checker = "check_$tagno";', I'll revise it to $tagno_880.
For validation of 1st subfield '6' rather than 'a' in the 245 (and other
fields), eventually there should probably be a single method that checks all
fields and reports an error if subfield 6 is present but not the 1st
subfield. For now though, I'll put similar code into each of the check_xxx
methods for the 2 cases--subfield 6 is present vs. subfield 6 is not
present. Then report errors for subfield a not being 2nd if subfield 6, and
not being 1st otherwise (for 245).
In the data section:
880 R ALTERNATE GRAPHIC REPRESENTATION
ind1 Same as associated field
ind2 Same as associated field
6 NR Linkage
Currently (in MARC::Lint since at least version 1.38), the data section
elements are separated by spaces. In prior versions, they were separated by
tabs. The lack of a 2nd column between the indicators and the description is
what is causing the 880 to report "Same" as the only valid indicator values.
Is there any reason not to change the column separators back to tabs? Should
this be limited to the 880 field (and any similar field that may exist or be
added)?
Please let me know of any suggestions you may have. Thank you,
Bryan Baldus
[EMAIL PROTECTED]
[EMAIL PROTECTED]
http://home.inwave.com/eija
