Michele,
I usually include <altformavail> at the collection level if any part of the collection is available in another format, in addition to the <c0#> level. In my mind, it's one of those things that doesn't hurt to be in more than one place in a finding aids. You never really know how much (or little!) a researcher is going to read before deciding if a collection is appropriate. For example, since we have several whole or partial collections available in digital form through an image database, it can be useful to add an explanation of what is or is not available digitally at the collection level. Then we can add links to that content at the component level. It seems to be working so far...
Kira
* * * * * *
Kira A. Dietz
Acquisitions and Processing Archivist
Special Collections
University Libraries
Virginia Tech
[log in to unmask]
Office/Voicemail: (540) 231-3810
http://spec.lib.vt.edu
* * * * * *
-----Original Message-----
From: Encoded Archival Description List [mailto:[log in to unmask]] On Behalf Of Michele R Combs
Sent: Thursday, February 03, 2011 11:08 AM
To: [log in to unmask]
Subject: altformavail placement
One of the principles of EAD as well as DACS is to put a piece of descriptive information at the highest hierarchical level it applies. If only a portion of a collection -- say, the correspondence -- was available in microfilm, would you include a statement to that effect in an <altformavail> up at the top, above the <dsc>? (In addition, obviously, to putting it down in the Correspondence series in the inventory.)
Or would it be more appropriate to put <altformavail> at the collection level only if the entire collection is available in an alternate format? I can see arguments for both approaches.
Michele
(be green - don't print this email!)
~~~~~~~~~~~~~~~~~~
Michele Combs
Manuscripts Librarian
Special Collections Research Center
Syracuse University Libraries
222 Waverly Ave.
Syracuse, NY 13244
315-443-2081
[log in to unmask]
~~~~~~~~~~~~~~~~~~
|
