Mark and All :
Hi -- this question regarding the use of dates and the formatting of those dates, esp. in the 37X fields of NACO records, reminds me of a question I had regarding "fuzzy" dates a couple of days ago. I wondered if in cases of "known" dates but not necessarily "known" start and/or end dates, if catalogers can use angle brackets (i.e., <2001- >) around dates in these subfields?
Within the Serials Cataloging community, we are very fond (smile!) of using angle brackets to represent the attribute of change over time.
In the case of NACO Authorities cataloging, the case comes up quite often where we know something about an entity for at least a given moment in time. For example, based on the resource(s) I have at hand, I may know that a certain person taught at or attended a certain university for a specific period of time, or I may know that a given Monographic Series was published by a specific publisher for a certain span of years. However, I don't know exactly when that attribute associated with said entity began or ended.
And doing the research necessary to find those exact start and end dates is time-consuming, and often frustrating.
In such situations, I would like to be able to at least put in the known date(s) within angle brackets, if necessary. Within a cooperative cataloging environment, the next NACO cataloger who updates this authority data may have additional information to contribute.
Of course, one could enter the "known" date information in the 670 fields as we do today. But then actually removing the specific date information from the attribute that it is intended to describe moves us away from the Entity-Relationship Model that RDA is intended to move libraries toward. I know that from my own experience that trying to reconstruct information encoded in LC/NAF Authority records based on the 670 information can be, at the risk of being repetitive, time-consuming and frustrating (smile!).
I suppose this is a long way of asking if NACO has made a decision on the use of angle brackets within the date subfields of Authority records.
Principal Serials Cataloger & Authorities Librarian
New York University Libraries
[log in to unmask]
212 998 2488
I wrote:Richard Moore responded:
>>True. And I just came across a questionable-date format in an example
> under the 375 $s on the MARC21 site.
>>But I don't want to rely on a single example as support for applying
> EDTF date formats
> That's not an example of an EDTF date format. It's an example of the wayI read RDA 220.127.116.11 <http://access.rdatoolkit.org/18.104.22.168.html> as
> RDA indicates that uncertain dates should be recorded (e.g. in 22.214.171.124).
applying only to those dates applicable to the elements under 9.3, and
any date formatting instructions in RDA as applying to those
instructions found within the context of the RDA text. For instance,
nowhere in RDA is there instruction, explicit or implicit, that the
Profession or Occupation element (9.16) be further enhanced
(optionally?) with dates that provide the time period in which a
person had a job or was otherwise occupied in a particular field. We
may, of course, spell this out in the Biographical Information element
(9.17) or the Source Consulted element (8.12), both mapped to
different MARC fields. Date of Usage (8.9) is limited to the
I did a little poking around the MARC site and I found this in
Discussion Paper 2008-DP05/2
"3.2.2. Period of activity
RDA includes elements for period of activity (start) and period of
activity (end).[!!] To include specifically in MARC, the same options
are available as with birth and death dates: either define a new field
for period of activity or define a new field to accommodate additional
dates with one or two subfields for period of activity (depending upon
whether you parse the start and end into two subfields or encode as a
range in one subfield)."
(These elements must have existed before the November 2008 draft of RDA.)
Proposal 2009-01/1 codifies the dating qualification for Field of
Activity and other fields with the supportive statement that
characteristics of an entity may change over time. Otherwise, there's
no RDA source I came across that specifies the application of these
dates for 37x elements.
Ultimately, the 37x $s and $t subfields strike me as a MARC layer we
apply on top of the RDA information in our authority records. I'm
seeking the MARC instructions/NACO policies that tell me what kind of
date formatting is allowed or required for the subfields in question.
For the time being, I'm following the approach you mention in another
post in this thread:
1.) use both known and fuzzy dates in the 046 for those RDA elements
that are mapped to that field
2.) stick with known dates in the 37x $s and $t and give fuzzy dates
in the 670/678s until I hear of a policy set down by the higher ups in
I wouldn't mind getting that resolved if we catalogers find it
> ISO 8601 and edtf dates are only recorded in 046. Part of the problem is
> that there would be no way to indicate what date standard you are using
> in 37X.
necessary to spell out what standard we're using in these $s and $t