ACL permission based on rights. Permission would match the rights taxonomy.
Google user: jessica%...@gtempaccount.com
Feature enhancement requested by user.
See wiki for explanation [http://qubit-toolkit.org/wiki/index.php?title=Release_1.3#Features ]
[g] Legacy categories: Access control
#1 Updated by Anonymous almost 10 years ago
The wiki no-longer has the use case scenarios. See below:
Use Case Scenario
1. Researcher requests access to view restricted records, "restricted" means records that are not normally accessible because of:
legislated access restrictions (e.g., FOI); or
donor agreements; or
archives policy; and
does not include reasons related to copyright law.
2. Archives evaluates researcher request based on type of restrictions, user's credentials, purpose of access, etc.
3. Archives issues access permission based on a written agreement or assignment of rights in which permission is limited to:
one specific user; and
one specific record or set of records (i.e., all records at or below a particular description node); and
a specific class of restrictions (e.g., permission to view all personal information, but not permission to view 3rd party business information); and
a particular time span. (e.g. "while researcher is in the reading room" or "three months from start date")
4. Identified problem
In ICA AtoM, we need to be able to:
issue permission to a specific researcher to view restricted records; and
authenticate that researcher; and
establish the record or set of records they have permission to view; and
establish the class of restrictions they have permission to view; and
establish the duration of the permission (i.e. it has an automatic expiry or can be revoked by the Archives)