Priviledges
Currently, the following roles have been distinguished that define the scope of operations:
Table 1
Function | Explanation |
admin | application administrator (unlimited rights) |
superdataentry | editor with extended privileges (can edit his own records and records created by other editors from his unit) |
dataentry | Editor (can only edit records of which he is the owner and records of people with lower privileges, i.e. selfimport, selfedition) |
superdownload | can perform exports of complete data from the system (including protected data) |
betatester | can perform new functions in testing mode, not yet available to general users |
XMLimport | can perform XML imports |
scoring | Can assign/correct scoring in journal descriptions; |
manualScore | can manually assign/correct scores in publications |
PBNexport | can generate data in a format acceptable to PBN (only for Polish installations) |
financeview | can view financial data (e.g., in project descriptions) |
statisticsview | can view generated statistics and other aggregate data |
versions | can perform global changes on types that are not under strict administrator control |
selfedition | can edit the data on his profile |
selfimport | can import its own publications (in BibTex format, MODS, by DOI) |
Functional privileges assigned according to the above roles can be further restricted as follows:
Table 2
Data types | limitation |
publications | editorial operations can be performed on all types of description of scientific achievements (publications, projects, patents, doctoral theses, dissertations, activities, achievements, etc.). |
people | editorial operations can be performed on the researher’s profile |
diplomas | editorial operations can be performed on diplomas records (doctoral, MSc, BSc theses) |
projects | editorial operations can be performed on project records |
technology | editorial operations can be performed on technology records |
activity | editorial operations can be performed on activities, prizes and awards |
For example, assigning the roles dataentry and publications allows the user to edit all types of records, but only those ones that he/she is the owner of.
An additional limitation is by defining the access level. If the access level of a user with editing rights is the entire university, the user can edit all resources of the university. If the user's access level in edit mode is limited to a unit (institute or department), the user can edit only those objects that are “owned” by the same unit.