Providing user data for account provisioning to repository administrators

Providing data for creating ORCID users

Login to ReSeeD via RUB LoginID is available to any researcher from Ruhr University Bochum with staff status ('Mitarbeiterstatus'). For other RUB users (see FAQ) and external scientific collaborators, an ORCID must be registered by ReSeeD service provider upon request by a RUB staff member.

The following information is required to register new ORCID users:

  • First Name
  • Last Name
  • Email address
  • ORCID iD

To provide information for multiple users at once, we recommend using the provided template table. This improves clarity and facilitates bulk account creation. You may use either the .xlsx or .csv version.

You can download the templates here:

How to use the template:

  • Each user occupies one row
  • Required fields for ORCID-based account creation are:
    • first_name
    • last_name
    • email
    • orcid
  • Keep column names (headers) unchanged.
  • Do not merge cells.
  • If using a .csv file, we recommend saving it with UTF-8 encoding with BOM.

Providing data for assigning group membership

You may also provide group membership information — for both ORCID users and users who log in via RUB LoginID.

Using groups allows for granular access control for datasets, such as separating read and write permissions. At present, group creation is not available as a self-service feature. Please contact the ReSeeD service provider if you wish to use this functionality.

After planning how you want to use groups in ReSeeD, you can use the same template table to submit role and membership information. A JSON mapping file will be used to map group and subgroup names to internal identifiers. This mapping will be maintained by the ReSeeD team after consultation.

Required fields for role assignment:

  • email
  • Either loginid (for RUB users) or orcid (for external or RUB non-staff users)

⚠️ Note: ORCID is recommended for external users even if they have acquired a temporary LoginID!

Default behavior: All users in the table are assigned the role of member of a main group, e.g., a member of CRC 1234 will be mapped to crc_1234_member.

Additional roles (optional):

  • group_manager: Whether the user is also manager of the main group.
  • subgroup: Subgroup name (must match an entry in the mapping JSON).
  • subgroup_manager: Whether the user is manager of the subgroup.

⚠️ Note: Subgroup roles are exclusive — a user can be either a member or a manager of a given subgroup, but not both.

Data Format For Account Info (Template Table)

Each row in the template table represents one account and/or role entry. A single user can appear in multiple rows if they hold multiple roles (e.g., subgroup memberships).

Column Type Example Notes
loginid STRING beispbyz Required for SAML users (RUB). Validated via regex.
first_name STRING Barbara Required for new account creation.
last_name STRING Beispiel Required for new account creation.
orcid STRING 1234-1234-1234-1234 Required for ORCID users. Validated via regex.
email STRING barbara.beispiel@rub.de Always required. Validated via regex.
group_manager BOOLEAN true Optional. Defaults to false.
subgroup STRING A01 Optional. Must match a key in the mapping JSON.
subgroup_manager BOOLEAN true Optional. Defaults to false. Specifies role within the subgroup.
comments TEXT Main contact person Optional. Ignored by the script — for internal notes or remarks.

Final notes

  • Only provide data that is accurate and validated.
  • Avoid editing column names (headers).
  • Contact the ReSeeD service provider if you need any help.