SWORD Simple Web-service Offering Repository Deposit Julie Allinson

SWORD Simple Web-service Offering Repository Deposit Julie Allinson 25 th March 2009, British Library

SWORD Quick Introduction n Vision: “lowering barriers to deposit” n Simple Web service Offering Repository Deposit n Aims to provide a standard mechanism for ‘doing deposit’ into repositories n JISC funded project started 2007, continuation funding for SWORD 2 from June 2008

What is it? n A lightweight protocol for deposit n A proﬁle of the Atom Publishing Protocol n Implementations of SWORD in Intra. Library, Fedora, DSpace and Eprints repositories n SWORD clients – web-based, desktop, MS Office plugin, Facebook, widgets

Motivations – why? n no standard interface for tagging, packaging or authoring tools to upload objects into a repository n no standard interface for transferring digital objects between repositories n no way to deposit into more than one repository with one ‘click’ n no way of initiating a deposit workflow from outside a repository system

The Project Partners n SWORD partners: n UKOLN, University of Bath and University of York (Project Management) – Adrian Stevenson & Julie Allinson n University of Aberystwyth (DSpace, Fedora, & clients) – Stuart Lewis, Neil Taylor, Glen Robson, Richard Jones n University of Southampton (EPrints) – Les Carr, Seb Francois n Intrallect (Intra. Library) – Sarah Currier, Andrew Robson, Martin Morrey n Jim Downing – standards development

Use Cases n Deposit from a Desktop/Online tool n Multiple deposit - e. g. deposit to institutional and (mandated) funders’ repository with one action n Machine deposit - e. g. automated deposit from a laboratory machine n Migration/transfer - e. g. to a preservation service n Mediated deposit - e. g. deposit by a nominated representative, to additional repositories

Scenario 1 n. Librarian A deposits via an easy-deposit desktop application into the institutional repository's mediated deposit queue n. Deposit n. Author L completes the deposit through the repository interface lightweight deposit web service can facilitate this transfer of object(s) nid n. A n. Librarian nid L invokes deposit of a surrogate into arxiv. org

n. A depositor is required to submit to a Research Council repository, but they also wish to deposit into their institutional repository and a relevant subject repository n. The depositor can choose one or more repositories to deposit into n. A lightweight deposit web service can facilitate this transfer of object(s) n. Deposit Scenario 2

SWORD Atom. Pub Profile

Standards n Web. DAV (http: //www. webdav. org/) n JSR 170 (http: //www. jcp. org/en/jsr/detail? id=170) n JSR 283 (http: //www. jcp. org/en/jsr/detail? id=283) n SRW Update (http: //www. loc. gov/standards/sru/) n Flickr Deposit API (http: //www. flickr. com/services/api/) n Fedora Deposit API (http: //www. fedora. info/definitions/1/0/api/) n OKI OSID (http: //www. okiproject. org/) n ECL (http: //ecl. iat. sfu. ca/) n ATOM Publishing Protocol (http: //www. ietf. org/htmlcharters/atompubcharter. html)

Atom. Pub “the Atom Publishing Protocol is an application-level protocol for publishing and editing Web resources” n benefits n n it already exists and has growing support n it is well-used in popular applications n it has an extension mechanism n n supports many of our parameters and requirements, in particular file deposit good fit with the Web architecture drawbacks / risks n too much of a retrofit? n it is designed for a single package/file OR an atom document – this means that we need to package up metadata and files

SWORD Atom. Pub Profile n SWORD profile builds on Atom. Pub n Provides extensions, constraint relaxations and enforcements when: n n Mediated deposit required n n Clients post compound resources (zip, tar) Workflows involved SWORD compliance does not preclude Atom. Pub compliance

SWORD APP Package Support n Atom. Pub uses MIME to describe resources n n SWORD supports accepting MIME types, but Inadequate for compound types e. g. n n n Zip, tar METS, SCORM, MPEG 21, DIDL packages SWORD extends Atom. Pub: n sword: accept. Packaging element n Value taken from SWORD package types n Developing area

SWORD APP Mediated Deposit n SWORD deposit client user may not be owner of resource n SWORD allows clients to set a HTTP header: n X-On-Behalf-Of n Assumes trust between owner and mediating user n Future development could explore OAuth for creating trust relationships

More Features n No-Op (Dry Run) n Verbose Output n Client and Server Identity n Auto-Discovery n Error Documents n Nested Service Description

SWORD APP Error Documents n SWORD adds new class of document to Atom. Pub to allow better error description n Error. Content n Error. Checksum. Mismatch n Error. Bad. Request n Target. Owner. Unknown n Mediation. Not. Allowed

SWORD Profile of Atom. Pub n Protocol Operations n n Listing Collections n Creating a Resource n n Retrieving Service Document Editing/Deleting resource – not part of SWORD, optional Service Documents n n new elements: version, verbose, no. Op, max. Upload. Size, collection. Policy, mediation, treatment, accept. Packaging, service increasing requirement for persistent Atom Entry Documents

How it Works n Issue HTTP requests (GET, POST) from client to SWORD interface n GET Service Document (explain/discover) n POST ATOM document or file/package to collection URI n HTTP response and ATOM document is returned n HTTP basic authentication should be supported

SWORD In Use

Implementations n Repository implementations n n EPrints n Intra. Library n n DSpace Fedora Client implementations n command-line, desktop and web clients n Facebook Client n Deposit from within MS Word & Powerpoint n Feedforward / FOREsite and others n Java, PHP and. NET libraries

SWORD in use n In addition to the case study implementations: n Feedforward has already implemented n ICE project is looking at SWORD n DSpace and EPrints installations already exist n Microsoft e. Chemistry work n OAI-ORE - FOREsite work n more are planned n NISO activity around deposit n Collaberation with Nature Publishing Group possible n York – funded project around SWORD

More Info and Contact n SWORD Website: n http: //www. swordapp. org n General queries: n n Adrian Stevenson a. stevenson@ukoln. ac. uk Technical queries: n sword sourceforge list sword-app-tech@lists. sourceforge. net

OAI-ORE Object Re-use and Exchange Julie Allinson 25 th March 2009, British Library

ORE background n n n n commenced October 2006 stands for ‘Object Reuse and Exchange’ falls in the remit of the Open Archives Initiative (creators of OAI-PMH) funded by the Mellon Foundation, with support from the National Science Foundation in the U. S. international focus and lots of interest a 2 year project, not the answer to all our problems ended September 2008

ORE Results n Primer – in heavy use for the presentation! n User Guides n Resource Map implementation in ATOM, RDF/XML, RDFa, HTTP n Resource Map Discovery n Specifications – Abstract Model and Vocabulary n Tools and additional resources

Key terminology for ORE n Aggregations n Web architecture – resource, URI, representation, link n Resource Maps n Linked Data / Semantic Web n RDF n ATOM n Serialization

ORE in one sentence “ORE is a serialization format for describing aggregations of Web resources” (according to me)

Relationship to OAI-PMH n n OAI-ORE is NOT a replacement for OAIPMH OAI-PMH will continue to exist as one approach to interoperability n n OAI-PMH metadata-centric OAI-ORE will complement with richer functionality, when this is desirable n OAI-ORE is resource centric

An example n The Fore. Site toolkit n “Libraries for constructing, parsing, manipulating and serializing OAI-ORE Resource Maps” n Demonstrator created Resource Maps of journals in JSTOR, delivered as ATOM documents via SWORD DSpace interface

That’s it.