|>>>>> "BD" == Bob Dunn <RGD122@psulias.psu.edu> writes:
BD> We are considering implementing Greenstone for use throughout the
BD> library's preservation department. In order to facilitate the
BD> large-scale scanning of documents, many people will need to be
BD> able to access and change metadata for any given collection.
BD> Rather than using the Librarian Interface, we have considered
BD> building a web front-end that would take any amount of data and
BD> generate configuration files automatically.
BD> While we could build the configuration directly as GSDL objects,
BD> we want to consider the possibility of creating METS objects
BD> first, then converting that METS object into a GSDL compatible
BD> Has anyone found or created a transformation schema that does
BD> this conversion automatically?
We used a similar approach. Our Preservation Department records a
bunch of data in an RDB at scanning time and exports text files that
we use to generate digital collections. Some of this was outlined as
part of a talk at DLF in the fall. Slides and handouts are at:
The handouts may be more useful, as the slides are mostly pictures
that I'd talk about. If you DON'T use the slideshow, you'll see the
outline slides that were hidden. Anyhow, the METS to GSAF mapping is
pretty natural. I can share the XSLT we use, though it is fairly
custom to our local needs.
BD> Does anyone have any additional insight we have missed?
Will all of your collections be using the same metadata set? If not,
you'll want to allow for that in your METS construction stream and in
the METS to GSAF transformation. Should be easy enough to check the
dmdSec attributes and invoke the correct template (assuming XSLT).
Tod A. Olson <email@example.com> "How do you know I'm mad?" said Alice.
Sr. Programmer / Analyst "If you weren't mad, you wouldn't have
The University of Chicago Library come here," said the Cat.