Dataverse Organization

This page is written mostly for decentralized data managers. Its purpose is to be a policy documentation for Jülich DATA as a service for scientists.

Todo

Add a visual decision tree for easier comprehension. But: do it in a user targeting help page

Baseline

1. All datasets stored in Jülich DATA reside in a hierachical structure. This primarily depicts the organizational entities of Forschungszentrum Jülich.
2. No datasets are stored at the root level Jülich DATA.
3. Non-staff has no permissions anywhere by default. Administrators, Curators or others with corresponding permissions have to grant them explicitely. See Dataverse Permissions and Dataset Permissions for details.

Campus Collection

Campus Collection contains no dataverses, only datasets:

Every staff member of Research Centre Jülich is (automatically) allowed to add datasets to the Campus Collection, but cannot publish it standalone. Entries are curated by the central library.

Please note: a director might decide you may not add data to the Campus Collection. Rouge entries will be either moved or deleted by its curators.

Institutes Dataverses

Research institutes[1] like (non-existing) IEK-33 and INM-22 organize their own dataverses as they see fit:

Those are curated by their named decentralized data manager. Please ask them for any special rules that might apply for their dataverse. Usually those rules come into effect by decision of the director.

Footnotes

[1]	Research Centre Jülich consists of about 80 organizational units, called “institutes”. Many of them publishing scientific data might have their own dataverse.