DaRUS is based on the OpenSource Software DataVerse and offers university groups (institutes, working groups, SFBs, projects) the possibility to maintain their own data universes with their own search criteria and description options. The data sets are described in such a way that they are easy to find and share. An API offers the possibility to automate the upload and the access to the data. The data sets do not have to be published, but can be easily quoted and made available to the public with a DOI. In this way, not only can the requirements of funding organizations or journals be met, but important research results within a research group can also be made visible and usable in the long term. In addition to the production system, DemoDaRUS offers a test environment in which the functionalities of DaRUS can be experimented with.
Currently DaRUS is in productive pilot operation. If you would like to use DaRUS for your working group or project, please contact the FoKUS-Team.
Frequenty Asked Questions
The web interface of DaRUS can be found at https://darus.uni-stuttgart.de . As a non-registered user you will see all published datasets and data areas (Dataverses).
The DemoDaRUS test system can be found at https://demodarus.izus.uni-stuttgart.de/. The test system can only be accessed within the University of Stuttgart.
Please contact us (see contact box below). If a dataverse already exists for your institute, we can tell you the local administrator. In the other case, we will create a data area (Dataverse) for your institute after a consultative meeting, which you can then manage yourself. For this, there has to be a local admin with the role "DaRUS-Administrator" in the Uni-Admin-Portal. Contents of the consultation are: Functions and configuration possibilities of DaRUS, rights and duties as DaRUS admin, application goals, data types, formats and volumes, description categories, automation.
Login is done on the DaRUS homepage via Shibboleth. Click on LogIn in the top right corner and select "Universität Stuttgart" as Institution. You will then be redirected to a login page where you can login with your AC account. In addition to the published datasets and dataverses, you now also see all data and dataverses to which you have rights.
In the DaRUS Knowledge Base on DaRUS you can find instructions for the first steps on DaRUS.
If you want to upload large amounts of data to DaRUS on a regular basis, please contact your local administrator or, as an administrator, the DaRUS team. We can then activate direct upload to the data backend for your dataverse.
More information about the different ways to upload files can be found under BigData.
In your dataverse, you can decide for yourself which users have which rights to the data records.. You can create user groups and assign roles to individual users or user groups. In order to assign rights to a user or to add a user to a group, this user must first log in to DaRUS via Shibboleth.
In addition, you can configure which search and description categories (metadata) should be available for your research data and which must be filled in optionally or mandatory. You can also create templates that prefill frequently used metadata.
Each dataverse has its own rights management. Rights are not inherited from a higher-level dataverse to lower-level dataverse. You need admin rights for a dataverse to be able to grant rights to other users or user groups. Rights can be assigned at the level of dataverses or records.
First, you need a dataverse for your project. If your institute already has a dataverse, the local admin (with the role DaRUS-Administrator in the Uni-Admin-Portal) can create a dataverse for you and give you admin rights for this dataverse.
Afterwards all project partners have to register once with DaRUS via Shibboleth so that they appear as users in the system. Then you can give the partners the desired rights to the project data averse.
In order for external partners to be able to authenticate themselves with DaRUS, the respective institution must be a member of the EduGAIN network and has to submit DaRUS four different attributes (eppn, givenName, sn, mail) to allow the creation of new user account. If there are any problems, please contact the FoKUS team.
Each data set is assigned a DOI (Digital Object Identifier) as ID during creation. You must publish the data record so that it can be permanently accessed by the public under this DOI. The data record goes through a publication workflow in which it is first checked from a scientific point of view and then from a formal point of view. After release, the DOI is registered and the data record is released to the public.
Allow at least one week for the publishing process. After the internal content control it usually takes about 3 working days until you get feedback from the DaRUS team. Until the actual release and publication of the data set, a revision may be necessary.
DaRUS offers different degrees of publicity:
- Published with DOI without restriction: Both the description (metadata) and the data itself are fully accessible to the public. Access to the data set is counted, but no information about the users is collected. (Application example: OpenData)
- Published with DOI with guestbook: The metadata is fully accessible, but users must complete a questionnaire before downloading the actual files. The data is made accessible independently of the answers to the questionnaire (application example: need for information about subsequent users of data).
- Published with DOI with file protection: The metadata is fully accessible, the files can only be requested and must be explicitly released by an administrator. (Application example: Restriction to scientific use of data relevant to data protection)
- Unpublished with private URL: A so-called private URL can be created for an unpublished record. Anyone in possession of this URL can access the record. (Application example: Access to data for reviewers)
- Unpublished: Unpublished datasets can only be accessed by users who have been explicitly granted rights to the Dataverse they contain. (Application example: sharing data in the project context)
Contact your local administrator and refer them to these FAQs.
When assigning rights to a dataverse, they are synchronized with the index with a time delay. To trigger the synchronization manually, change the metadata configuration of the data verses in question.