Output – SWORD – Case Studies

Title: SWORD case studies

Date Released: November 2007 to July 2008

URI for Output: http://www.ukoln.ac.uk/repositories/digirep/index/SWORD_case_studies

Summary of contents: Four case studies were commissioned to demonstrate the requirement for and use of the SWORD profile for deposit.

Additonal information:

Case study 1 : arXiv

Abstract: “The arXiv e-print archive (http://arxiv.org/) has for many years used an ad-hoc automated upload interface to accept submissions from proxies (overlay and other journals also posting open-access copies of articles to arXiv) and from our remote submission site in France (HAL, http://hal.archives-ouvertes.fr/). In collaboration with Microsoft, we are working to produce a new interface to allow automated upload of conference articles from the popular Conference Management Toolkit site (CMT, http://cmt.research.microsoft.com/cmt/). We are implementing the SWORD profile of Atom at arXiv to facilitate these uploads.”

Case study 2 : SOURCE

Information at http://flickr.com/photos/dff1978/1533681354/

Case study 3 : SPECTRa

The SPECTRa web application allows for the quick and easy deposition of chemistry data in a range of formats. The original implementation works against the DSpace Lightweight Network interface, since the SWORD did not exist at the time SPECTRa was developed. This is a limitation, since the installed base of the DSpace LNI is extremely small. To ameliorate this limitation, the function of deposit is performed through a plugin mechanism, whereby plugins can be developed for other deposit protocols. A SWORD plugin for SPECTRa will help to achieve two main goals: –

1) Increase the utility of SPECTRa to the mainstream of DSpace installations

2) Allow use of SPECTRa with a range of repository softwares.

Case study 4 : White Rose Research Online

Outlines automatic deposit in a funder-mandated repository from a local repository. Case study outlines:

1. Implementing the EPrints SWORD package on the White Rose server.
2. Proof of concept of export/import between two development repositories.
3. Workflow modelling.

%d bloggers like this: