{{indexmenu_n>7}}
====== Glossary ======

This section contains an overview and short explanation of terms that are used in the wiki. 

**Back-up**\\
Data in the RDMS is secured by storing multiple replicas on two different physical locations.

**CLI**\\
CLI stands for Command Line Interface. In contrast to a GUI, a CLI does not have a clickable graphical interface, but is text-based. The most common CLI to interact with the RDMS is called iCommands.

**Client**\\
A client is a program that is used to interact with the RDMS. These can be used for file transfers and/or other means of data management.

**Collection**\\
Collection is the iRODS term for a folder.

**DataArchive**\\
The DataArchive is a separate location in the RDMS where final data can be archived, for example after the end of a research project or publication.. The RDMS web interface offers a workflow to archive data from the Projects location to this DataArchive location.

**Data Manager**\\
The role of Data Manager in the RDMS is specific for the archiving workflow. The Data Manager is responsible for verifying that the data sent to the archive is complete and uncorrupted, and giving the final approval of the archive. Best practice is to assign this role to the person(s) who actively works with the data. 

**Data Object**\\
A logical representation of data that maps to one or more physical instances of the data at rest in storage resources.

**Data Safety**\\
Data safety is the practice of safeguarding digital information from unauthorized access, accidental loss, disclosure and modification, manipulation or corruption throughout its entire lifecycle, from creation to destruction.

**Data Security**\\
The practice of protecting digital information from unauthorized access, corruption or theft throughout its entire lifecycle.

**DOI**\\
DOI stands for Digital Object Identifier. A DOI is a persistent identifier used for electronic output of scientific research such as electronic books, papers, software, and datasets. With a DOI these objects can always be found even though the location of these objects changes.

**FAIR**\\
The FAIR data principles provide guidance on how to make your data better Findable, Accessible, Interoperable, and Reusable. The aim of FAIR data management is to maximize the use and reuse of research data.

**GDPR**\\
The General Data Protection Regulation is a Regulation in EU law on data protection and privacy in the EU and the European Economic Area.

**Group Admin**\\
This is a role a user can have within the RDMS. A group admin has the ability to create new team drives, groups, and projects and to manage these.

**GUI**\\
GUI stands for Graphical User Interface. Interaction with the RDMS is done via special software called clients. None-text based clients, with for example a clickable interface and icons, are called GUIs. CyberDuck is an example of a GUI-based client to interact with the RDMS.

**Home Drive**\\
The personal Home Drive is accessible to and managed by the current user logged in. This storage space can be used for data that is not accessible to others including research supervisors. Although the data in the Home Drive is only accessible to the owner, data objects and collections can be shared with other RDMS users from this location.

**iCommands**\\
iCommands is the iRODS command line client for interaction with iRODS, thus RDMS, via linux-based workspaces.

**iRODS**\\
The RDMS is developed on the basis of iRODS (integrated Rule-Oriented Data System), open source data management software. iRODS is designed as an archiving system for large amounts of data. The software enables the use of “rules” to initiate automated actions on the data, for example through specific metadata tags. 

**Metadata**\\
Metadata provides information about your data, in other words it is ‘data about the data’. For research data, this could be information about how, when, and by whom the data was acquired, as well as important experimental details, but also publication information if applicable. The RDMS includes a search engine that queries for these metadata. Therefore, if a user wants to reuse data stored on the RDMS, including both own data or others if permissions are correct, metadata information can greatly simplify the process of both finding the desired data and providing important experimental details.


**Metadata Manager**\\
The role of Metadata Manager in the RDMS is specific for the archiving workflow. The Metadata Manager is responsible for verifying and completing the metadata information related to the archive. Best practice is to assign this role to the person(s) who know(s) the origin and scope of the data, along with the knowledge of other locations where the data is stored (knowledge about existing DOIs).

**Metadata Template**\\
With a metadata template the metadata for multiple files or folders can be set. Uniformity in metadata is assured.

**Open Data**\\
Data that is openly accessible, exploitable, editable and shared by anyone for any purpose. 

**Open Research**\\
Open Science is the movement to make scientific research (including publications, data, physical samples, and software) and its dissemination accessible to all levels of society, amateur or professional.

**Open Source**\\
A computer program in which the source code is available to the general public for use or modification from its original design. The RDMS is based on the open source application iRODS. 

**Permissions**\\
Permissions or user privileges are the rights that users have on a data object or within a collection. The RDMS contains four levels of permissions which are, in ascending order, ‘Null’, ‘Read’, ‘Write’, and ‘Own’.

**Permissions Inheritance**\\
Rights to files and folders can be inherited from parents higher up in the file structure.

**Project**\\
The Projects location is a separate location in the RDMS in addition to the Home and Team Drives. Here (collaborative) data can be collected related to a specific research project. In this Projects location, it is possible to assign extra policies if needed. These policies have to be specified and implemented upon request by the users. An example of a policy would be: “Revoke access of participants after XX months”. In addition, a project in the RDMS is the starting point to initialize the archiving workflow.

**Project Admin**\\
The persons assigned 'own' permission for a RDMS Project folder is the Project Admin who can manage a project (add/remove users, etc.).

**Project Manager**\\
The role of Project Manager in the RDMS is specific for the archiving workflow. The Project Manager is responsible for assigning the data manager and metadata manager roles, starting the archiving process. Best practice is to assign this role to a supervisor and/or to the person(s) who have access to the project folder from which the archive is generated. 

**Pure**\\
Pure is the current research information system (CRIS) of the University of Groningen, which serves as a repository for all research output within the university. Data registered in Pure will be visible and findable via the UG research portal.

**Repository**\\ 
A collection of information. Mostly a database.

**Team Drive**\\
A shared storage location for research groups or other collaborators to collectively and safely store data.

**Unishare**\\
Cloud data storage for all UG users.

**User**\\
Every end-user who interacts with the RDMS. So essentially yourself.

**Workflow**\\
A defined way of working. In the RDMS there is a workflow for the process of archiving sensitive data with different rights to that data for researchers and staff involved.

**X/Y Drives**\\
Data storage drives on the UG workplaces. X is for personal data, Y for group data.

**Zones**\\
An iRODS term for different databases. Zones are used to balance and separate storage and compute load within the RDMS.