1,277
edits
Important: The GCConnex decommission will not affect GCCollab or GCWiki. Thank you and happy collaborating!
Changes
Jump to navigation
Jump to search
m
→046 Special coded dates: Added anchor for field 046 2nd par
Line 566:
Line 566:
+
'''General'''
'''General'''
−Best practice: When encoding date information, give the fullest information about the date that is readily available (the date in field 046 may be more precise than a date used in the 100 subfield $d). When revising existing authority records, record dates in field 046 even if the heading itself does not have dates in 100 subfield $d, when the information is readily available.
+Best practice: When encoding date information, give the fullest information about the date that is readily available (the date in field 046 may be more precise than a date used in the 100 subfield $d).
+<span id="046_2nd_par">When</span> revising existing authority records, record dates in field 046 even if the heading itself does not have dates in 100 subfield $d, when the information is readily available.
When recording dates in field 046, use the Extended Date Time Format (EDTF) schema in all cases except for centuries; supply dates using the pattern yyyy, yyyy-mm, or yyyy-mm-dd. See date table in [http://original.rdatoolkit.org/lacbanqpschp9_lacbanqps9-304.html LAC-BanQ PS 9.3.1.3].
When recording dates in field 046, use the Extended Date Time Format (EDTF) schema in all cases except for centuries; supply dates using the pattern yyyy, yyyy-mm, or yyyy-mm-dd. See date table in [http://original.rdatoolkit.org/lacbanqpschp9_lacbanqps9-304.html LAC-BanQ PS 9.3.1.3].
