Dates #382
Replies: 2 comments 7 replies
-
Yes, this data belongs in RDA. Can we afford to lose it? Depends ... How will we map it? The values of $c in 260, 264 may not be timespans; e.g. "1967, c1965" These MARC 21 Bibliographic examples indicate how difficult it will be to parse out a timespan from $c (sometimes). So where $c is not a simple, obvious date, it is better to use 008 Date 1 and Date 2 and ignore $c. "u" values can be simply converted to ISO 8601; e.g. "19uu" > "19"; "195u" > "195". The value of 008/06 is also useful for parsing a value in $c: "b": convert the value of $c to a standard BCE value such as ISO 8601. |
Beta Was this translation helpful? Give feedback.
-
Related discussion to start @CECSpecialistI --> To what extent do we reuse systematic IRI's for places/timespans/etc. in this mapping? |
Beta Was this translation helpful? Give feedback.
-
Issue came up in review of 008 mapping:
Character position 06 indicates meanings of Date 1 and Date 2, which often repeat information in 26Z $c in a structured way that computers can interpret more reliably than 26X $c which includes all sorts of stuff.
This discussion should take 26X $c, 045, and 046 into consideration as well.
Beta Was this translation helpful? Give feedback.
All reactions