Page History
...
Table of Contents | ||||||
---|---|---|---|---|---|---|
|
Enabling SWORD v2 Server
To enable DSpace's SWORD v2 server, just make sure the {{\ Wiki Markup [dspace
\]/webapps/swordv2/
}} web application is available from your Servlet Container (usually Tomcat).
Configuring SWORD v2 Server
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="c45caf3a-1167-4711-918f-17707314e3c0"><ac:plain-text-body><![CDATA[ | Configuration File: |
| |
---|---|---|---|
Property: | | ||
Example Value: |
| ||
Informational Note: | The base url of the SWORD 2.0 system. This defaults to | ||
Property: | | ||
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 | ||
Property: | | ||
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 | ||
Property: | | ||
Example Value: |
| ||
Informational Note: | The accept packaging properties, along with their associated quality values where appropriate. | ||
Property: | | ||
Example Value: |
| ||
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="5fbfdcd0-62fa-46cd-a9b5-8f3d3d58f026"><ac:plain-text-body><![CDATA[ | 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 | |
Property: | | ||
Example Value: |
| ||
Informational Note: | A comma-separated list of MIME types that SWORD will accept. | ||
Property: | | ||
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: | | ||
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. | ||
Property: | | ||
Example Value: |
| ||
Informational Note: | Should DSpace store a copy of the orignal SWORD deposit package? | ||
Property: | | ||
Example Value: |
| ||
Informational Note: | The bundle name that SWORD should store incoming packages within if | ||
Property: | | ||
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 | ||
Property: | | ||
Example Value: |
| ||
Informational Note: | If | ||
Property: | | ||
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: | | ||
Example Value: |
| ||
Informational Note: | The URL which identifies DSpace as the software that is providing the SWORD interface. | ||
Property: | | ||
Example Value: |
| ||
Informational Note: | The version of the SWORD interface. | ||
Property: | | ||
Example Value: |
| ||
Informational Note: | Which form of authentication to use. Normally this is set to | ||
Property: | | ||
Example Value: |
| ||
Informational Note: | The location where uploaded files and packages are stored while being processed. | ||
Property: | | ||
Example Value: |
| ||
Informational Note: | The metadata field in which to store the updated date for items deposited via SWORD. | ||
Property: | | ||
Example Value: |
| ||
Informational Note: | The metadata field in which to store the value of the slug header if it is supplied. | ||
Property: | | ||
Example Value: |
| ||
Informational Note: | The metadata field in which to store the value of the atom entry author if it supplied. | ||
Property: | | ||
Example Value: |
| ||
Informational Note: | The metadata field in which to store the value of the atom entry title if it supplied. | ||
Property: | | ||
Example Value: |
| ||
Informational Note: | Supported packaging formats for the dissemination of packages. | ||
Property: | | ||
Example Value: |
| ||
Informational Note: | Which workflow manager to use. | ||
Property: | | ||
Example Value: |
| ||
Informational Note: | Which package ingester to use for METS packages. | ||
Property: | | ||
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: | | ||
Example Value: |
| ||
Informational Note: | Configuration of metadata field mapping used by the SimpleDCEntryIngester. | ||
Property: | | ||
Example Value: |
| ||
Informational Note: | The order of precedence for importing multipart content. If this is set to | ||
Property: | | ||
Example Value: |
| ||
Informational Note: | If the workflow gets started (the collection being deposited into has a workflow configured), should a notification get sent? | ||
Property: | | ||
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: | | ||
Example Value: |
| ||
Informational Note: | Pairs of states (URI and description) than items can be in. Typical states are |
...