We plan to host multiple projects from multiple scholars. Omeka S is very appealing, except that all the users seem to be able to access and manipulate everyone else’s item sets. That approach doesn’t scale, and has the possibility of accidental or even deliberate changes to others’ work.
- Am I missing something about Omeka S whereby users could control others’ access?
- If not, how difficult would it be to add some access controls to Omeka S?
- Or, should we just expect to have multiple Omeka instances in order to manage access?
- If we should have multiple instances, what’s the case for Omeka S? It seems more robust, under the hood, than Omeka Classic, but doesn’t yet have as much support for themes and plugins/modules.
Thanks in advance for your thoughts.