Multiple collections withdifferent users and access?

michaelzimmer

Hi all - I'm hoping to be able to use CollectiveAccess for a particular set of needs:I want to have a general website for my institution's multiple collections of unrelated items. Each collection would have its own separate description and access controls. I'd have an "umbrella" webpage that shows all the various collections, but then as a user clicks through to an individual collection, separate access rules would apply. For example, a user could be authorized to access Collection A, but not necessarily Collection B or Collection C, all of which are located within a single installation of CollectiveAcess. Is this possible?

Julia

<font face="Arial, Verdana" size="2">In Providence (CA back-end) we support source-level access control that would allow you to grant read/edit/no access to a user for Collection A with different privileges for Collection B.  It would be possible to extent this functionality to Pawtucket (front-end) with some custom configuration and theme work.  You may also want to look at metadata-level access control, which determines field-level access:</font>

<font face="Arial, Verdana" size="2">http://docs.collectiveaccess.org/wiki/Access_Control</font></div>

samall

Hi Michael,In Providence we use access rights on one CollectiveAccess instance. If you work with collections, then you can define the access rights on collections and let the objects inherit the access rights from the parent collection. So I think it is possible what you want to do.  How many objects do you have? Because if you have too many objects it gets slow. We have 120000 records in that instance.Sam

michaelzimmer

Thanks, Sam. I'm still learning the right nomenclature, but I think what I'd have are multiple collections, each with probably 100-500 items. So, it sounds like when user accounts are created, they could be granted access rights to particular collections, correct? And all the collections could be listed on a general user-facing homepage?