PubMan Sword
This page briefly describes the SWORD Server implementation in the PubMan solution. General Information about SWORD can be found here.
Implementation[edit]
For start the SWORD functionality is directly implemented in PubMan by exploiting and extending the sword api provided by JISC. In future we could have a seperate SWORD service for all eSciDoc solutions. PubMan implements 3 classes for the SWORD service:
- PubManSwordServer - Processing of requests
- PubManServiceDocumentServlet - Accepting requests for the Service Document (dependent on user credentials)
- PubManDepositServlet - Accepting requests for the deposits (dependent on user credentials)
Deposit[edit]
- The result of a deposit depends on the workflow of the collection an item is deposited to. Check the deposit action mapping.
Interface[edit]
The PubMan SWORD interface is deployed within the PubMan ear, therefore one can access the above described servlets by the PubMan baseURL + the servlet path.
(Example with PubMan base url http://pubman.mpdl.mpg.de, note that sword functionality is not yet deployed on live server)
Service Document[edit]
http://pubman.mpdl.mpg.de/pubman/faces/sword/servicedocument
Request:
Response:
Deposit Service[edit]
http://pubman.mpdl.mpg.de/pubman/faces/sword/deposit?collection=1234
Request:
Response:
Action Mapping[edit]
SWORD Action | PubMan Action | Comment |
---|---|---|
Deposit | Submit - Release | {Save}, {Save, Submit} or {Save, Submit,Release}, depending on the collection workflow and collection policies. |
Edit | Release | same as above |
Delete | Withdraw | Provide also delete for 'not submitted' items?--Friederike 08:51, 11 March 2009 (UTC)
|