This problem was caused by the Sword configuration on the DSpace server.
Or, more precisely, the complete lack of configuration of the Sword
module. We moved the server from another host last summer, and that must
be when the config got overwritten with the defaults. Apparently, no one
had t
Further information:
We seem to have got past "unauthorized credentials."
Now Vireo says, "Unable to communicate with deposit location:
org.purl.sword.client.SWORDClientException: Received error from service
document request: Code: 400, Message: 'Bad Request'
Using curl to browse to the Sword
Further information:
We seem to have got past "unauthorized credentials."
Now Vireo says, "Unable to communicate with deposit location:
org.purl.sword.client.SWORDClientException: Received error from service
document request: Code: 400, Message: 'Bad Request'
Using curl to browse to the Sword
