SWORDv2 Server

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).

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).

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).

accept-packaging.collection

Example Value:

Informational Note:

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

Package format information

• METSDSpaceSIP: zipfile containing mets.xml file describing the resources packed together with it in the root of the zipfile.
• Binary: Binary resource that should be taken in as-is, not unpacked
• SimpleZip: Zip file that should be unpacked and each file in the zip should be ingested separately. No metadata provided/ingested.

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

Package format information

• METSDSpaceSIP: zipfile containing mets.xml file describing the resources packed together with it in the root of the zipfile.
• Binary: Binary resource that should be taken in as-is, not unpacked
• SimpleZip: Zip file that should be unpacked and each file in the zip should be ingested separately. No metadata provided/ingested.

accepts

Example Value:

Informational Note:

A comma-separated list of MIME types that SWORD will accept.  To accept all mimetypes, the value can be set to "*/*"

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.

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. 

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. 

bundle.name

Example Value:

Informational Note:

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

bundle.deleted

bundle.deleted = DELETED

Informational Note:

The bundle name that SWORD should use to store deleted bitstreams if versions.keep is set to true. This will be used in the case that individual files are updated or removed via SWORD. If the entire Media Resource (files in the ORIGINAL bundle) is removed this will be backed up in its entirety in a bundle of its own

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.

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. 

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. 

on-behalf-of.update.mediators

on-behalf-of.update.mediators = admin@mydspace.edu, mediator@mydspace.edu

Which user accounts are allowed to do updates on items which already exist in DSpace, on-behalf-of other users?

If this is left blank, or omitted, then all accounts can mediate updates to items, which could be a security risk, as there is no implicit checking that the authenticated user is a "legitimate" mediator

verbose-description.receipt.enable

verbose-description.receipt.enable = false

verbose-description.error.enable

verbose-description.error.enable = true

error.alternate.url

error.alternate.url = http://mydspace.edu/xmlui/contact

The error document can contain an alternate url, which the client can use to follow up any issues. For example, this could point to the Contact-Us page on the XMLUI

error.alternate.content-type

error.alternate.content-type = text/html

The error.alternate.url may have an associated content type, such as text/html if it points to a web page. This is used to indicate to the client what content type it can expect if it follows that url.

generator.url

Example Value:

Informational Note:

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

generator.version

Example Value:

Informational Note:

The version of the SWORD interface. 

auth-type

Example Value:

Informational Note:

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

upload.tempdir

Example Value:

Informational Note:

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

updated.field

Example Value:

Informational Note:

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

slug.field

Example Value:

Informational Note:

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

author.field

Example Value:

Informational Note:

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

title.field

Example Value:

Informational Note:

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

disseminate-packaging

Example Value:

Informational Note:

Supported packaging formats for the dissemination of packages. 

statement.bundles

statement.bundles = ORIGINAL, SWORD, LICENSE

Which bundles should the Statement include in its list of aggregated resources? The Statement will automatically mark any bitstreams which are in the bundle identified by the ${bundle.name} property, provided that bundle is also listed here (i.e. if you want Original Deposits to be listed in the Statement then you should add the SWORD bundle to this list)

plugin.single.org.dspace.sword2.WorkflowManager

Example Value:

Informational Note:

Which workflow manager to use.

workflowmanagerdefault.always-update-metadata

workflowmanagerdefault.always-update-metadata = true

Should the WorkflowManagerDefault plugin allow updates to the item's metadata to take place on items which are in states other than the workspace (e.g. in the workflow, archive, or withdrawn) ?

workflowmanagerdefault.file-replace.enable

workflowmanagerdefault.file-replace.enable = false

Should the server allow PUT to individual files?

If this is enabled, then DSpace may be used with the DepositMO SWORD extensions, BUT the caveat is that DSpace does not formally support Bitstream replace, so this is equivalent to a DELETE and then a POST, which violates the RESTfulness of the server. The resulting file DOES NOT have the same identifier as the file it was replacing. As such it is STRONGLY RECOMMENDED to leave this option turned off unless working explicitly with DepositMO enabled client environments

mets-ingester.package-ingester

Example Value:

Informational Note:

Which package ingester to use for METS packages. 

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.

simpledc.*

Example Value:

Informational Note:

Configuration of metadata field mapping used by the SimpleDCEntryIngester, SimpleDCEntryDisseminator and FeedContentDisseminator

atom.*

atom.author = dc.contributor.author

metadata.replaceable

metadata.replaceable = dc.description.abstract, dc.rights, dc.title.alternative, dc.identifier.citation

Used by SimpleDCEntryIngester: Which metadata fields can be replaced during a PUT to the Item of an Atom Entry document? Fields listed here are the ones which will be removed when a new PUT comes through (irrespective of whether there is a new incoming value to replace them)

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.

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?

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.

state.*

Example Value:

Informational Note:

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

workspace.url-template

workspace.url-template = http://mydspace.edu/xmlui/submit?workspaceID=#wsid#

URL template for links to items in the workspace (items in the archive will use the handle). The #wsid# url parameter will be replaced with the workspace id of the item. The example above shows how to construct this URL for XMLUI.