Michelle, what are you actually trying to create? Just a summary list
of things from all the EAD files?
Mark A. Matienzo
Applications Developer, Digital Experience Group
The New York Public Library
On Fri, Mar 6, 2009 at 12:44 PM, Michele R Combs <[log in to unmask]> wrote:
> Hm, yes, that would work. I'd prefer not to list the EAD files by name though, rather have it just run through all the files currently in the directory. That way a) shorter style sheet, as you rightly point out (we have over 1000 EADs at the moment), and b) I can re-run the script on a regular basis to generate an updated output file (we're adding new EAD files every week).
>
> Michele
>
> -----Original Message-----
> From: Encoded Archival Description List [mailto:[log in to unmask]] On Behalf Of Custer, Mark
> Sent: Friday, March 06, 2009 12:29 PM
> To: [log in to unmask]
> Subject: Re: Mutiple EADs to single output
>
> Well that certainly work, then, but there's probably a better way depending on your overall plan. That said, using the document function, you could setup a stylesheet to output xml, and then do something like:
>
> <xsl:value-of select="document('EAD001.xml')/ead/eadheader/@audience"/>
> <xsl:value-of select="document('EAD002.xml')/ead/eadheader/@audience"/>
> Etc.
>
> Placing whatever XML skeleton you needed around those values.
>
> As long as you have a list of the EAD documents that you'd need to include, you should be able to include every EAD file that you have pretty easily (though that make the stylesheet quite long).
>
>
> Mark Custer
>
>
>
> -----Original Message-----
> From: Encoded Archival Description List [mailto:[log in to unmask]] On Behalf Of Michele R Combs
> Sent: Friday, March 06, 2009 12:17 PM
> To: [log in to unmask]
> Subject: Re: Mutiple EADs to single output
>
> Process = ingest, transform, take as input, suck data from -- pick your term :) Essentially I want to build a single XML file (non-EAD) that contains certain bits of data culled from all our EAD files.
>
> Michele
>
> -----Original Message-----
> From: Encoded Archival Description List [mailto:[log in to unmask]] On Behalf Of Custer, Mark
>
> That's the first thing that comes to mind, at least, but I'm not sure I understand exactly what you mean by "process".
>
> Mark
>
>
|