Hey Curtis,
It is as modular as you want it to be - and as your XSL skill level
permits. You can set it up to output other profiles, but you will need
to modify the code to structure the METS accordingly. To put it
differently, it isn't aware of METS profile documentation or differences
between profiles.
The out-of-the-box version is configured to output the CDL CONTENTdm
METS Profile (http://www.loc.gov/mets/profiles/00000010.xml). See
Customization.txt for more information on how to modify the code. Also,
there is as much commenting in the .xsl files as we could include, so
reading some of the comments may be helpful.
Paul Fogel
California Digital Library
[log in to unmask]
510.987.0680
Curtis Fornadley wrote:
>
> Hi
>
> How modular is it;
>
> can it accomdomate the output of METS to other profiles besides the
> CDL profile?
>
>
>
> bye
>
> Curtis Fornadley
> Digital Library Architect
>
> ----- Original Message -----
> From: paul fogel <[log in to unmask]>
> Date: Wednesday, July 12, 2006 10:00 am
> Subject: Re: [METS] 7train METS generation tool
> To: [log in to unmask]
>
> > Hi Jody,
> >
> > Thank you for the kind message.
> >
> > 7train was designed in such a way that it can be modified to
> > accommodate
> > XML of any flavor. The one caveat I make to that statement is
> > that a
> > requirement of the system (and of METS in general) is that the XML
> > 1.)
> > identifies all of the files that make up the object and 2.)
> > describes
> > how those files fit together (the structure). We had focused on
> > CONTENTdm XML for our initial release as that system was involved
> > in the
> > project that spawned 7train's development.
> >
> > I am more than willing to talk to you in more detail about what
> > the
> > above paragraph means. Feel free to call or email.
> >
> > In the meantime, please look over the following files included
> > with the
> > tool, including some sample files (input & transformation):
> >
> > Customizing.txt
> > examples/oai.xsl
> > examples/oai-sample.xml
> >
> > Also, the Documentation webpage for the project
> > (http://seventrain.sourceforge.net/7train_documentation.html)
> > gives a
> > little more information that may be helpful.
> >
> > Best,
> >
> > Paul Fogel
> > California Digital Library
> > [log in to unmask]
> > 510.987.0680
> >
> >
> >
> > Deridder, Jody L wrote:
> > > Paul! This is very exciting. Especially since XTF needs METS
> > records> for input, and especially since we have 10,000 items on
> > their way that
> > > need METS records for DAITSS.
> > > However, we do not have ContentDM, so I have no idea what a
> > sample> export record from that software looks like. Would you be
> > willing to
> > > provide a handful of sample input files with the software?
> > >
> > > Jody DeRidder
> > > IT Administrator
> > > Digital Library Center
> > > University of Tennessee Libraries
> > >
> > >
> > >
> > >> -----Original Message-----
> > >> From: Metadata Encoding and Transmission Standard
> > >> [mailto:[log in to unmask]] On Behalf Of paul fogel
> > >> Sent: Wednesday, June 21, 2006 4:31 PM
> > >> To: [log in to unmask]
> > >> Subject: [METS] 7train METS generation tool
> > >>
> > >> The California Digital Library (CDL) is pleased to announce
> > >> the release of "7train", an XSLT 2.0-based tool for
> > >> generating Metadata and Encoding Transmission Standard (METS)
> > >> files from standardized XML inputs.
> > >> Version 1 of the open-source, platform-independent tool is
> > >> available via Sourceforge at http://seventrain.sourceforge.net.
> > >>
> > >> 7train was designed to transform XML documents into METS
> > >> files conforming to a specific METS profile. This initial
> > >> implementation was designed with the goal of transforming
> > >> exports from the CONTENTdm digital asset management tool
> > >> (Version 4.0 and higher) into the CDL 7train METS profile,
> > >> available at http://www.loc.gov/mets/profiles/00000010.xml,
> > >> which is suitable for inclusion in CDL repositories.
> > >> However, the tool can be customized to produce METS files
> > >> from any kind of standardized XML document (e.g, OAI records).
> > >>
> > >> The tool was developed through the CDL's work in the
> > >> "California Local History Digital Resources Project", a
> > >> multi-year LSTA grant-funded project that explores a model to
> > >> aggregate, preserve, and provide permanent public access to
> > >> digitized local history content via a statewide online access
> > point.>>
> > >> The CDL invites METS implementors and CONTENTdm users to
> > >> utilize and comment on the toolkit. The Sourceforge web page
> > >> contains contact information for feedback.
> > >>
> > >> --
> > >> Paul Fogel
> > >> California Digital Library
> > >> [log in to unmask]
> > >> 510.987.0680
> > >>
> > >>
> > >
> > >
> >
>
|