LISTSERV mailing list manager LISTSERV 16.0

Help for EAD Archives


EAD Archives

EAD Archives


EAD@LISTSERV.LOC.GOV


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  October 2002

EAD October 2002

Subject:

Re: question about re-engineering

From:

"Fox, Michael" <[log in to unmask]>

Reply-To:

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

Date:

Tue, 29 Oct 2002 16:32:21 -0600

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (40 lines)

Amy,
        Are you talking about physically rearranging the materials or only
their description?

        If the former, is the underlying question actually this- is it
permissible to organize materials in a hierarchical manner that were not
originally so arranged?

        Description, if that is what is meant, should follow arrangement.
While EAD offers a mechanism for reflecting complex hierarchies, many
collections in my experience are very flat in their organization and do not
need such structures. A collection may not be divisible into series but
consist simply of a group of files or even simply discrete items. And this
is not limited to very small collections. We have one large collection that
could be characterized as a single series comprised of many individual,
discrete files whose listing runs to over 900 pages.

        EAD does not demand a certain arrangement but only wishes to provide
a way to reflect what is there. There may be only two levels of hierarchy-
the description of the whole and the description of the individual parts.

Michael

-----Original Message-----
From: Amy McCrory [mailto:[log in to unmask]]
Sent: Tuesday, October 29, 2002 10:17 AM
To: [log in to unmask]
Subject: question about re-engineering


Has anyone, in attempting to re-engineer legacy finding aids for EAD
compatibility, encountered resistance on the basis that re-ordering of
elements into series and other hierarchical levels would violate the
creator's original order?

Amy McCrory
Archivist
Cartoon Research Library
Ohio State University

Top of Message | Previous Page | Permalink

Advanced Options


Options

Error during command authentication.

Error - unable to initiate communication with LISTSERV (errno=111). The server is probably not started.

Log In

Log In

Get Password

Get Password


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager
https://listserv.loc.gov/cgi-bin/wa?A2=ind0210&L=EAD&F=P&P=29408
listserv.loc.gov
crawl=CC-MAIN-2021-10
42971
application/http; msgtype=response
sha1:RFE54O4YSAPIM3MWZ7AHCD2PP3EGXWC3
<urn:uuid:cdbbcc60-9eb5-4100-9442-87d67a24fe68>
2021-03-07T21:14:20Z
140.147.239.86
text/html
sha1:GVOAPYA3WBXCQ6JRPLVSHH5RLJVP2VHJ
<urn:uuid:2164ee2e-3597-4f62-b388-bef63cc5848a>
https://listserv.loc.gov/cgi-bin/wa?A2=ind0210&L=EAD&F=P&P=29408
response
<urn:uuid:2bc7d1b5-d68a-44da-91b2-04647229f2fd>
isPartOf: CC-MAIN-2021-10
publisher: Common Crawl
description: Wide crawl of the web for February/March 2021
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-59.ec2.internal
software: Apache Nutch 1.18 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.2-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/