Thanks for your interest Rick,
I would definitely like to add a link on the tools page, whenever that
is appropriate. It should probably be about the same time that I
register the profile. There are effectively two related profiles, one
for the working file and one for repository ingest. I think both files
are written to conform to the 1.9 METS schema, but I am not at my desk
right now.
We are not using Fedora's METS ingest offshoot. Instead our profile
captures many soon-to-be Fedora objects in a single document, along with
their hierarchy. These individual objects are translated into Fedora's
FOXML by ingest middle-ware we run in front of Fedora.
On a side note, anyone attending IDCC in Chicago next week can visit
with Erin O'Meara at our poster there. The tool is available for
experimentation at our download site: www.lib.unc.edu/software
kind regards,
Greg Jansen
On 12/3/2010 5:16 PM, Rick Beaubien wrote:
> Thanks for providing this information, Greg. This looks to me like
> something we would want to include on the METS tools page, especially if
> you plan to make it publicly available and it is (or becomes) applicable
> outside of the UNC/CDR work flow.
>
> I do have one question: Does the METS manifest that the Curator's
> workbench creates conform to the official METS schema
> (http://www.loc.gov/standards/mets/mets.xsd or one of its 1.x
> predecessors) or does it conform to the Fedora METS extension schema
> (http://fedora-commons.org/definitions/1/0/mets-fedora-ext1-1.xsd)?
> Even though the latter declares the same target namespace as the METS
> v.1.x schemas (unfortunately in my view), it differs from the mets.xsd
> in significant ways. And documents conforming to the mets-fedora-ext
> schema will not validate against the mets 1.x schemas. Particularly
> when we try to provide the community with information about available
> tools, this is a distinction that we need to make. Tools that produce
> mets for fedora ingest purposes may not be appropriate for broader METS
> applications.
>
> Also, especially if your tool does produce manifests conforming to a
> METS 1.x schema (as opposed to mets-fedora-ext1-1.xsd), I was wondering
> if you would have any interest in registering your CDR METS profile?
> This might help potential users of the Curator's Workbench.
>
> Thanks again for informing the community about this developing tool.
>
> Best,
> Rick Beaubien
>
>
> On 12/1/2010 1:48 PM, Greg Jansen wrote:
>> Hi METS,
>> I want to share a new METS-based software tool I've been developing at
>> the Univ. of NC at Chapel Hill. We call it the Curator's Workbench
>> and built it to process incoming collections for submission to our
>> repository. We just posted an overview of the tool in our blog:
>> http://bit.ly/en3dlL
>>
>> I should mention here that a METS file is the manifest for each
>> project, storing links to original and staged files as well as MODS
>> records. The export format for submission is also a METS XML
>> document, but with many irrelevant details stripped out.
>>
>> The tool is a good showcase for the flexibility of METS for work
>> flow. The manifest neatly tracks quite a bit of information as the
>> incoming folder tree is captured and arranged.
>>
>> Any suggestions are more than welcome.
>>
>> thanks,
>> Greg Jansen
>>
|