DACS practice would be to use 245 $f and $g and omit 264, so my guess agrees with yours, that the duplication is to try to cover both rda and dacs bases. I'd be interested in other opinions, but DACS and RDA are different enough that I don't think they should be combined in one record.

On Wed, Mar 29, 2017 at 4:23 PM, Casey Mullin <[log in to unmask]> wrote:

[excuse cross-posting]

 

Dear CW,

 

I note that dates of archival collections are covered by the RDA element 2.7.6.7, which maps to 264 _0 $c. There is an optional addition for the bulk dates, in addition to the inclusive dates.

 

My question is: is there provision in RDA for *also* (or instead) giving these date ranges in 245 $f and $g? Example:

 

245 ...  papers, ǂf 1861-2015 ǂg (bulk 1923-1995).

264 _0ǂc 1861-2015, bulk 1923-1995.

 

I note that 245 $f and $g are not included in the MARC to RDA Bibliographic mapping in the Toolkit. So my initial answer to my own question would be no.

 

Some cursory searching in OCLC for archival collection records coded RDA reveals a diversity in practice. Sometimes 245 $f (and $g if applicable) are given, but 264 is not. Sometimes both. Sometimes the inclusive dates are given in both fields, but the bulk dates in 245 only. Etc. Does such a redundancy suggest a practice "borrowed" from DACS (which I am not versed in); some records I found are coded *both* dacs and rda in 040.

 

I'm OK with the 245/264 redundancy for our local purposes, but I'd like to ensure our records are RDA-compliant.

 

Thanks,

Casey

________________________________

Casey A. Mullin
Head of Cataloging and Metadata Services
Western Washington University


Chair, Music OCLC Users Group

 

360-650-7458

[log in to unmask]

 




--
Christine DeZelar-Tiedman
Metadata and Emerging Technologies Librarian
University of Minnesota Libraries
160 Wilson Library                      (612) 625-0381 PH
309 19th Ave. S.                        (612) 625-3428 FAX
Minneapolis, MN 55455               [log in to unmask]
https://listserv.loc.gov/cgi-bin/wa?A3=ind1703&L=PCCLIST&E=quoted-printable&P=3046837&B=--001a1146f102927ff6054bf319a8&T=text%2Fhtml;%20charset=UTF-8&pending=
listserv.loc.gov
crawl=CC-MAIN-2021-25
5100
application/http; msgtype=response
sha1:LWU3DQNHUFF52BJVU7RMQ4LDKTK4M6VU
<urn:uuid:55affa6e-18c9-4d40-b409-490f3bb3875d>
2021-06-13T09:23:41Z
140.147.239.86
text/html
sha1:YL4I4CO4CZ2C7D2M5XJ2TM7BRQHPHGUH
<urn:uuid:c41e1154-ecc3-4d13-b56e-679c408cd830>
https://listserv.loc.gov/cgi-bin/wa?A3=ind1703&L=PCCLIST&E=quoted-printable&P=3046837&B=--001a1146f102927ff6054bf319a8&T=text%2Fhtml;%20charset=UTF-8&pending=
response
<urn:uuid:e8a2f25b-f88e-4257-936d-47c266e92ab6>
isPartOf: CC-MAIN-2021-25
publisher: Common Crawl
description: Wide crawl of the web for June 2021
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-182.ec2.internal
software: Apache Nutch 1.18 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.2-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/