ESciDoc Access Rights

Work in progress

• based on meeting NBU, UTS, MFR

Related discussion

see ESciDoc Institutional Visibility Discussion

Retrieval of items and components

• Rule of thumb: a component (i.e. its content) cannot be evtl. retrieved by the user if she has privilege to view it's enclosing item

Description of the roles/groups in the access component rules table

• Depositor - user who can create items in the repository and manage items (including components and their content) she created in accordance with the overall workflow rules.
• DataAdmin - user who has the possibility to create items and manage items (including components and their content) independently from their ownership and in accordance with the overall workflow rules.
• QARole - placeholder for roles in the system that are responsible for the quality assurance of the data e.g. Metadata editor, Moderator, Authority, Rights checking.
• Collaborator - placeholder for user-groups in the system that can access the content under specified conditions of item and version statuses.

• Audience - general placeholder for roles / groups in the system
  • Internal - access level is allowed for above mentioned roles of Depositor, DataAdmin, QARole
  • Public - no access level restriction
  • Group - Groups of users (account users, unregistered users) that can be authorized via single criteria or combination of:
    • List of organizational units
    • List of account users
      • Can we consider IP ranges as a special account user e.g. user is "MPI für Psycholinguistic" user (and the IP ranges associated with this account are defined by the Administrator)?
    • Key/Certificate based (unregistered user)

• Audience and Collaborator groups differ by their access rights during the Item workflow. In addition, Colaborator group may have modification privileges (not yet described in here).

Description of the access component rules table

• Item status - the public-status of the item. Item may have different public status then the status of the last version of the item.
• Who may access - Name of the role or group that can access the content associated with the component of the item.
• Where is role defined - The eSciDoc resource type for which the role or group has been associated when granting privilege for access
• Check for access level - Whether or not to check the access level for this role/group under specified conditions

Access rules table for Components

Item status	Who may access	Where is access level defined	Check for access level
pending	Depositor (only if owner) DataAdmin	Context	No
pending	Colaborator	Component (thus Item implicitly)	No
submitted, in-revision	Depositor (if owner) DataAdmin QARole	Context	No
submitted	Colaborator	Component (thus item implicitly)	No
released	Depositor (if owner) DataAdmin QARole	Context	No
released	Colaborator	Component (thus item implicitly)	No
released	Audience	Component (thus item implicitly)	Yes => Access level can be Public XOR Internal* XOR Group*
withdrawn	Depositor (if owner) DataAdmin QARole	Context	No

Example

• Item A is created by Depositor D in context C and consist of:
  • Component C1
  • Component C2

• QA User 1 - has QA role assigned for context C
• QA User 2 - has QA role assigned for context C, context D

Case 1

• Depositor D gives Internal access for Component C2 and Public access for Component C1
• Depositor D gives additionally access to Colaborator User U and to Colaborator Person P and to Colaborator Department DEP for Component C2

• Colaborator User U - is account user and is known to the system via his/her user account
• Colaborator Person P - is a system visitor who received a security "Key" from Depositor D with which s/he can access the Component C2

• According to the upper table:
  • When item is in Pending status, beside Depositor D:
    • Component C1 can be accessed by DataAdmin
    • Component C2 can be accessed by Colaborator User U and DataAdmin

• • When item is in Submitted status, beside Depositor D:
    • Component C1 can be accessed by DataAdmin, QA User 1, QA User 2
    • Component C2 can be accessed by Colaborator User U, DataAdmin, QA User 1, QA User 2

• • When item is in Released status, beside Depositor D:
    • Component C1 can be accessed by any user (i.e. Audience=Public)
    • Component C2 can be accessed by Colaborator User U, DataAdmin, QA User 1, QA User 2

• • When item is in Withdrawn status, beside Depositor D:
    • Component C1 can be accessed by DataAdmin, QA User 1, QA User 2
    • Component C2 can be accessed by DataAdmin, QA User 1, QA User 2

Case 2

• Depositor D gives Internal access for Component C2 and MPG wide access for Component C1
• Depositor D gives additionally access to Colaborator User U and to Colaborator Person P for Component C2

• Colaborator User U - is account user and is known to the system via his/her user account
• Colaborator Person P - is a system visitor who received a security "Key" from Depositor D with which s/he can access the Component C2

• According to the upper table:
  • When item is in Pending status, beside Depositor D:
    • Component C1 can be accessed by DataAdmin
    • Component C2 can be accessed by Colaborator User U, DataAdmin and Colaborator Person P

• • When item is in Submitted status, beside Depositor D:
    • Component C1 can be accessed by DataAdmin, QA User 1, QA User 2
    • Component C2 can be accessed by Colaborator User U, Colaborator Person P, DataAdmin, QA User 1, QA User 2

• • When item is in Released status, beside Depositor D:
    • Component C1 can be accessed by any user that comes from MPG (i.e. Audience="MPG wide")
    • Component C2 can be accessed by Colaborator User U, Colaborator Person P, DataAdmin, QA User 1, QA User 2

• • When item is in Withdrawn status, beside Depositor D:
    • Component C1 can be accessed by DataAdmin, QA User 1, QA User 2
    • Component C2 can be accessed by DataAdmin, QA User 1, QA User 2

Internet Protocol

Max-Planck-Institut

Enhanced Scientific Documentation

Quality Assurance

Max-Planck-Gesellschaft