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.

Manuscripts and ArchivesYale University Libraryhttp://www.library.yale.edu/mssabill.landis@yale.eduDACS revision comments – Bill LandisGenerally, I think these edits represent a real improvement in the structure <strong>of</strong> DACS. I especiallylike slicing <strong>of</strong>f Part III and freeing this archival content standard from its legacy <strong>of</strong> inclusion <strong>of</strong>selected rules from AACR2 for formulating names. Congrats on moving that forward.I also think that you've done a nice job turning Part II into a data content standard for archivalauthority file records based on ISAAR(CPF) and aimed at encoding in EAC-CPF. Starting to bringthese international content standards (ISAD & ISAAR) together for the benefit <strong>of</strong> archivists in theU.S. through DACS seems like a major step in the right direction.I've made a lot <strong>of</strong> comments on the attached PDF <strong>of</strong> the draft that you released for comments. Theyrepresent my thoughts as I moved through the pages (and pages and pages …) <strong>of</strong> the revision. Idon't know how useful they'll be to TS-DACS. I'm going to try to summarize the major thrust <strong>of</strong> mycomments below.1. General:1.1. Preamble partsYou may be waiting until you're farther along with this draft, but I hope TS-DACS will be updating thePreface, Acknowledgments, and Overview <strong>of</strong> Archival Description to make them specific to DACS 2013. Ithink it is important that you provide some grounding for why these changes were undertaken andaddress the scope <strong>of</strong> the revision as TS-DACS undertook it, especially at a broad level the things youchose not to address in this revision.1.2. Encoding examples at the end <strong>of</strong> each chapter in Part I.I think it is a mistake to remove these. I know that you're moving fully encoded examples to theStandards Portal, which is a great thing. Nonetheless, removing element-specific examples <strong>of</strong>encoding in EAD and USMARC here forces people who don't really know those structure standardsto wade through fully encoded examples elsewhere. I think element-specific examples serve auseful purpose at the end <strong>of</strong> each Part I chapter and that they should be updated and retained.1.3. Examples in Chapter 2.3.Many <strong>of</strong> the new examples in Chapter 2.3 seem gratuitous to me. I actually think you've managed tomake this chapter a laughing stock, frankly. The new examples do things that differ markedly fromother examples without explanation. For example: 2.3.4, where existing examples include all segments <strong>of</strong> the supplied title, but the new onesdo not, with no explanation about the difference. I think you perhaps underestimate the role<strong>of</strong> DACS in teaching. If you want the 2.3.4 examples to illustrate only the name segment,then you need to change all <strong>of</strong> them, I think. 2.3.6. It seems unuseful to identify the source <strong>of</strong> an example unless it helps to explainsomething about the example. In both <strong>of</strong> these examples that is not the case. Again, seemsgratuitous and definitely introduces an inconsistency within examples in the chapter. 2.3.8. Rule is explicitly about personal names, so why would you use an example with acorporate name? And what does "additional records" mean? Additional to what? This is aAction: DACS Revision Page 154 <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!