The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
Table of Contents |
|---|
Introduction
Institutional Repositories are increasingly used as archives for publications, theses and other scholarly or educational output. With this, the archival services offered by repository applications maintained by the university libraries is used in an increasing number of business processes, whether this being the deposit of peer reviewed stage 2 material, the deposit of bachelor theses at the and of the academic year or the need to archive research data.
With this, library staff and repository applications need to accommodate more and more use cases, each requiring its specific needs, e.g. the deposit of a thesis resulting from a collaborative effort for publication in the HBO Kennisbank or the self-archival of research data at an external data repository.
In order to create a scalable solution, the need arises to separate the archival service from services that support the deposit workflows and to loosely couple institutional repositories with specialised deposit application which then exchange information through standardised web service interfaces.
This application profile describes a protocol to allow the deposit of publications, theses and research data to institutional repositories.
Standards reference for this application profile
SWORD: Simple Web service Offering Repository Deposit
The first version of Simple Web service Offering Repository Deposit was developed in a project funded by JISC as an effort to 'lowering the barriers to deposit, principally for depositing content (any content!) into repositories, but potentially for depositing into any system which wants to receive content from remote sources'. It is in itself an application profile of the Atom Publishing Protocol (APP) described in RFC 5023 used for the publishing and editing of web resources using HTTP and XML 1.0. Although related, the APP is not to be confused with the Atom Syndication Format described RFC 4287 commonly used for web feeds used to check for updates on a website.
The current version of SWORD at the time of writing is version 1.3, although a new 2.0 version is in the making. This version however still has a working beta status and has not been finalised.
This application profile is based on SWORD v1.3.
Use of SWORD features
This section will describe the use of the SWORD profile in the context of the SURFshare programme. The contents are organised according and supplementary to the document SWORD Atom Pub Profile version 1.3 part A. If a SWORD profile section or feature is omitted, implementations MUST behave as defined in SWORD profile.
1. Package Support
1.1. Package support in Service Description
1.2 Package description in entry documents
2 Mediated Deposit
2.1 Mediation in Service Description
4 Auto Discovery
6 Nested Service Description
Use of APP features
The contents are organised according and supplementary to the document SWORD Atom Pub Profile version 1.3 part B, which is turn is organised according to the sections of RFC 5023 describing APP. If a SWORD profile section or feature is omitted, implementations MUST behave as defined in SWORD profile.