Sorry all. This message was meant for the individual, not the list. Hoping
my BCC is not turned on, as I didn't see the EAD list in my Reply field.

john

> -----Original Message-----
> From: Glenn Gardner [mailto:[log in to unmask]]
> Sent: Friday, March 18, 2005 2:10 PM
> To: [log in to unmask]
> Subject: Re: Access to EAD
>
>
> Just so everyone knows, the EAD Listserv generally blocks
> attachments automatically (to help prevent the spread of
> viruses and malware). You can always email the intended
> recipient directly to their email address and that should work.
>
> Also, there is now a zipped file download option of the DTD
> files on the Official EAD Version 2002 Web site at:
> http://www.loc.gov/ead/
>
> .. contained under the "EAD DTD Official Documentation for
> Version 2002" heading.  Thanks to Corey Keith at the Library
> of Congress for his assistance.
>
> Best,
>
> Glenn
>
> Glenn Gardner
> Network Development & MARC Standards Office
> Library of Congress
> Washington, D.C.  USA  20540-4402
> Ph: +1 (202) 707-7414             Internal: LS/TECH/NDMSO (4402)
>
> >>> [log in to unmask] 03/18/05 11:52 AM >>>
> Lois,
>
> Attached is a zip with the current dbase with some sample
> files, dated documentation, and an import xsl we use for
> large box lists that helps save some data entry time.
>
> The tool is set up for the 90% type of guides we produce and
> is a bit inflexible when it comes to adding extra tags. I
> hand-edit for that other 10% during post-production
> processes. Some aspects are unwieldy for sure but this is
> what I knew how to do with what little Visual Basic I have.
>
> Let me know what you think.
>
> 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: Peterson, Lois A. [mailto:[log in to unmask]]
> > Sent: Friday, March 18, 2005 10:24 AM
> > To: [log in to unmask]
> > Subject: Re: Access to EAD
> >
> >
> > 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
> > > >
> > >
> >
>