Andrea-
Thank you so much for this tip! Uncommenting and standardizing the
servicedocument.url property, plus one other minor change, fixed the
problem.
Keep up the good work!
-GG
On Wednesday, August 22, 2018 at 5:41:26 PM UTC-4, Andrea Schweer wrote:
>
> And further to that (having
And further to that (having tripped over this myself about five minutes
ago) - the url property in that file doesn't carry over to the
collection.url and servicedocument.url properties, so if you use a non
standard "url" value then (as stated in the comments of the file) you'll
have to adjust
Hi,
check what you have configured as the service document URL - probably in
[dspace]/config/modules/swordv2-server.cfg. It's the first property in that
file "url". The default is {dspace.url}/swordv2 and the base URL you use in
your sword deposit must match that exactly.
cheers,
Andrea
On Thu,
We're attempting to enable the SWORDv2 endpoint in our DSpace instance for
use in a DSpace-Symplectic Elements Repository Tools 2 integration. The
service document gives this error: "Unable to recognise URL as a valid
service document:..."
Does anyone have any insight into what could be
