|
--simple boundary
Content-Type: text/plain; charset=US-ACSII
Content-Transfer-Encoding: 7bit
Message is undeliverable.
Reason: User "[log in to unmask]" is not found in the cc:Mail Directory.
Original text follows:
---------------------
--simple boundary
Content-Type: text/plain; charset=US-ACSII
Content-Transfer-Encoding: 7bit
Received: from rs8.loc.gov by library.sos.state.il.us (ccMail Link to SMTP R8.00.01)
; Wed, 08 Oct 97 18:25:58 -0600
Return-Path: <[log in to unmask]>
Received: from rs8 (rs8.loc.gov [140.147.248.8])
by rs8.loc.gov (8.8.4/8.8.4) with SMTP
id TAA78036; Wed, 8 Oct 1997 19:26:11 -0400
Received: from RS8.LOC.GOV by RS8.LOC.GOV (LISTSERV-TCP/IP release 1.8b) with
spool id 211382 for [log in to unmask]; Wed, 8 Oct 1997 19:26:09 -0400
Received: from sos.state.il.us (ftp.sos.state.il.us [199.15.1.2]) by
rs8.loc.gov (8.8.4/8.8.4) with SMTP id TAA54004 for <[log in to unmask]>;
Wed, 8 Oct 1997 19:16:03 -0400
Received: from library.sos.state.il.us (ccgate.sos.state.il.us [199.15.1.5]) by
sos.state.il.us (8.6.12/8.6.12) with SMTP id TAA20388 for
<[log in to unmask]>; Wed, 8 Oct 1997 19:24:25 -0500
Received: from ccMail by library.sos.state.il.us (ccMail Link to SMTP R8.00.01)
id AA876352190; Wed, 08 Oct 97 18:09:51 -0600
X-Mailer: ccMail Link to SMTP R8.00.01
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="simple boundary"
Message-ID: <[log in to unmask]>
Date: Wed, 8 Oct 1997 18:09:50 -0600
Reply-To: Encoded Archival Description List <[log in to unmask]>
Sender: Encoded Archival Description List <[log in to unmask]>
From: [log in to unmask]
Subject: cc:Mail Link to SMTP Undeliverable Message
Comments: To: [log in to unmask]
To: Multiple recipients of list EAD <[log in to unmask]>
--simple boundary
Content-Type: text/plain; charset=US-ACSII
Content-Transfer-Encoding: 7bit
Message is undeliverable.
Reason: User "[log in to unmask]" is not found in the cc:Mail Directory.
Original text follows:
---------------------
--simple boundary
Content-Type: text/plain; charset=US-ACSII
Content-Transfer-Encoding: 7bit
Received: from rs8.loc.gov by library.sos.state.il.us (ccMail Link to SMTP R8.00.01)
; Wed, 08 Oct 97 18:09:48 -0600
Return-Path: <[log in to unmask]>
Received: from rs8 (rs8.loc.gov [140.147.248.8])
by rs8.loc.gov (8.8.4/8.8.4) with SMTP
id TAA50918; Wed, 8 Oct 1997 19:10:58 -0400
Received: from RS8.LOC.GOV by RS8.LOC.GOV (LISTSERV-TCP/IP release 1.8b) with
spool id 211332 for [log in to unmask]; Wed, 8 Oct 1997 19:10:57 -0400
Received: from sos.state.il.us (ftp.sos.state.il.us [199.15.1.2]) by
rs8.loc.gov (8.8.4/8.8.4) with SMTP id TAA31562 for <[log in to unmask]>;
Wed, 8 Oct 1997 19:00:56 -0400
Received: from library.sos.state.il.us (ccgate.sos.state.il.us [199.15.1.5]) by
sos.state.il.us (8.6.12/8.6.12) with SMTP id TAA20363 for
<[log in to unmask]>; Wed, 8 Oct 1997 19:09:17 -0500
Received: from ccMail by library.sos.state.il.us (ccMail Link to SMTP R8.00.01)
id AA876351282; Wed, 08 Oct 97 17:54:44 -0600
X-Mailer: ccMail Link to SMTP R8.00.01
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="simple boundary"
Message-ID: <[log in to unmask]>
Date: Wed, 8 Oct 1997 17:54:42 -0600
Reply-To: Encoded Archival Description List <[log in to unmask]>
Sender: Encoded Archival Description List <[log in to unmask]>
From: [log in to unmask]
Subject: cc:Mail Link to SMTP Undeliverable Message
Comments: To: [log in to unmask]
To: Multiple recipients of list EAD <[log in to unmask]>
--simple boundary
Content-Type: text/plain; charset=US-ACSII
Content-Transfer-Encoding: 7bit
Message is undeliverable.
Reason: User "[log in to unmask]" is not found in the cc:Mail Directory.
Original text follows:
---------------------
--simple boundary
Content-Type: text/plain; charset=US-ACSII
Content-Transfer-Encoding: 7bit
Received: from rs8.loc.gov by library.sos.state.il.us (ccMail Link to SMTP R8.00.01)
; Wed, 08 Oct 97 17:54:39 -0600
Return-Path: <[log in to unmask]>
Received: from rs8 (rs8.loc.gov [140.147.248.8])
by rs8.loc.gov (8.8.4/8.8.4) with SMTP
id SAA71512; Wed, 8 Oct 1997 18:53:59 -0400
Received: from RS8.LOC.GOV by RS8.LOC.GOV (LISTSERV-TCP/IP release 1.8b) with
spool id 211315 for [log in to unmask]; Wed, 8 Oct 1997 18:53:58 -0400
Received: from library.berkeley.edu (library.Berkeley.EDU [128.32.224.55]) by
rs8.loc.gov (8.8.4/8.8.4) with SMTP id SAA56384 for <[log in to unmask]>;
Wed, 8 Oct 1997 18:53:56 -0400
Received: from moff250-136.Lib.Berkeley.EDU by library.berkeley.edu;
(5.65v3.2/1.1.8.2/29Oct94-1209AM) id AA09418; Wed, 8 Oct 1997
15:56:50 -0700
X-Sender: [log in to unmask]
X-Mailer: Windows Eudora Pro Version 3.0 (32)
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Message-ID: <[log in to unmask]>
Date: Wed, 8 Oct 1997 15:53:10 -0700
Reply-To: Encoded Archival Description List <[log in to unmask]>
Sender: Encoded Archival Description List <[log in to unmask]>
From: Alvin Pollock <[log in to unmask]>
Subject: Re: dsc type="combined" with tabular layout questions
Comments: To: Encoded Archival Description List <[log in to unmask]>
To: Multiple recipients of list EAD <[log in to unmask]>
Hi Susan,
We use the tabular markup almost exclusively in our
Online Archive of California Project (aka UC-EAD).
There are many, many different ways to use EAD tabular
markup in a container list. There is no one, "right"
way. You've seen the description of our way of applying
tabular markup in the retrospective conversion guidelines
(see: http://sunsite.berkeley.edu/amher/upguide.html#Appen )
It contains no examples of a "combined" container list
as you pointed out. The salient point to remember when
applying the American Heritage/UC-EAD tabular markup guide-
lines is that series, subseries, recordgrps, subgrps, etc.,
appear in <did><unittitle></unittitle></did> and non-series-
like entries appear in <drow><dentry>. For combined container
lists, simply follow the closing </did> with your scopecontent,
odd, etc. information. Here's an example:
<dsc type="combined">
<head>Container List</head>
<tspec> ... </tspec>
<c01 level="series">
<did>
<unittitle>Correspondence, <unitdate>1961-1977</unitdate>
</unittitle></did>
<scopecontent>
<arrangement><p>Arranged chronologically.</p></arrangement>
<p>Personal and professional letters of Woodbridge Bingham.
Incoming (and outgoing, as well as neither to nor from)
letters also appear in three general subject files in
carton 7: folder 20 concerns an embezzlement charge against
an old family friend, J. R. Moulthrop; Navy correspondence
is found in folders 24-27; and, folder 33 concerns a takeover
threat at Tiffany & Company. Correspondence with Bingham's
co-authors and publishers is also found among the textbook
materials in Series 12.</p></scopecontent>
<thead>
<row>
<entry spanname="c1-3">Box</entry>
<entry spanname="c4-16">Contents</entry>
<entry spanname="c17-20">Dates</entry>
</row>
</thead>
<c02>
<drow>
<dentry spanname="c1-3">
<unitloc loctype="container" containertype="box">1</unitloc>
</dentry>
<dentry spanname="c4-16">
<unittitle>Fragments</unittitle></dentry>
<dentry spanname="c17-20">
<unitdate>1966-1970</unitdate></dentry></drow></c02>
We have certainly lived to tell about our experience using
tabular markup. It's pretty complicated to learn how to do
when you first start with it but once it's incorporated into
scripted and programmatic markup it takes no longer to encode
a container list than does non-tabular markup. If you're
doing it all by hand however, then you're looking at a pretty
labor-intensive process.
Please feel free to contact me concerning any questions
you might have about the American Heritage/UC-EAD flavor
of tabular markup. We've stumbled across quite a few tricks
that streamline the process considerably (such as omitting
</c> end tags during markup and putting them in programmatically
using an sgml normalizing tool like sgmlnorm when you're done).
Very best regards,
Alvin Pollock
Electronic Text Unit
UC Berkeley Library
[log in to unmask]
At 05:38 PM 10/8/97 -0400, you wrote:
>The GAMMA project, a NEH-funded collaborative cataloging project within
>the University Center in Georgia has received a grant from the Georgia
>Historical Records Advisory Board to engage in a small EAD DTD project.
>
>We have explored all the wonderful information that the early implementors
>of EAD have put out there on the internet (which followers are much
>appreciative of). However, we do seem to have hit a small snag in our
>encoding which we can't seem to find the answer for.
>
>We were hoping to use the <dsc type="combined"> with the tabular layout,
>however examples of this are few and far between. We have
>perused the information presented in the "Encoded Archival
>Description Retrospective Conversion Guidelines" about the tabular
>layout. We have also beat our heads against the wall for three days.
>Is there any brave soul out there that has survived the
>tabular layout and lived to tell of it? Your help would be much
>appreciated.
>
>Susan Potts McDonald
>Emory University Special Collections
>GAMMA Project
>
>
--simple boundary--
--simple boundary--
--simple boundary--
|
