Michele R.,
I fully appreciate your concern in delivering EAD to users.
One question I always get is "How can we see the document once it is
coded?"
My goal was to create a stylesheet that would transform the EAD XML
into PDF (via XSL-FO). I have created a sister stylesheet to the HTML
(used in my conversion toolkit) that transforms the EAD into PDF. I
really don't see a better display document format for EAD than PDF.
In doing so, I was able to overcome the 2 tier document system that
was being previously maintained (EAD and word processor). Now, PDF
documents will be used on the finding aid site as well as in the
reading room.
Further, I have derived the content of the meta data tags from the
ARCHDESC/DID. This really enables search engines like Google to pick
up the document quickly (try: Serge Koussevitzky Archive). I hope to
convince some others to develop a JAVA extension for creating XMP
with a MODS schema.
I don't have any issues with HTML, but it really is a stop-gap for
our data. Browsers are really infuriating for creating an outlined
format (hanging indents??; wrap control??; script issues). XHTML will
be really nice (when I am given the green light on that one as
well...).
As for delivering XML, I think it is good to offer the XML document
to users. But maybe someone can answer the question of how ENTITY
(ent) files are delivered with the XML document?
In any case, I am very happy with the PDF finding aids and hope to
continue to increase this production. I really believe that we can
have our cake and eat it too using this type of approach.
Sincerely,
Mike Ferrando
Library Technician
Music Division
Library of Congress
Washington, DC
202-707-4454
Music Division Finding aids page:
http://www.loc.gov/rr/perform/special/gd-index.html
--- MicheleR <[log in to unmask]> wrote:
> Hi all --
>
> In discussing the various EAD issues in a meeting today, we began
> exploring
> how one delivers the EAD documents to the end user. We considered
> delivering XML directly but obviously that excludes people without
> XML-capable browser. We considered converting the XML documents
> into HTML
> but that results in a duplicate set of data, thus two sets of docs
> to be
> updated. We considered on-the-fly rendering of XML to HTML, done
> on the
> server side. We considered cross-walking to Dublin Core and
> putting them in
> ContentDM...plus a few more "wild hares."
>
> So I thought I would survey the collective wisdom. How are most
> people
> using/delivering EAD-encoded finding aids?
>
> Regards
>
> Michele
> Syracuse University
>
>
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.802 / Virus Database: 545 - Release Date: 11/27/2004
>
__________________________________
Do you Yahoo!?
Yahoo! Mail - Helps protect you from nasty viruses.
http://promotions.yahoo.com/new_mail
|