We’re in the first stages of a project to make Omeka S available for Australian humanities researchers running on our national research cloud platform, Nectar, and I’m trying to understand the best way to manage the use case of multiple projects from different research teams.
I’d assumed that a single Omeka S instance would make sense, but it looks like this might not get the separation between research projects I’d been imagining and which the IsolatedSites plugin seems to be designed for.
The alternative - which we’re going with for some of our legacy collections - is running a separate instance of Omeka S for each collection behind an Apache as a load-balancer. The problem with this is that spinning up new projects will require more work than just starting a new project in an Omeka S instance.
Is there a middle ground, where we use Omeka S permissions to put a user’s items in an itemset which corresponds to a project?