I think therein lies my problem: we are not using subdomains. I kept looking
that part over and worrying that that was the issue. I’ll get on that. Thank
you for the reply.
Kyle Fortney
Computer Specialist
405-744-7924
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
[mailto:archi
If you're following the example you shouldn't add the port numbers to the
URL - staff.myarchive.org and research.myarchive.org (or whatever
subdomains you're using) should serve the frontend (staff UI) and public UI
respectively. SSL connections all happen over port 443, which is why you
have to u
I am working on installing our SSL for our ArchivesSpace server. Unfortunately
I cannot get the 8080 and 8081 redirects to work. I have followed the
information in Step 2 at
https://github.com/archivesspace/archivesspace/blob/master/README_HTTPS.md. Not
sure how Step 1 is related. Our SSL is in
I cannot claim credit for this because someone else mentioned it to me.
Might the compromise to have an on/off button in the agents section of a
Resource to designate whether sync between the two parts of the system should
happen? Perhaps even to the point of turning on initially to populate base
I second (third?) everybody's interest in such a feature. It would also reflect
growing consensus in the archives community that one should manage creator
metadata separate from collection metadata.
Looking at the specs below, I think more conversation would want to happen
around the ability to
