We're currently reworking the roles in the reporting module, and I would like to use this opportunity to explain how we envision roles should work in the reporting module. This description is only valid for the reporting module and does not pertain to the classic reporting module. 

Vision

The vision is to make it clearer who can do reporting and on what.

To make this happen, any user who should be able to do reporting, must have a reporting role, either organizational (local) or global, or be an administrator. A user can only report on what they are able to read. This means that any user must have a role specific to the content type they wish to report on, or the general reporter role.

Another important distinction for reporting is how organizational roles are interpreted. For reporting, organizational roles are taken from the associated organizations, where elsewhere in Pure, it is the managing organization that determines the level of access. We need to make this distinction to make sure that users can in fact do reporting on the content that they have been involved in. Either as a researcher, or as someone who needs to get an overview of the activity their part of the organization have been involved in. 

Example

To put this into context, consider the following example:

In this example, there are two organizational units assigned to the output, Faculty of Health Science and Department of Computer Science. The managing organization on this is Faculty of Health Science.  To edit this output, a user must have edit right on the Faculty of Health Science. For reporting, you would be able to report on this output, if you have a reporting role on either organizations. 

Values and filters

What can you then report on? If you have reporting rights on a content type, for instance research outputs, you will be able to report on all the values and use all the filters that the reporting module have. You will also be able to make relations to other content, but only to the content directly linked to the content where you have reporting rights. If you make a relation to another content type, for instance from research outputs, to persons, then you will not be able to see any other values than the short render. You will also not be able to make any further links, or use any filters on this content type. 

Example

Take the research output from before. 

Alice and Bob will be able to report on the research output above, where Charlie cannot, but all research outputs where Department of Politics are affiliated instead. 

Column A is the title of the output. Column B is the name of the associated Person, and column C is the name of the organization of the person. So A is research output content type. B is a person content type, and C is an organization content type. 

Since Alice only have a reporting role on research outputs, she can see all information about the research outputs for Faculty of Health Science. She can make relations to content that is related to the research output, for instance the person. For the person content type, she can only use values that are used for the short render, such as name. She cannot make any further relations from Person. 

Overview

Confidential content

To enable users to report on confidential content, they must have access to that content. This can be achieved if they hold another role, such as an editor of research output, specifically for research outputs. Additionally, we've introduced a configuration that allows any reporting role to access confidential content. However, this access is limited to the content types assigned to their respective roles.

For example, if a user has a reporting role designated for Research outputs and the relevant configuration is enabled, they can report on confidential Research outputs. However, they will not have access to other types of confidential content, such as Projects.

The configuration is located under Administrator → System settings → confidentiality.

Detailed Example

Example report 

• Research output
  • Organizations (associated)
  • Persons (contributors) – expanded
    • Organizations (affiliations)

As. seen by an administrator: 

Columns with * are non-reportable details. 

As seen by a user with local Output and Person reporter permissions on org1:

Explanation:

• output2 is not reportable by the user and the row is eliminated
• The associated organization's semantic relationship is not restricted, and the wide preview of organization name is visible because name is a reportable property.
• Person1 is affiliated with org1 and is thus reportable by the user, allowing the display of ORCID and following the affiliations semantic relationship to organizations. 
• Person2 is not affiliated with org1 and is thus not reportable by the user. Hence, the non-reportable ORCID is hidden. Also, the organization affiliations relationship is restricted.
• The non-reportable Number of descendants is not visible for any rows because the user has no reporting permissions on Organization