WANTED: SWORD case studies

Sep 232010
 

We’re looking to improve the SWORD website and inspire new uses of SWORD by collecting and publishing a collection of SWORD case studies.  We’d love to hear from you if you’ve written a SWORD client, or made use of an existing client in a new way.  There is a lot of good work being undertaken that uses SWORD, and we want to make sure that everyone knows about it.

If you have a case study, please either email it to us (info@swordapp.org), or get in touch. If you’d prefer we could arrange to interview you instead.  We’ll publish the case studies on the SWORD website, and we’ll look into other options for disseminating them further.

The SWORD Course

Sep 212010
 

The complete slides and videos from the SWORD course are now online. To access the course materials use the ‘The SWORD Course‘ link in the menu bar at the top of the site.

Here is an overview of the materials available:

  1. An Introduction to SWORD: Gives an overview of SWORD, the rationale behind its creation, and details of the first three funded SWORD projects (Slides | Video)
  2. SWORD Use Cases: Provides an introduction to use cases, and examines some of the use cases that SWORD can be used for (Slides | Video)
  3. How SWORD Works: A high level overview of the SWORD protocol, lightly touching on a few technical details in order to explain how it works (Slides | Video)
  4. SWORD Clients: The reasons for needing SWORD clients are shown, followed by a tour of some of the current SWORD clients (Slides | Video)
  5. Create Your Own SWORD Client: An overview of the EasyDeposit SWORD client creation toolkit, including the chance to try it out (Slides | Video)

Seeking feedback for SWORD v2

Sep 202010
 

Between 2007 and 2010 the JISC funded three iterations of the original SWORD project. These projects between them managed to create a new standard for repository deposit interoperability, a worldwide community of active users and developers, and a deeper understanding of the deposit interoperability needs of our repositories. From the initial funded implementations for DSpace, EPrints, Fedora and Intralibrary have spawned an ecosystem of SWORD servers and clients, including implementations for tools such as Microsoft Word, Drupal, Facebook, Moodle and OJS. At the recent Open Repositories 2010 conference in Madrid, much of the presented work involving repository deposit was making use of SWORD. The project was also named ‘The Most Innovative Project’ at the 2009 JISC Repositories and Preservation conference.

The original SWORD projects dealt with creating new repository resources by package deposit -­ a simple case which was at the root of its success but is also its key limitation. This method of deposit could be summed up as ‘fire and forget’. SWORD supports the deposit of the content, but once it is deposited, the user of a SWORD client is unable to track the progress of the item through any workflows, make alterations or updates to the content, or to delete it.

This proposed next version of SWORD will push the standard towards supporting the full repository deposit lifecycle by specifying and implementing update, retrieve and delete extensions to the specification. This will enable the repository to be integrated into a broader range of systems in the scholarly environment, by supporting an increased range of behaviours and use cases.

The first step in developing the SWORD v2 standard has been the development of a white paper by the SWORD v2 Technical Lead Richard Jones. Richard has worked as a repository developer for several universities including The University of Edinburgh, The University of Bergen, and Imperial College London. He is currently the Head of Repository Systems at Symplectic Ltd.

The white paper can be found at http://sword2depositlifecycle.jiscpress.org/

Please read the white paper and provide comments. Comments can either be about the contents of the white paper itself, your experiences and thoughts of the SWORD v1 standard, or your ideas for SWORD v2. The feedback from the white paper will be used in the drafting of the v2 standard. Please contribute, all input welcome!