Hello!
I’m trying to figure out an issue I have been having with the dSpace Connector module in Omeka S. I’ve been struggling to import collections from my institution’s repository on dSpace 7. When I set server/api as the endpoint it just works and works and nothing happens, it doesn’t even log that a job has been initiated or attempted. When I set the endpoint to rest I get the option to import the entire collection - this is not what I want to do but I tried it anyway to see if anything would be imported and just set the limit to 10 or 20 items. Nothing gets imported but it logs a job and just says 0 items have been imported. Disappointing because I’ve been able to use the module successfully with another dSpace repository on version 5.(?) and it works seamlessly!
Does this seem like a problem with the dSpace repository? or a problem with how I am entering it in Omeka?
Very new to this so any input helps! Thanks!
Hello, would you mind sharing the exact api url you are using so I can test?
When I use https://dspace.sunyconnect.suny.edu/ as the DSpace Site URL value and server/api as the Endpoint value, I am consistently getting results. It does take a while (about 2-3 minutes) since there are over 100 collections to fetch from this DSpace instance.
Perhaps you’re leaving the full https://dspace.sunyconnect.suny.edu/server/api as the DSpace Site URL value? When I do this and submit, it also hangs endlessly.
The server/api information needs to be stripped form the URL value: DSpace Connector - Omeka S User Manual
Thank so much for your help. I got it to work today after getting some help from the repositories manager. I’m not really sure what the problem was, I had removed the server/api from the URL and was still getting nothing. The only thing different this time was setting the limit to 50 which seemed to be the magic number? Strange. I’m very happy it is working now since this will save me a lot time. I really appreciate you testing it out for me, thanks!
Yeah, often times fiddling with the # of returned results can help depending on the variables such as metadata/records/server response time etc. Servers can often timeout or overload silently so putting in smaller return values can find magic number to return results without choking on too much traffic at once.
Glad to be of help!