Unsupported Release

This documentation relates to DSpace 1.8.x, an old, unsupported version. Looking for another version? See all documentation.

As of January 2015, DSpace 1.8.x is no longer supported. We recommend upgrading to a more recent version of DSpace. See DSpace Software Support Policy.

Skip to end of metadata
Go to start of metadata

SWORD (Simple Web-service Offering Repository Deposit) is a protocol that allows the remote deposit of items into repositories. DSpace implements the SWORD protocol via the 'sword' web application. The specification and further information can be found at http://swordapp.org/.

SWORD is based on the Atom Publish Protocol and allows service documents to be requested which describe the structure of the repository, and packages to be deposited.

Enabling SWORD v2 Server

To enable DSpace's SWORD v2 server, just make sure the [dspace]/webapps/swordv2/ web application is available from your Servlet Container (usually Tomcat).

Configuring SWORD v2 Server

Configuration File:

[dspace]/config/modules/swordv2-server.cfg

Property:

url

Example Value:

Informational Note:

The base url of the SWORD 2.0 system. This defaults to ${dspace.baseUrl}/swordv2 (where dspace.baseUrl is defined in your dspace.cfg file).

Property:

collection.url

Example Value:

Informational Note:

The base URL of the SWORD collection. This is the URL from which DSpace will construct the deposit location URLs for collections. This defaults to ${dspace.baseUrl}/swordv2/collection (where dspace.baseUrl is defined in your dspace.cfg file).

Property:

servicedocument.url

Example Value:

Informational Note:

The service document URL of the SWORD collection. The base URL of the SWORD service document. This is the URL from which DSpace will construct the service document location urls for the site, and for individual collections. This defaults to ${dspace.baseUrl}/swordv2/servicedocument (where dspace.baseUrl is defined in your dspace.cfg file).

Property:

accept-packaging.collection

Example Value:

Informational Note:

The accept packaging properties, along with their associated quality values where appropriate.

Property:

accept-packaging.item

Example Value:

Informational Note:

The accept packaging properties for items.   It is possible to configure this for specific collections by adding the handle of the collection to the setting, for example accept-packaging.collection.[handle].METSDSpaceSIP = http://purl.org/net/sword-types/METSDSpaceSIP

Property:

accepts

Example Value:

Informational Note:

A comma-separated list of MIME types that SWORD will accept. 

Property:

expose-communities

Example Value:

Informational Note:

Whether or not the server should expose a list of all the communities to a service document request.   As deposits can only be made into a collection, it is recommended to leave this set to false.

Property:

max-upload-size

Example Value:

Informational Note:

The maximum upload size of a package through the SWORD interface (measured in bytes).  This will be the combined size of all the files, metadata, and manifest file in a package - this is different to the maximum size of a single bitstream.

If this is set to 0, no maximum file size will be enforced. 

Property:

keep-original-package

Example Value:

Informational Note:

Should DSpace store a copy of the orignal SWORD deposit package?

This will cause the deposit process to be slightly slower and for more disk to be used, however original files will be preserved.  It is recommended to leave this option enabled. 

Property:

bundle-name

Example Value:

Informational Note:

The bundle name that SWORD should store incoming packages within if keep-original-package is set to true. 

Property:

keep-package-on-fail

Example Value:

Informational Note:

In the event of package ingest failure, provide an option to store the package on the file system.  The default is false.  The location can be set using the failed-package-dir setting.

Property:

failed-package-dir

Example Value:

Informational Note:

If keep-package-on-fail is set to true, this is the location where the package would be stored. 

Property:

on-behalf-of.enable

Example Value:

Informational Note:

Should DSpace accept mediated deposits?  See the SWORD specification for a detailed explanation of deposit On-Behalf-Of another user. 

Property:

generator.url

Example Value:

Informational Note:

The URL which identifies DSpace as the software that is providing the SWORD interface. 

Property:

generator.version

Example Value:

Informational Note:

The version of the SWORD interface. 

Property:

auth-type

Example Value:

Informational Note:

Which form of authentication to use.  Normally this is set to Basic in order to use HTTP Basic. 

Property:

upload.tempdir

Example Value:

Informational Note:

The location where uploaded files and packages are stored while being processed.

Property:

updated.field

Example Value:

Informational Note:

The metadata field in which to store the updated date for items deposited via SWORD. 

Property:

slug.field

Example Value:

Informational Note:

The metadata field in which to store the value of the slug header if it is supplied. 

Property:

author.field

Example Value:

Informational Note:

The metadata field in which to store the value of the atom entry author if it supplied.

Property:

title.field

Example Value:

Informational Note:

The metadata field in which to store the value of the atom entry title if it supplied.

Property:

disseminate-packaging

Example Value:

Informational Note:

Supported packaging formats for the dissemination of packages. 

Property:

plugin.single.org.dspace.sword2.WorkflowManager

Example Value:

Informational Note:

Which workflow manager to use.

Property:

mets-ingester.package-ingester

Example Value:

Informational Note:

Which package ingester to use for METS packages. 

Property:

restore-mode.enable

Example Value:

Informational Note:

Should the SWORD server enable restore-mode when ingesting new packages.  If this is enabled the item will be treated as a previously deleted item from the repository.  If the item has previously been assigned a handle then that same handle will be restored to activity.

Property:

simpledc.*

Example Value:

Informational Note:

Configuration of metadata field mapping used by the SimpleDCEntryIngester. 

Property:

multipart.entry-first

Example Value:

Informational Note:

The order of precedence for importing multipart content.  If this is set to true then metadata in the package will override metadata in the atom entry, otherwise the metadata in the atom entry will override that from the package.

Property:

workflow.notify

Example Value:

Informational Note:

If the workflow gets started (the collection being deposited into has a workflow configured), should a notification get sent?

Property:

versions.keep

Example Value:

Informational Note:

When content is replaced, should the old version be kept?  This creates a copy of the ORIGINAL bundle with the name V_YYYY-MM-DD.X where YYYY-MM-DD is the date the copy was created, and X is an integer from 0 upwards.

Property:

state.*

Example Value:

Informational Note:

Pairs of states (URI and description) than items can be in.  Typical states are workspace, workflow, archive, and withdrawn.

Other configuration options exist that define the mapping between mime types, ingesters, and disseminators.  A typical configuration looks like this:

  • No labels