Jason,
The AIP and default SWORD Packaging are biased towards METS, you'll want to
write your own packager to support the NLM Manifest format. To show you a
similar approach, here is the iMSCP IMLS packager used by MIT to ingest and
disseminate IMSCP Packages of OCW courses.
http://scm.dspace.org
Thanks, Tim, for taking a shot at it. Sorry for being too vague. The
requirements are pretty loose.
In this case, I have Community/Collection owners wanting to export content to
National Library of Medicine for indexing. For now at least, they'll need to
export the complete contents of a new
Hi Jason,
I'm not sure I fully follow your use case, but a few things you may wish
to look at (if you haven't already):
* If you are looking at exporting METS + bitstreams, have you taken a
look at the AIP Backup & Restore feature (which generates "AIPs" that
are just zipped up METS files + bi
I need some advice on the best (easiest, preferred) lightweight method for
exporting crosswalked metadata and bitstreams. I've read the crosswalk
configuration docs at
http://www.dspace.org/1_7_1Documentation/Configuration.html#Configuration-CrosswalkandPackagerPluginSettings
and the sysadmin
4 matches
Mail list logo
