13.07.2015 Views

Appendix A - Society of American Archivists

Appendix A - Society of American Archivists

Appendix A - Society of American Archivists

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Reviewers were pleased overall with the content <strong>of</strong> the revision, and happy to see the new section onarchival authority records and to see part III removed. Although understanding that the companionwebsite will provide additional examples, reviewers regretted the loss <strong>of</strong> MARC and EAD encodingexamples, as well as the full text examples found in the <strong>Appendix</strong> D (where sample EAC-CPF encodingwould be a useful addition.) Reviewers were happy to note that changes in formulating titles aredetermined by the institution (no mandated move away from "papers".) Some <strong>of</strong> the copy-editingproblems that were caught (occasional references to "supplied" rather than "devised", pp. 37-38) weknow that TS-DACS is already aware <strong>of</strong>.General Comments and Questions References to AACR2 should either be deleted or changed to “RDA or AACR2” (as is done in 2.6),given that RDA will be the predominant North <strong>American</strong> bibliographic content standardbeginning in 2013. There is concern that description <strong>of</strong> digital material should not obscure the content <strong>of</strong> thematerial. While extent, for instance, must be expressed for the digital format, titles and otherdescriptions <strong>of</strong> content (such as sound recordings, moving images, maps) should not beobscured by describing them as electronic files.Preface: We are assuming that the preface to the 2013 edition will be written after the other text isfinalized. The remainder <strong>of</strong> the prefatory matter should be reviewed as well.Introduction: Paragraph on Examples (p. 5) will need to be rewritten if most MARC and EAD examples havebeen removed, and to clarify when they appear; it looks like these occur only when the ruleindicates that information can be given in text or in a code. EAC-CPF examples should bementioned here as well.Chapter1, Levels <strong>of</strong> Description:Second paragraph (new text): Given that the first sentence states that a finding aid can consist<strong>of</strong> either a single level <strong>of</strong> description or multiple levels <strong>of</strong> description, the third sentence is notquite logical. Can a finding aid combine both a single-level and multiple-levels <strong>of</strong> description?Would something similar to the following be slightly clearer (if it accurately conveys theintention <strong>of</strong> the second paragraph)?A finding aid that consists <strong>of</strong> multiple levels <strong>of</strong> description may provide information atsuccessively narrower levels <strong>of</strong> arrangement (such as subseries, files, and even items)for some series while confining information to a single level <strong>of</strong> hierarchy for others.Fourth paragraph (existing text): Copy editing issue. “Twenty-five” is spelled out in the firstsentence <strong>of</strong> the fourth paragraph, but the number 25 is used in the first sentence <strong>of</strong> the sixthparagraph.Requirements for Single-level Descriptions:Action: DACS Revision Page 151 <strong>of</strong> 158 0113-II-A-DACS

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!