Hello everyone,
We are attempting to enable Swordv1 on our Dspace 5.5 test instance
<http://dspace2-test.creighton.edu:8080/xmlui/> as a precursor to enabling
it on our production server in order to facilitate ProQuest deposits, but
we keep encountering a 404 error when trying to access the service document
(http://dspace2-test.creighton.edu:8080/sword/servicedocument).
As best we can tell we have made the necessary updates to the
sword-server.cfg and dspace.cfg files and have added the sword webapp
folder from the dspace webapp folder (/opt/dspace/webapps/sword) to our
tomcat webapp folder (/opt/apache-tomcat-7.0.68/webapps/sword) based on the
dspace 5 swordv1-server documentation
<https://wiki.lyrasis.org/display/DSDOC5x/SWORDv1+Server>.
We have also tried adding the sword webapp folder to
/var/lib/tomcat/webapps/sword based on this similar previous question
<https://groups.google.com/g/dspace-community/c/HqfQYNWY4Qs/m/rSo2uFg_IAAJ>
in dspace-community.
I have included a copy of the sword-server.cfg file in case we have missed
a setting.
Any tips or recommendations would be appreciated.
Karl Wirth
Creighton University
--
All messages to this mailing list should adhere to the Code of Conduct:
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups
"DSpace Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/dspace-community/2c722b9f-c39a-415c-ba47-6e1e7e5beb4cn%40googlegroups.com.
#---------------------------------------------------------------#
#-------------SWORD V.1 SERVER CONFIGURATIONS-------------------#
#---------------------------------------------------------------#
# These configs are only used by the SWORD Server interface, #
# version 1.3 (used by DSpace to accept ingest packages via #
# SWORD protocol) #
#---------------------------------------------------------------#
# tell the SWORD METS implementation which package ingester to use
# to install deposited content. This should refer to one of the
# classes configured for:
#
# plugin.named.org.dspace.content.packager.PackageIngester
#
# The value of mets-ingester.package-ingester tells the
# system which named plugin for this interface should be used
# to ingest SWORD METS packages
#
# The default is METS
#
mets-ingester.package-ingester = METS
# The base URL of the SWORD deposit. This is the URL from
# which DSpace will construct the deposit location urls for
# collections.
#
# The default is {dspace.url}/sword/deposit
#
# In the event that you are not deploying DSpace as the ROOT
# application in the servlet container, this will generate
# incorrect URLs, and you should override the functionality
# by specifying in full as below:
#
# deposit.url = http://www.myu.ac.uk/sword/deposit
deposit.url = http://dspace2-test.creighton.edu:8080/sword/deposit
# 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
#
# The default is {dspace.url}/sword/servicedocument
#
# In the event that you are not deploying DSpace as the ROOT
# application in the servlet container, this will generate
# incorrect URLs, and you should override the functionality
# by specifying in full as below:
#
# servicedocument.url = http://www.myu.ac.uk/sword/servicedocument
servicedocument.url =
http://dspace2-test.creighton.edu:8080/sword/servicedocument
# The base URL of the SWORD media links. This is the URL
# which DSpace will use to construct the media link urls
# for items which are deposited via sword
#
# The default is {dspace.url}/sword/media-link
#
# In the event that you are not deploying DSpace as the ROOT
# application in the servlet container, this will generate
# incorrect URLs, and you should override the functionality
# by specifying in full as below:
#
# media-link.url = http://www.myu.ac.uk/sword/media-link
media-link.url = http://dspace2-test.creighton.edu:8080/sword/media-link
# The URL which identifies the sword software which provides
# the sword interface. This is the URL which DSpace will use
# to fill out the atom:generator element of its atom documents.
#
# The default is:
#
#http://www.dspace.org/ns/sword/1.3.1
#
# If you have modified your sword software, you should change
# this URI to identify your own version. If you are using the
# standard dspace-sword module you will not, in general, need
# to change this setting
#
generator.url = http://www.dspace.org/ns/sword/1.3.1
# The metadata field in which to store the updated date for
# items deposited via SWORD.
#
updated.field = dc.date.updated
# The metadata field in which to store the value of the slug
# header if it is supplied
#
slug.field = dc.identifier.slug
# The accept packaging properties, along with their associated
# quality values where appropriate.
#
# Global settings; these will be used on all DSpace collections
#
accept-packaging.METSDSpaceSIP.identifier =
http://purl.org/net/sword-types/METSDSpaceSIP
accept-packaging.METSDSpaceSIP.q = 1.0
# A comma separated list of MIME types that SWORD will accept
accepts = application/zip
# Collection Specific settings: these will be used on the collections
# with the given handles
#
#accept-packaging.[handle].METSDSpaceSIP.identifier =
http://purl.org/net/sword-types/METSDSpaceSIP
#accept-packaging.[handle].METSDSpaceSIP.q = 1.0
# Should the server offer up items in collections as sword deposit
# targets. This will be effected by placing a URI in the collection
# description which will list all the allowed items for the depositing
# user in that collection on request
#
# NOTE: this will require an implementation of deposit onto items, which
# will not be forthcoming for a short while
#
expose-items = false
# Should the server offer as the default the list of all Communities
# to a Service Document request. If false, the server will offer
# the list of all collections, which is the default and recommended
# behaviour at this stage.
#
# NOTE: a service document for Communities will not offer any viable
# deposit targets, and the client will need to request the list of
# Collections in the target before deposit can continue
#
expose-communities = false
# The maximum upload size of a package through the sword interface,
# in bytes
#
# This will be the combined size of all the files, the metadata and
# any manifest data. It is NOT the same as the maximum size set
# for an individual file upload through the user interface. If not
# set, or set to 0, the sword service will default to no limit.
#
max-upload-size = 0
# Should DSpace store a copy of the original sword deposit package?
#
# NOTE: this will cause the deposit process to run slightly slower,
# and will accelerate the rate at which the repository consumes disk
# space. BUT, it will also mean that the deposited packages are
# recoverable in their original form. It is strongly recommended,
# therefore, to leave this option turned on
#
keep-original-package = true
# The bundle name that SWORD should store incoming packages under if
# keep-original-package is set to true. The default is "SWORD"
# if not value is set
#
bundle.name = SWORD
# In the event of package ingest failure, provide an option to store
# the package on the file system. The default is false.
keep-package-on-fail=true
failed-package.dir=/opt/dspace/upload
# Should the server identify the sword version in deposit response?
#
# It is recommended to leave this enabled.
#
identify-version = true
# Should we support mediated deposit via sword? Enabled, this will
# allow users to deposit content packages on behalf of other users.
#
# See the SWORD specification for a detailed explanation of deposit
# On-Behalf-Of another user
#
on-behalf-of.enable = true
# 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 had
# previously been assigned a handle then that same handle will be
# restored to activity.
restore-mode.enable = true
# Configure the plugins to process incoming packages. The form of this
# configuration is as per the Plugin Manager's Named Plugin documentation:
#
# plugin.named.[interface] = [implementation] = [package format identifier] \
#
# Package ingesters should implement the SWORDIngester interface, and
# will be loaded when a package of the format specified above in:
#
# accept-packaging.[package format].identifier = [package format identifier]
#
# is received.
#
# In the event that this is a simple file deposit, with no package
# format, then the class named by "SimpleFileIngester" will be loaded
# and executed where appropriate. This case will only occur when a single
# file is being deposited into an existing DSpace Item
#
plugin.named.org.dspace.sword.SWORDIngester = \
org.dspace.sword.SWORDMETSIngester =
http://purl.org/net/sword-types/METSDSpaceSIP \
org.dspace.sword.SimpleFileIngester = SimpleFileIngester
