Hi, because of the multitude of subjects and material I have decided to used
series and subseries to describe and organize my material with <c01> series,
<c02> subseries <c03>
<c01> level label "series" id"series I-VII"
<unittitle> contains series title
<unitdate>contains dates of series
<physdesc> contains no. of boxes and folders
<unitid> contains the call no. of the box
<c02> Subseries label> title of subseries
<unittitle> title of material in folder
<unitdate>date of material in folder
When <c02> is broken down to show a connection within
c02 <container>box is used to id the box and <container>folder is use to
show the number of folders i.e. <c02> <container>folders 1-5
<unittitle> identify the group of folders and unitdate identify material
dates covered in the folders. In <c03> is the <container>box, <container>
folder, <unittitle> describes folder contents and <unitdate>dates of the
contents. A <note> is provided for additional descriptions.
Has anyone done this and does anyone see any problems with using this?
Rita Knight-Gray, Project Archivist
The Flewellen Collection
East Cleveland Public Library
14101 Euclid Ave.
East Cleveland, OH 44112
[log in to unmask]
From: Encoded Archival Description List [mailto:[log in to unmask]] On Behalf Of
Sent: Friday, March 17, 2006 1:57 PM
To: [log in to unmask]
Subject: Re: Spam: EAD and minimal-level processing
Jodi and all---
If the very low intensity of physical processing either can't identify
record series, or at least can't disentangle them meaningfully, why not
simply code every resulting <c0x> as @LEVEL=file? Then the coding is
intellectually sound, and it reflects the circumstance that no useful
hierarchy presents itself in their arrangement.
Just one way to skin the cat,
Dennis Meissner, Archival Processing Manager Minnesota Historical Society
Voice: 651.296.2496 | Fax: 651.296.9961
eMail: [log in to unmask]