Library Technical Services > Procedures & Documentation > Rare & Manuscripts Collection > DACS and APPMs | |
| How DACS Differs from APPM (LTS Procedure #112) Scope: This document lists the MARC fields that are treated differently under the new rules for cataloging manuscripts and archives, Describing Archives: A Content Standard (DACS), compared with the previous rules, Archives, Personal Papers, and Manuscripts (APPM). Contact: Margaret Nichols Unit: LTS Special Materials Date last updated: 03/27/08 Date of next review: April 2009 Note: DACS rules are intended to apply to finding aids as well as catalog records. Fields whose names are in boldface below are required in all DACS records (although the MARC tags are required only in the catalog records, not in the finding aids).
Leader: fill in 008: fill in Place: nyu [country code for location of repository, not for where the manuscripts come from]
040 $a NIC $c NIC $e dacs
099 _9 Collection number
100, 110, or 111 Creator or collector, if applicable (if the repository is the collector, don’t use this field)
245 00 $a Title: creator’s name + nature of the materials + (optionally) topic, $f date (if you use “circa,” spell it out; if the collection has no date, use “undated,” not “n.d.”), $g bulk [dates—if you have bulk dates]
Examples:
Nichols family papers, $f circa 1910-1975
Alexander Gardner Civil War photographs, $f 1861-1865
Note: Use “papers” (for an individual or family) or “records” (for an organization) only if the collection includes three or more forms of documents. If the collection consists of one or two forms of documents, include those forms in the title (see DACS 2.3.19).
Date(s): You can formulate the date(s) in the way that you think best, as long as you are consistent about it. For instance, expressions like “1890s,” “probably 1834,” or “before 1925” are OK.
300 Extent: spell out the words, e.g. 35 cubic feet. You can include in this field both a measurement and a count.
Examples:
6 $f cubic feet (15 boxes)
2 $f cubic feet (200 items)
545 Administrative/ biographical history, if applicable
520 Scope and content
Note: If the collection is incomplete for reasons other than appraisal decisions, describe the gaps here (DACS 3.1.5).
351 Organization/arrangement: describe the aggregations within the collection and their relationships, if applicable (DACS 3.2.2).
506 1_ Conditions governing access: RMC will use this field only when access is restricted. Note that the first indicator for this field has now been defined: 0 (zero) if there aren’t any restrictions, 1 if there are restrictions.
Examples:
$3 Letters from Susie Bright are $a restricted until 2010.
538 Technical access element (required if applicable)
Examples:
$3 Correspondence from 1980 onward is $a on floppy disks, double sided, double density.
System requirements: Windows 95/NT; sound card; color monitor.
BetaMax.
$3 Numerical data is recorded in $a Access database.
540 Conditions governing use (required if applicable), e.g. restrictions on reproduction due to copyright (DACS 4.4.6, 4.4.8-9)
Note: If the material is in the public domain, say so in this note (DACS 4.4.10). This field could also be used to alert patrons that they need permission to quote materials, or to specify who owns the copyright, etc.
546 Languages and scripts of the material (required; also, use the appropriate MARC language code for Language in the 008 field)
Examples:
$3 Pamphlets in $a German; $b Fraktur.
$a In English. $3 Early (16th-century) documents are in $b secretary script.
600, 610, 611, 630, 650, 651, and/or 655 Access fields (subjects) as appropriate
700, 710, 711, 730 Access fields (added entries, e.g. for contributors, correspondents, co-creators) as appropriate
852 Name and address of repository. RMC will not use this field. Note: The absence of other fields from this list does not mean that you cannot use them in DACS. This list is meant to highlight the fields that are treated differently in DACS than in APPM.
|