You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is not clear why field 046 (Special coded dates) is ignored in bib records when there is a specification for conversion in authority records. At a minimum, the same spec can be used in bib records for subfields k and l.
We would like to see subfield o (single or starting date for aggregated content) and subfield p (ending date for aggregated content) included. When a work is an aggregate, the specs for subfields k and l work for o and p as well. It should be relatively easy to include this in the conversion program.
The text was updated successfully, but these errors were encountered:
It is not clear why field 046 (Special coded dates) is ignored in bib records when there is a specification for conversion in authority records. At a minimum, the same spec can be used in bib records for subfields k and l.
We would like to see subfield o (single or starting date for aggregated content) and subfield p (ending date for aggregated content) included. When a work is an aggregate, the specs for subfields k and l work for o and p as well. It should be relatively easy to include this in the conversion program.
The text was updated successfully, but these errors were encountered: