Introduction
A catalog groups one or more projects. A project contains several records. The catalog implements a system of rights based on the notion of project. It does not allow a finer granularity.
The different roles
For this paragraph, let us assume that our catalog is called MY-CATALOG and that it contains a project called MY-PROJECT.
The catalog uses four roles:
- The catalogue administrator (MY_CATALOGUE_MEMBER). For all projects in the catalog this user can:
- Create/Modify/Delete records
- Access all data
This role often corresponds to the technical managers of the tool.
- The metadata editor (MY_PROJECT_METADATA_EDITOR). This user can:
- Create/Modify/Delete records related to this project
- Access all data in the records related to this project
This role often corresponds to project managers
- The project’s restricted community member (MY_PROJECT_EMBARGO_DATA_ACCESS. This user can:
- Access all data in the records related to this project
This role often corresponds to project members
- The project’s community member (MY_PROJECT_DATA_ACCESS). This user can:
- Access all data in the records which aren’t covered by an embargo
How to get a role ?
If you think you shoud be allowed to edit metadata records for some projet or have access to project data, you should contact the project responsible. The name of the responsible can be find in the contact section of a metadata record or in the project website.
How to give a role ?
If you are a catalogue administrator or a metadata editor you can assign roles for your projects to people registered in the catalogue directory.
To do this, you have to go here.