Michele R.,
I see one way with some options for explaining the material. Remember
you are really attempting to code the item, not simply create coding
that will work with the dtd.
<c01 level="file">
<did>
<container type="box" label="Box">1</container>
<container type="folder" label="Folder">1</container>
<unittitle encodinganalog="245$a">Inventory</unittitle>
</did>
</c01>
1. I assume that the folder and box were containers that your
institution used to re-house the collection material. If that is the
case, then you are not to describe these items. They are simply
containers. Designate them using the <container> element. Physdesc is
a physical description of the item(s). Some might use this to say how
many items were in the folder (3 leaves), etc. (MARC 300 generally)
2. "Inventory" is a folder heading. I assume that this folder heading
caption was created by the archivist that processed the collection
materials. If this is true, then you have should use the <unittitle>
element for this information. If you have information from the spine
of a bound item, then you should use that information in the
<unittitle> and then give a <note><p></p></note> to explain the
source of your title information. Thus, this "heading" given by the
processor is really title information (generally speaking). Using
head is simply incorrect. You need to match the data-type with the
elements.
3. If you have a location of the material that is specific, like an
annex or folio shelf or something like that, you can indicate this
with <physloc> and even give some detail about this with
<custodhist>. Otherwise, you need to use <container/> (99% of the
time) to indicate what container the item is housed in IN the
collection. Many repositories leave the folio/annex info to the desk
to deal with and don't want it encoded into the document (it could
change or not be info for the public to read...).
4. [log in to unmask] As in your example you can use <container
type='box'/> once and in each <container type='folder'/> you can use
the @parent attribute to indicate what previous container should be
displayed along with this folder information. See the example in the
tag library:
http://www.loc.gov/ead/tglib/elements/container.html
My stylesheet does use the @PARENT attributes when present. However,
other stylesheets may not. If your stylesheet does not, you will need
to inquire as to whether your display (HTML, PDF, etc.) can
incorporate or needs to incorporate these containers. This means you
may have to create the <container type="box"/> for each <c01/>.
Anyway, I hope this helps.
Mike Ferrando
Library Technician
Music Division
Library of Congress
Washington, DC
202-707-4454
--- MicheleR <[log in to unmask]> wrote:
> Hi all --
>
> I'm struggling a bit with the function and relationship of c01,
> container,
> physdesc, physloc. As far as I can see, if I have a folder in Box
> 1
> labelled "inventory" I can see at least four ways right off the bat
> to
> represent it (and there are probably more):
>
> <c01><did><head>Inventory</head>
> <container>Box 1 Folder 1</container></did></c01>
>
> <c01><did><head>Inventory</head>
> <container label="box">1</container>
> <physdesc>1 folder</physdesc>
> <physloc>AKC Box 1</physloc></did></c01>
>
> <c01><did><head>Inventory</head>
> <container>Box 1</container>
> <physloc>Folder 1</physloc></did></c01>
>
> <c01><did><head>Inventory</head>
> <physdesc>1 folder</physdesc>
> <physloc>AKC Box 1</physloc></did></c01>
>
>
> Can somebody help me understand what the difference is, and/or
> which way
> most closely aligns with what the various tags are intended to
> describe?
> The EAD tag library at loc.gov gives an example where the box is
> one
> container, and the folder is another container but you specify the
> box
> container in the "parent" attribute. This seems really awkward and
> unwieldy
> (not to mention a pain to tag). Does anyone actually do it this
> way??
>
> Michele
>
>
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.782 / Virus Database: 528 - Release Date: 10/23/2004
>
__________________________________
Do you Yahoo!?
Take Yahoo! Mail with you! Get it on your mobile phone.
http://mobile.yahoo.com/maildemo
|