Here's the follow-up to my previous question.
I have a crude (but useable) XSLT crosswalk ("nlm") in DSpace. It transforms
DIM metadata to fit the NLM Journal Publishing profile. I can test the output
successfully with OAI-PMH.
As it turns out, I don't really need to export bitstreams. I just need the
metadata for a set of items within a collection that would be specified by the
end-user/Community Owner. So, if I want just the crosswalk output for that set
of items and I don't want the OAI protocol wrapper or the bitstreams, then do I
still need a custom packager for that as in Mark's IMSCP example? I expect the
answer is yes.
I think what 'm really wanting is to be able to call the crosswalk as a method
on the collection, in a RESTful way, and return the output as a single XML
document for the collection containing each of the transformed items.
Conjured example: handle/2271/883/nlm.xml or nlm/handle/2271/883
Jason
Jason Stirnaman
Biomedical Librarian, Digital Projects
A.R. Dykes Library, University of Kansas Medical Center
[email protected]
913-588-7319
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
