Thanks, Stephen. I'm hesitant to use the URL because we've already had one
instance where the library changed the pathway and I had to go back and
change all of the finding aids (not too much of a problem when there were
only 50 but once we export everything from the database it will be over
At 08:22 AM 5/24/2006, you wrote:
>Short answer is no, it doesn't matter. The <eadid> is merely meant to
>provide a globally unique string of characters that identify your finding
>aid. Since you are using EAD 2002, I would suggest however that you
>consider something like:
><eadid publicid="-//Pennsylvania State University::University
>Libraries::Special Collections Library//TEXT (US::PSt::MGN324::Helen
>Hulick Beebe Papers, 1927-1998//EN">beebe.WHATEVER</eadid>
>Or even substitute the publicid attribute with 'url' and reference the URL
>of the final location of the instance document.
>Yale University Library::Manuscripts and Archives
>On 5/23/06, Susan Hamburger
><<mailto:[log in to unmask]>[log in to unmask]> wrote:
>We are planning to export finding aids from a database into EAD-tagged XML
>documents and ingest them into DLXS for federated searching. The techies
>want to know if the entity declaration in the PUBLIC identifier that I
>currently use for XMetaL-created finding aids is necessary. I currently
>create my finding aids in an XMetaL template as SGML files then convert
>them to XML with NoteTabPro, run the Saxon frameset to create HTML versions
>for display on the Web, and run Saxon jvm to create PDFs for printable
>copies. All this conversion will be moot when we ingest the XML document
>In the example below, is "beebe.sgm" necessary or could it be " beebe.xml"
>or simply "beebe"? The techie is changing the name to "beebe1" without a
>.xml or .sgm extension before ingesting it into DLXS and it seems to work
><?xml version=" 1.0" encoding="ISO-8859-1"?>
><!DOCTYPE ead SYSTEM "file:/c:\pubclass\shared\ead\ead.dtd" [
><!ENTITY psulogo PUBLIC "-//Pennsylvania State University::University
>Libraries::Special Collections Department//NONSGML (PSU logo)//EN"
>"file:/C:\pubclass\documents\psulogo.gif" NDATA gif>
> >PUBLIC "-//Pennsylvania State University::University
> Libraries::Special Collections Library//TEXT (US::PSt::MGN
>324::Helen Hulick Beebe Papers, 1927-1998//EN" "beebe.sgm"</eadid> . . .
>Am I worrying about retaining legacy data that is unnecessary or is there a
>good reason that the extension should remain? Thanks for your insight.
>Susan Hamburger, Ph.D.
>Manuscripts Cataloging Librarian
>126 Paterno Library
>The Pennsylvania State University
>University Park, PA 16802