Would you send me a copy also, please, to look at.
Truly yours,
Lois Peterson
Frederick Douglass Library
University of Maryland Eastern Shore
Princess Anne, MD 21853
-----Original Message-----
From: Encoded Archival Description List [mailto:[log in to unmask]] On Behalf
Of Rees, John (NIH/NLM)
Sent: Tuesday, March 15, 2005 5:11 PM
To: [log in to unmask]
Subject: Re: Access to EAD
Lynn,
As Chris says, the top level EAD info is usually pretty easy to pull
from a
flat-ish dbase table--the hard part is getting out container level data,
if
you have it, and having the nesting nicely done. The Berkeley approach
uses
Access's reporting tools, which we found to be quite buggy, esp. for
large
finding aids
We have an Access solution that does all this a bit more elegantly by
writing out files directly from the dbase. I've presented this tool at
various venues and am happy to send you an empty copy to play with.
John
John P. Rees, MA, MLIS
Curator, Archives and Modern Manuscripts
History of Medicine Division
National Library of Medicine
8600 Rockville Pike
Bethesda, MD 20894
Phone: 301.496.8953
Fax: 301.402.7034
> -----Original Message-----
> From: Chris Prom [mailto:[log in to unmask]]
> Sent: Tuesday, March 15, 2005 4:24 PM
> To: [log in to unmask]
> Subject: Re: Access to EAD
>
>
> Lynn,
>
>
> You could also use the PHP and especially its xml extensions
> to accomplish this result. The access file would not
> necessarily need to be flat, but it would need to comply with
> content standards and/or be easily mappable to EAD elements.
> You could pull data from related tables out with a series of
> sql inner joins, but you would need some pretty heavy hitting
> programming to do all this. It is possible, but at least as
> complicated as using xsl.
>
> Thanks,
>
> Chris
>
> --
>
> Christopher J. Prom
> Assistant University Archivist and
> Assistant Professor of Library Administration
> University of Illinois at Urbana Champaign
> 19 Library
> 1408 W. Gregory Dr.
> Urbana, IL 61801
>
> phone: 217.333.0798
> fax: 217.333.2868
> e-mail: [log in to unmask]
> web: http://web.library.uiuc.edu/ahx
>
> On Tue, 15 Mar 2005, Chatham Ewing wrote:
>
> > Lynn,
> >
> > Late model Access (2003) will produce XML output, even from
> relational
> > files. But it seems to do best with flat files.
> >
> > If the data in your Access database is flattish and already
> formatted
> > to be compliant with a content standard that satisfies you,
> like DACS
> > (is
> > it?) and the fields you have in your database easily map to
> EAD tags (do
> > they?), then it becomes a matter of transforming the database's XML
> > output into EAD using XSL.
> >
> > Chatham
> >
> >
> > -----Original Message-----
> > From: Encoded Archival Description List
> [mailto:[log in to unmask]] On Behalf
> > Of Lynn Lobash
> > Sent: Tuesday, March 15, 2005 2:54 PM
> > To: [log in to unmask]
> > Subject: Access to EAD
> >
> > I have an Access database and would like to produce an EAD encoded
> > file. Any help appreciated.
> >
> > Lynn Lobash
> >
>
|