Hi all,
Before watching the webinar about the connector, I read up on it and spoke with LibraryHost who hosts all our archive software. They did not see an issue and so the connector and hierarchy modules were added to our Omeka site. Long story short- I was unable to get the connector to work and alerted our site host. We were able to confirm it was the API permissions that are causing the issues. This is the final reply from our host before I put them on hold. I did not want to waste the limited IT hours we have.
"I did some more digging and realized I was wrong – the API is completely permissions based. I thought that a published record would be accessible through the API as it is through the public interface, but it is not – by design.
The ArchivesSpace API requires an account with at least Repository Viewer permissions to view a record, whether it is published or not.
What I don’t yet understand is how to get the Omeka ArchivesSpace connector plugin to “log-in” to ArchivesSpace as a user would. There are no fields that I can see in the ArchivesSpace Connector module for adding a user account, and the module’s page on omeka.org and Github has no documentation on how to do this (or really, any documentation at all).
The ArchivesSpace connector module is rather new. I think the next step is to reach out to the developer for advice on how to get the Omeka module do authentication. Then, we can create a read only user in ArchivesSpace, and have the connector module use that so it has permission to access the record."
Can anyone help me with this? Is it completely impossible for the connector to work with a hosted site? I am not unfamiliar with the language of the API, but I cannot even access more than a sort of welcome text to the API. We did confirm I have the correct addresses since we have never really needed to access the API.
Sheralyn