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/svn/repo/modules/dspace-imscp/trunk/src/main/java/org/dspace/content/packager/
We do need more examples of Packages that are not METS based so this would
be an excellent opportunity to reinforce to the community that while METS is
great, we need to be sure we are not stick with it being the only solution.
It needs to be clarified that SWORD is not bound to just accepting Its
METS/SWAP packaging format, we worked with MIT to asure they could push
thier packaging format through SWORD as well.
Mark
On Thursday, September 15, 2011, Jason Stirnaman <[email protected]>
wrote:
> 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 collection each time. So, selecting
the content is pretty straightforward whether I use the AIP or OAI.
>
> The metadata has to follow NLM's schema which is why I assume an XSLT
crosswalk is best.
>
> The bitstreams need to be bundled up with, and referenced locally by, the
metadata.
>
> Downloading to a specific location would be ideal, but exporting to the
DSpace server filesystem is fine; I can get it to them from there.
>
> Yes, I think the AIP B&R is what I was referring to. It's just a little
unclear in the sysadmin documentation what the relationship is between the
METS and AIP packagers.
>
> Given that's what I wanted, how would I specify a crosswalk for the AIP
feature to transform METS to NLM? Or is that even possible without writing a
custom packager?
>
> And if Graham or anyone else is using DSpace to get stuff to NLM or other
indexers then I would love to hear from you.
>
> Jason
>
> Jason Stirnaman
> Biomedical Librarian, Digital Projects
> A.R. Dykes Library, University of Kansas Medical Center
> [email protected]
>
913-588-7319 <tel:913-588-7319> <tel:913-588-7319 <tel:913-588-7319>>
<tel:913-588-7319 <tel:913-588-7319> <tel:913-588-7319
<tel:913-588-7319>>>
>
>
>>>> On 9/15/2011 at 12:34 PM, in message <[email protected]>,
Tim Donohue <[email protected]> wrote:
>
> 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 + bitstreams):
> https://wiki.duraspace.org/display/DSDOC/AIP+Backup+and+Restore
> More about the AIP format here:
> https://wiki.duraspace.org/display/DSDOC/DSpace+AIP+Format
>
> * If you are interested in hooking up Curation Tasks to
> Packagers/Disseminators, that is possible. In fact, Richard Rodgers & I
> are working on a 1.8.0 "add-on" called the Replication Suite, which
> brings AIP export/import to Curation Tasks:
> https://wiki.duraspace.org/display/DSPACE/ReplicationTaskSuite
> More details in my slides from OR11 on using Replication Suite to
> backup/restore to/from DuraCloud:
> http://www.slideshare.net/tdonohue/dspace-duracloud-integrations
>
> I'm not sure if either of these will help your use case or not, but both
> are examples of using Packagers (along with crosswalks) to export METS +
> bitstreams and enable that via Curation Tasks.
>
> Perhaps if you described your use case a bit more? Is what you are
> building an Administrator tool? End user tool? Is it a specific METS
> format/profile you need, or specific Metadata schemas? When they
> "export" are they actually needing to download it to a specific
> location, or just export to the filesystem on the server where DSpace is
> running? (the latter is how the Replication Suite works, unless you
> connect it to DuraCloud or point it at a mounted drive)
>
> - Tim
>
> On 9/15/2011 11:32 AM, Jason Stirnaman wrote:
>> 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
>> <
http://www.dspace.org/1_7_1Documentation/Configuration.html#Configuration-CrosswalkandPackagerPluginSettings
>_/and
>> the sysadmin packager docs at
>> /_
http://www.dspace.org/1_7_1Documentation/System%20Administration.html#SystemAdministration-PackageImporterandExporter
>> <
http://www.dspace.org/1_7_1Documentation/System%20Administration.html#SystemAdministration-PackageImporterandExporter
>_/as
>> well as some of the plugin stuff.
>>
>> Specifically, I need to enable some users to export a new collection of
>> items and their bitstreams on a regular basis and ultimately ftp it
>> somewhere. I need to do some transformation of the metadata. All the
>> elements I need are in METS I think. I'm using DSpace 1.7.1.
>>
>> Here are my thoughts and options so far:
>>
>> 1. I'll likely need to use an XSLT crosswalk. In the config,
>> schemalocation is required. Does DSpace actually look for the xsd? Is it
>> possible to point to a DTD instead?
>>
>> 2. I could write a separate client app to retrieve the oai METS and
>> referenced bitstreams over HTTP, but I think I'd prefer to keep as much
>> as possible within DSpace. Although, a good tradeoff might be put my
>> crosswalk in DSpace and then collect everything over HTTP. I don't
>> currently have the REST API installed and I'm not sure what I would gain
>> from it here, but I guess that would be an option as well.
>>
>> 3. Ignoring #2, I could use the METS package disseminator with my
>> crosswalk, but I'm still unc
--
Mark R. Diggory
@mire - www.atmire.com
2888 Loker Avenue East - Suite 305 - Carlsbad - CA - 92010
Esperantolaan 4 - Heverlee 3001 - Belgium
------------------------------------------------------------------------------
Doing More with Less: The Next Generation Virtual Desktop
What are the key obstacles that have prevented many mid-market businesses
from deploying virtual desktops? How do next-generation virtual desktops
provide companies an easier-to-deploy, easier-to-manage and more affordable
virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
