LISTSERV mailing list manager LISTSERV 16.0

Help for EAD Archives


EAD Archives

EAD Archives


[email protected]


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

EAD Home

EAD Home

EAD  June 2005

EAD June 2005

Subject:

Re: where to indicate container info?

From:

"Prof. Dr. Angelika Menne-Haritz" <[log in to unmask]>

Reply-To:

Encoded Archival Description List <[log in to unmask]>

Date:

Fri, 3 Jun 2005 17:51:41 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (179 lines)

You are right, Michael, concerning the German archival practice. A <c> with
the level attribut value "class" here is something like a chapter in a book
and we use <unittitle> for the header of this classification group. In
German finding aids the actual records are the deciptive units on the lowest
c-level where we use the attribute value "file", which in general correspond
to the physical units in the stacks identified by a call number in <unitid>
.

Angelika Menne-Haritz
Bundesarchiv, Berlin





----- Original Message -----
From: "Fox, Michael" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Friday, June 03, 2005 5:20 PM
Subject: Re: where to indicate container info?


There are some interesting ideas here but I would prefer not to use the term
"headings" as that evokes the concept of display text associated with the
element <head> in EAD.

Rather what we have is a reflection of arrangement. In our organizational
of archival materials, some of the units of arrangement relate to actual
archival "stuff" and may be described specifically. Other units of
arrangement are simply there to provide organizing "buckets" for ordering
materials into useful groupings. I am reminded, in a vaguely related sort
of way, of the guide cards in card catalogs that helped to organize and
subdivide the contents of a drawer into manageable groupings. Of course,
these were not necessarily hierarchical in the way we do archival
arrangement but they achieve some of the same goals.

If I understand the theory correctly, German archival practice consciously
identifies such units of arrangement as classification (though not in the
sense of library subject classification), thereby distinguishing them from
descriptions of actual records. Hence the level attribute value "class" in
EAD.

Michael Fox



-----Original Message-----
From: Encoded Archival Description List [mailto:[log in to unmask]]On Behalf Of
Mike Ferrando
Sent: Thursday, June 02, 2005 9:27 AM
To: [log in to unmask]
Subject: Re: where to indicate container info?


Michele R.,
My perspective on the relationship between finding aid container list
and the DSC elements is that you only have two types of entries. You
either have a "heading" (used loosely) or you have an "item" (used
loosely). Headings rarely have any descriptive elements. Items do
have descriptive elements.

If the headings are series or subseries, then you will have the
summation of container info, a scopecontent and other information
elements. (These are not necessarily required or always needed. For
example, you need not have subseries scopecontent if you have covered
it in the series scopecontent.) Whatever the elements chosen for the
series or subseries, they will be summations.

Items have elements specifically related to their description. This
could include scopecontent and other such elements, but even these
are tailored to the specific item itself.

Limitations do present situations where you may fudge the finding aid
to get a better coded EAD document. There are often times when it is
unclear if a "heading" is actually a subseries or not. In such cases,
you must make a decision concerning these types of finding aid
puzzles.

In my coding experience, "subseries" represents an intellectual
judgement about the material. The heirarchy of information in the
finding aid does not always obligate an intellectual judgment, but
rather only an organizational judgement. When you have an
organizational judgement you merely continue to give the "heading"
component [c02] and nested component [c03] the @level='file'.

Often there will be only "headings" and no item level description at
all. I find this very common with clippings and miscellaneous.

I must admit that there are times when I just have to go and look at
the collection box or folder to understand the finding aid for proper
coding. (The shorthand is just too short.)

In the case you present, I know nothing of the actual items. If you
are presented with material that clearly has one genre of material
"writings", then you most likely should try to find a term to
describe the other group as well (i.e, "printed matter",
"miscellaneous", "notes", "other", etc.). Often you can find many
items of this other "group" is actually a subseries in the first
group. This would mean that you really don't have "writings" and
"other" you have groups of "writings". The subseries you thought you
had under writings become series in the new arrangement and you have
solved your problem.

My experience is that the "headings" are best served by using the
components hierarchically to give context to the items (providing the
landscape of processed collection). The "items" are best served by
the component itself and the descriptive elements that will best
represent the datatypes given (dates, notes, physical description,
etc.). I admit that I do tend to see the hierarchy as wrapping, and
the item as a possibility of item level description (aka MARC21
encodinganalog values).

In conclusion, you really don't offer much information about this
collection. I would say that the container MUST appear for each item
(my stylesheet does respect the @parent attribute in the container
elements). However, if this has not been done in the legacy finding
aid, then go with what is there. The real issue is how are people
going to find the item (if that is the intention of the container
information)? Otherwise, you merely have summations of containers for
each "heading".

Mike Ferrando
Library Technician
Library of Congress
Washington, DC
202-707-4454


--- MicheleR <[log in to unmask]> wrote:

> OK, another question for the collective wisdom. Let's say I have
> some
> material that looks like this, and that it's all in Box 1 of a
> 5-box
> collection:
>
> c01 - Writings
> c02 - History of Spain
> c02 - History of England
> c02 - History of Holland
>
> c01 - something else...
>
> Is it more appropriate to put the container information at the c01
> level
> (Writings), since all the child pieces are in the same box and
> they'll
> inherit from the parent, or is it more appropriate to put the
> container
> information at the lowest level, i.e. repeat it in each c02, so
> that each
> piece has its own container information? Has anyone run into
> problems doing
> it one way or the other?
>
> The EAD application guidelines say something nutty about just
> sticking in a
> container element wherever the material switches to a new container
> and not
> worrying about what c0# you're in but that seems, well, a bit
> strange to me.
> Doing that is likely to leave some elements with no accurate
> container
> information based on the document tree and I'm not really
> comfortable with
> that...
>
> Michele
>





__________________________________
Do you Yahoo!?
Yahoo! Mail - You care about security. So do we.
http://promotions.yahoo.com/new_mail

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

March 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001
June 2001
May 2001
April 2001
March 2001
February 2001
January 2001
December 2000
November 2000
October 2000
September 2000
August 2000
July 2000
June 2000
May 2000
April 2000
March 2000
February 2000
January 2000
December 1999
November 1999
October 1999
September 1999
August 1999
July 1999
June 1999
May 1999
April 1999
March 1999
February 1999
January 1999
December 1998
November 1998
October 1998
September 1998
August 1998
July 1998
June 1998
May 1998
April 1998
March 1998
February 1998
January 1998
December 1997
November 1997
October 1997
September 1997
August 1997
July 1997
June 1997
May 1997
April 1997
March 1997
February 1997
January 1997
December 1996
November 1996
October 1996
September 1996
August 1996
July 1996
June 1996
May 1996
April 1996
March 1996
February 1996
December 1995

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager