Hi Susan --
I'm curious about the Saxon jvm/PDF process that you mention. Could
you provide a little more detail on this? We are also using saxon/HTML
for web presentation but printing them is, to say the least, not
optimal, so I'd be interested in how you're creating the PDFs.
Special Collections Research Center
Syracuse University Library
222 Waverly Avenue
Syracuse, NY 13244
>>> [log in to unmask] 5/23/2006 5:27 PM >>>
We are planning to export finding aids from a database into EAD-tagged
documents and ingest them into DLXS for federated searching. The
want to know if the entity declaration in the PUBLIC identifier that I
currently use for XMetaL-created finding aids is necessary. I
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
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
In the example below, is "beebe.sgm" necessary or could it be
or simply "beebe"? The techie is changing the name to "beebe1" without
.xml or .sgm extension before ingesting it into DLXS and it seems to
<?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
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