Incorrect fixed fields pulled from 006 fields
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
New
|
Undecided
|
Unassigned |
Bug Description
Evergreen (All supported through at least 2.9)
Other versions irrelevant
The 008 fixed fields are dependent only on the Leader/06 value for record type, but both the 006 and 007 fixed fields define their fixed fields based on their first character position (006/00 = Form of Material, 007/00 = Category of Material). Currently all 006 fields in a record are treated as if the 006/00 represents the same form of material as the leader/06, which leads to any fixed fields not shared among all 006/00 values to be potentially incorrect.
Here's an example: http://
To make it easy to look at them, attached are the 006's and MARC attributes for this record. To make sense of them you'll need to keep http://
The 006 that has a /00=a defines Ills=a, Conf=0, Indx=0, Fest=0, and Form=0, but what we're given is a TMat=0, which makes no sense. The /00=j field defines Comp, FMus, Part, AccM, LTxt, and TrAr, none of which are defined in evergreen currently (see bug 1371647 in progress) but it contributes nothing because VIS defines /01-03 to be Time which would be ppn, and the s that would be AccM is in the undefined block for VIS subfields.
I'm hoping this starts some discussion about how to go about fixing this, I don't know if it's necessary to go to the same lengths that we do to support the 007 but I don't personally see a better way since they both work so similarly.
tags: | added: cataloging |
Apologies for all of the OCLC FF abbreviations, but they do seem to be fairly well known among catalogers and LC doesn't seem to use any abbreviations. (I got no time for that...)