From my experience with Primo in a previous job, despite its many
flaws, it is unlikely to be the cause here.
There is an open issue with ArchivesSpace which may be relevant:
https://archivesspace.atlassian.net/browse/ANW-1301
Especially the comment I've just added.
I have no experience
We treated this as an ArchivesSpace bug. According tp openarchives.org,
"If a record is no longer available then it is said to be deleted."
ArchivesSpace only indicates that a record is deleted when it is
actually deleted from the database, not when it becomes suppressed
(contrary to what we
I would like to look at running ArchivesSpace within a Docker image. I see
at least a couple of pre-built containers available in DockerHub. Is the
ArchivesSpace version the preferred version or are others better? And is
there good documentation somewhere on how to run AS within a docker
Hey Tom
Here's a repo describing the setup we use:
https://github.com/dartmouth-dltg/aspace-docker
This is pre AS v3.2.0, so no external solr - we're still running AS v3.1.1 in
prooduction.
jds
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
Hi Tom,
This is our setup:
https://gitlab.msu.edu/msu-libraries/public/archivesspace-docker that uses
separate Docker containers for ArchivesSpace and Solr, running v3.1.1.
- Megan
_
Megan Schanz
Application Developer & Systems Administrator
Michigan
