Hello Allison, I would certainly recommend looking further into Collective Access (CA) (http://www.collectiveaccess.org/) It’s a project that has been around for years, but still seems to be going strong. I’ve met some of the people behind the project. Very open and friendly and knowledgeable. What was nice was that they also had archivists and historians on staff, so they could approach a project from the technical and the business side. The software itself is very flexible and can be customised heavily. Which is an advantage and a disadvantage at the same time. Depending on who you are, what your technical skills are and how much you're willing to invest.
I believe Omeka (http://omeka.org/) is somewhat similar in some aspects, although it is supposed to be less flexible and less customisable. But much simpeler to get up and running. Finally there's also Collection Space (http://www.collectionspace.org/)<http://www.collectionspace.org/>. I assume that one is a bit closer to Collective Access, but maybe that's just because of the names. I do think Collective Access is the most flexible of them all and based on my limited experience it has the bigger user base. Cheers, Koen Van: [email protected] [mailto:[email protected]] Namens Allison Lee Verzonden: maandag 14 november 2016 16:34 Aan: Arches Project <[email protected]> Onderwerp: Re: [Arches] How to integrate Built Heritage, Immoveable Collections, and Moveable Collections Hello David, Thank you for the detailed response about bringing these documentation objectives together into one place. We have reviewed a bit of Collective Access, and it does seem to be a good option for storing our collection data and linking it to the main Arches site. At the moment, developing new modules may be too demanding for our limited resources but we will revisit this when v4 is released. If anyone has other suggestions for moveable collections, or any advice regarding Collective Access, please do let us know. We don't have experience with Collective Access, but it does appear very capable for extensive component collections such as ours. Best, Allison -- -- To post, send email to [email protected]<mailto:[email protected]>. To unsubscribe, send email to [email protected]<mailto:[email protected]>. For more information, visit https://groups.google.com/d/forum/archesproject?hl=en --- You received this message because you are subscribed to the Google Groups "Arches Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:[email protected]>. For more options, visit https://groups.google.com/d/optout. -- -- To post, send email to [email protected]. To unsubscribe, send email to [email protected]. For more information, visit https://groups.google.com/d/forum/archesproject?hl=en --- You received this message because you are subscribed to the Google Groups "Arches Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
