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
When you record a range of dates in bf:date, eg a multivolume work, should be able to get a range coded as “multiple dates” in the 008’s position 06, with the first date in positions 07-10 (“Date 1”); the second date in positions 11-14 (“Date 2”) (see https://www.loc.gov/marc/bibliographic/bd008a.html):
008 220819m20132014ja a jpn||.
Actual MARC
When you record a range of dates in bf:date, eg a multivolume work, you get a single date with a trailing hyphen:
008 220819s2013- ja a jpn||.
Expected mapping logic
In most cases of a single, monographic instance, it will be an unambiguous four-digit sequence (e.g. “2019” or “1965”) which maps cleanly to MARC 008’s positions 07-10, and justifies the use of “s” in position 06.
Multivolume instances can span publications across multiple years, and their literal dates would be for example “2013-2014” (as in the sample Stage link above). MARC maps such sequences as date type “m” (not “s”) in position 06.
The text was updated successfully, but these errors were encountered:
Type of change
Existing mapping in 008
Example RDF records
https://api.stage.sinopia.io/resource/a06fd6b3-0107-4e50-9988-5632c07180ca
bf:date is listed as “2013-2014”.
Resource template
pcc:bf2:Monograph:Instance
Stage
Expected MARC
When you record a range of dates in bf:date, eg a multivolume work, should be able to get a range coded as “multiple dates” in the 008’s position 06, with the first date in positions 07-10 (“Date 1”); the second date in positions 11-14 (“Date 2”) (see https://www.loc.gov/marc/bibliographic/bd008a.html):
008 220819m20132014ja a jpn||.
Actual MARC
When you record a range of dates in bf:date, eg a multivolume work, you get a single date with a trailing hyphen:
008 220819s2013- ja a jpn||.
Expected mapping logic
In most cases of a single, monographic instance, it will be an unambiguous four-digit sequence (e.g. “2019” or “1965”) which maps cleanly to MARC 008’s positions 07-10, and justifies the use of “s” in position 06.
Multivolume instances can span publications across multiple years, and their literal dates would be for example “2013-2014” (as in the sample Stage link above). MARC maps such sequences as date type “m” (not “s”) in position 06.
The text was updated successfully, but these errors were encountered: