Print

Print


Hi Christopher,

If you are aggreggating files from numerous repositories into
one database, then you should consider assigning a unique ID to each
repository for starters.  This way you are able to identify the XML files
uniquely.

As for the <eadid> contents, a number of fields can be combined to form a
primary key delimited by a non-alphanumeric charcters (e.g *,:,/,;)

For example,
RepositoryUniqueId::repositoryName::XMLfileName::OtherHeaderInformationaboutFindingAid

This way you are sure to avoid duplicates.
Another approach would be to assign URL or URNs which are unique in their
own nature.  Its just a matter of preference.


Best Regards,

Aman Singh
XML Programmer
York University Archives and Special Collections



>From: christopher j prom <[log in to unmask]>
>Reply-To: Encoded Archival Description List <[log in to unmask]>
>To: [log in to unmask]
>Subject: <eadid> element
>Date: Mon, 31 Dec 2001 11:46:00 -0600
>MIME-Version: 1.0
>Received: from [140.147.249.48] by hotmail.com (3.2) with ESMTP id
>MHotMailBDF9F26200C94004319C8C93F930A1B50; Mon, 31 Dec 2001 09:59:01 -0800
>Received: from sun8 (sun8 [140.147.249.48])by sun8.loc.gov
>(8.8.8+Sun/8.8.8) with ESMTP id MAA13733;Mon, 31 Dec 2001 12:47:44 -0500
>(EST)
>Received: from LISTSERV.LOC.GOV by LISTSERV.LOC.GOV (LISTSERV-TCP/IP
>release          1.8d) with spool id 74557 for [log in to unmask]; Mon,
>31 Dec 2001          12:47:05 -0500
>Received: from staff1.cso.uiuc.edu (staff1.cso.uiuc.edu [128.174.5.59]) by
>         sun8.loc.gov (8.8.8+Sun/8.8.8) with ESMTP id MAA13641 for
><[log in to unmask]>; Mon, 31 Dec 2001 12:47:03 -0500 (EST)
>Received: from localhost (prom@localhost [127.0.0.1]) by
>staff1.cso.uiuc.edu          (8.11.0/8.11.0) with ESMTP id fBVHk0U16992 for
><[log in to unmask]>; Mon, 31          Dec 2001 11:46:00 -0600 (CST)
>From [log in to unmask] Mon, 31 Dec 2001 10:00:38 -0800
>X-X-Sender:  <[log in to unmask]>
>Message-ID:  <[log in to unmask]>
>Sender: Encoded Archival Description List <[log in to unmask]>
>Comments: To: [log in to unmask]
>
>Can anyone on the list offer some comment on how the <eadid> element is
>being used?  It is intended to provide a unique identifier, but as part of
>a project I am involved it, I am having trouble deciding whether it can be
>reliably used to point to the location of the actual EAD file.  This
>becomes an issue when you aggreggate files from numerous repositories into
>one database (like I am attempting to do)
>
>I notice versions encoded in SGML typically include SGML catalog entries,
>but
>what are people doing for XML files?  Is anyone using a handle technology
>like URN's or DOI's that are resolvable?  Do people use URL.  Or are
>people just giving a local file name or identifier along with a systemID
>attribute?  That has been my past practice.
>
>
>Chris Prom
>Assistant University Archivist
>University of Illinois Archives
>Room 19 Library (MC-522)
>1408 W. Gregory Drive
>Urbana, IL 61801
>
>web:    http://www.library.uiuc.edu/ahx/
>e-mail: [log in to unmask]
>phone:  217 333 0798
>fax:    217 333 2868




_________________________________________________________________
MSN Photos is the easiest way to share and print your photos:
http://photos.msn.com/support/worldwide.aspx