If I have several independent collections (perhaps for different institutions or clients), do I need a separate Omeka install for each client?
That is, I'd like to have a single administrator account (myself), with access to several client accounts; each client account should not be aware of the other clients, and should not have access to objects held in the collections of other clients.
The administrator account would be great for managing pan-collection metadata, access statistics, etc.
Is this a case for a custom install, rather than Omeka.net? Maybe with a custom administrator layer written from scratch?