Difference between revisions of "PubMan Sword"
Jump to navigation
Jump to search
Kleinfercher (talk | contribs) m (started structure) |
Kleinfercher (talk | contribs) |
||
| Line 2: | Line 2: | ||
==Implementation== | ==Implementation== | ||
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) | |||
==Interface== | ==Interface== | ||
Revision as of 11:37, 1 April 2009
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)