Multi-repository set ups in AS. There's a lot of sharing between repositories (eg agent records) which is really helpful, but some seems less so (eg location records, container profile records, location profile records). I'm worried about scaling up here- will it be feasible to use AS for location management by 30 separate repositories if each repository can see each other's location records?
Eve Neiger recommends developing a group of stakeholders at your repository to meet regularly and agree on how to input information into ArchivesSpace for consistency.
There was also a recommendation to try and identify aa group of ArchivesSpace users who are dealing with issues related to managing multiple repositories within in ArchivesSpace. Maybe a call on the users group?
Natalie Adams, Cambridge
User accounts and changing passwords: we're setting up around 80-100 new users on AS and are finding it challenging because the users can't change their passwords.
Please watch JIRAs that already exist and offer comment as appropriate
Natalie Adams, Cambridge
How do people work with vendors to customize AS? Any tips of those who have gone through the process be it vendor selection, requirement prep, relationship management etc would be of interest to me.
Eve Neiger (Yale) spoke about a specific vendor relationship and recommends thinking through what you hope to accomplish with the vendor using the specific example of developing use cases or user stories. She also recommended staying in frequent communication and getting quotes and estimates as you work. It can become complicated when dealing with vendors in different timezones. Yale has one point of contact for vendor communication. The ArchivesSpace stakeholders all meet and discuss before changes are made but everything is funneled through one point of contact.
Mary Haberle, Mike Kelley Foundation for the Arts
What do you wish you had known before importing legacy data? What setup issues MUST I do?
Do as much advanced prep/clean up as possible
Use a test instance to play in and test everything before going into production.
“One important thing we’ve realized is that if an accession record or a digital object is in one repository, and a resource record is in a a different repository, the links are lost.”
“data clean up can be challenging, so try to get it right the “first” time
“We didn't realize at first that Accessions records weren't required. We can't use AS for accessiion records, so not having to create them anyway was a great time saver!”