Research Data Management

To avoid errors, mix-ups and long search times in future, it is worth investing some time in creating a systematically organized file and folder structure already at the start of a project. This is especially important if you are collaborating with other research groups. Everyone involved in a project should agree to a scheme and stick to it. It is advisable to record the organizational and naming scheme in a document which you subsequently deposit with the published data as an accompanying document.

• Group related files in folders (e.g. for measurements, methods or project phases)
• Use clear, unique folder names
• Use a hierarchical folder structure (N.B.: too many nested levels results in long and complicated filepaths)
• Keep active and completed work in separate folders and delete any temporary files that are no longer required.

Make sure you use file names that are unique and are also meaningful for people who are not involved in the project. General elements that can form part of a name:

• Creation date (YYYY-MM-DD)
• Project reference/name
• Description of the content
• Name of creator (initials or whole name)
• Name of research team/department
• Version number

To avoid operating system constraints, use the following character/naming conventions:

• Short names
• No special characters (: & * % $ £ ] { ! @)
• Use underscores _ rather than blank spaces or dots
• Include a file suffix wherever possible (.txt, .xls, etc.)
• Do not rely on uppercase/lowercase distinctions

The careful choice of a file format can ensure that files can still be used after many years and consequently greatly facilitate reuse of the research data. When choosing a suitable format, various factors should be taken into consideration:

• Future-proofing: how many software products can read the data format?
• Open access to documentation
• No legal constraints (patents)
• No technical constraints (encryption, DRM)
• Established in community

The file formats for research data can vary widely depending on the discipline in question. The following file formats are recommended:

• Images: TIFF, TIF
• Documents: TXT, ASC, PDF/A
• Tabular data: CSV
• Audio files: WAV
• Databases: SQL, XML
• Structured data: XML, JSON, YAML

Further information about which file formats are recommended for long-term preservation can be found at here.

It is essential to use version control, especially for datasets that change over the course of a project. Individual datasets should be named sequentially and the names should include the save date (YYYY-MM-DD) along with the version number. The final version should be indicated as such. Maintaining a version table in which all changes and new names are recorded can help keep track of the datasets.

We recommend you back up your data using the university's IT system as it collects the data campus-wide and redundantly backs it up to two state-of-the-art tape libraries.

Click here for more information: Campus Backup/Archive (access only via campus network)

You should always adopt the 3-2-1 backup strategy:

• 3 copies of the data (1 original + 2 backups)
• Stored on 2 different types of media (external hard drives, USB sticks, SD cards, CDs, DVDs, Cloud)
• 1 copy off-site

Backup should be automated to run at regular intervals. Check that the backup was successful and that the data can be retrieved again if necessary.

Comprehensive documentation is essential to enable correct interpretation and reuse of the data at a later date. Among other things, the documentation should include details about the time and place the data was collected, the methods, tools, software and statistics models used, as well as information about the parameters chosen and any missing values, along with nomenclature and acronyms. This information can be added complementary to your dataset, e.g., in the form of supplementary documentation in a ReadMe file.

Further information on data documentation can be found here and on ReadMe files here.

The decision about what data for a project should be archived and for how long depends on the academic value of the data as well as on legal, regulatory and financial factors.

As a minimum, however, all the data on which a publication is based must be stored and the corresponding metadata must be published online.

The Digital Curation Centre (DCC) and forschungsdaten.info list five steps for deciding what data to keep.

• Guide (English)

Whenever possible, data should be deposited in subject-specific repositories. These are geared to the needs of the subject area, are familiar with specific data formats and often also offer subject-specific metadata.

Which data repositories can be used? A comprehensive list of data repositories is provided by the SNSF (the SNSF list is not exhaustive) and Scientific Data.

The best starting point for your search for a suitable repository is Research Data Repositories (re3data.org).

An institutional data repository (BORIS Portal Research Data, Research Project, Research Funding) has been officially launched. BORIS Portal allows you to archive and manage research data, to determine access options and manage rights, as well as to link project and researchers’ profiles, to make it accessible and clearly identifiable. Login to BORIS Portal research data, projects and fundings via your campus account.

Sharing figure

Figshare  - store, share and discover research.

Sharing methods

protocols.io A secure platform for the development and exchange of reproducible methods.

The Open Science Team at the University Library of Bern recommends licensing research data under the Creative Commons Public Domain Dedication (CC 0) or the newest version of the Creative Commons Attribution International Public License CC BY licenses to allow maximal reusability. If data cannot be openly published due to ethical or legal reasons, metadata and supplementary material can be published under CC0 to fulfil funders' agencies' requirements.

The Swiss National Science Foundation (SNSF) allows researchers to choose the best suitable license for the data based on the principle of reusability (e.g., SNSF Policy on Open Research Data).

The European Commission (EC) requires the latest available version of the CC BY or CC 0 or a licence with equivalent rights, following the principle “as open as possible as closed as necessary”. For details, please visit Horizon Europe Model Grant Agreement from 15. December 2021, v.1.1, p. 96 and the EU's open science policy (link).

As part of the FAIR principles, funding bodies require a unique identifier to be assigned to the published data. When depositing your data in BORIS, a Digital Object Identifier (DOI) is assigned to each dataset. Click here for further information.

Research data generated and collected during a project can often be useful beyond its original purpose. It is therefore worthwhile making the data obtained publicly accessible. For this purpose it is important to ensure that your data is assigned persistent identifiers, good metadata is generated and sufficient documentation is provided to enable the data to be reused.
There are currently three ways of publishing research data.

Publication in a repository

Research data can be published in a disciplinary or a general repository. If possible, it is preferable to publish data in a disciplinary repository rather than in a generic one. Further information about selecting a suitable repository can be found in Finding a repository.

Publication in a data journal

Data papers published in data journals are documents that facilitate the dissemination and reuse of published data. These publications contain all information about data collection, methods, licenses and access rights along with information about potential reuse opportunities. The data itself is usually deposited in a repository.

The website of the Humboldt University of Berlin has a list of data journals.

Publication as a supplement to an article

Data can also be published as additional information for an article in a periodical. This is usually the data on which the publication is based which enables the findings to be understood. The data may either be deposited directly on the periodical's platform or in an external data repository.  

When citing data it is advisable to use either the standards applicable to the research field in question or the form suggested by the repository in which the dataset was deposited. If there are no particular standards or recommendations, Datacite recommends providing the following details as a minimum:

• Author
• Year of publication (of the dataset)
• Title
• Edition or version (optional)
• Publisher (for data this is usually the archive in which the data is stored)
• Resource type (optional)
• Persistent identifier (as a permanent linkable URL)

Information and action guide for publishing open source software.

Data security IT-Department, University of Bern (German version only, Pdf)

• Legal service office of the University of Bern (data protection, legal questions) E-Mail
• Unitectra supports researchers in the commercialization of research results into new products and services (patents, licenses), in the negotiation of research agreements as well as in the creation of a spin-off company E-Mail

Data protection and research in general: EDÖB (addresses federal bodies and private persons, here for general information in German, French and Italian only). Researchers at the University of Bern must normally comply with the Cantonal Data Protection Act).

European General Data Protection Regulation (GDPR). Introductory Ordinance to the EU Data Protection Directive 2016/680 on the protection of personal data (Introductory Ordinance to the EU Data Protection Directive) of the Canton of Bern.

The data protection laws of some countries are recognized as equivalent to those of Switzerland (Transborder data flows).

Personal data is information about specific or identifiable natural or legal persons. The Data Protection Act of the Canton of Bern (KDSG) serves to protect individuals from improper data processing by authorities.

If you collect, analyze or otherwise process personal data in your research project with the help of IT applications (e.g. self-programmed apps, but also applications such as Qualtrics or RedCap), it may be necessary to draw up a concept for handling information security and data protection (ISDP).

Such a concept serves to clarify the requirements and existing or to be developed technical solutions in this area, as well as, if necessary, as the basis for control by the data protection authorities of the canton. The legal basis for this is the data protection legislation of the Canton of Bern, in particular, the Data Protection Act (KDSG), Art. 17a. The "Directives on Data Protection in the IT Sector of the University of Bern" must be followed.

For information and advice on legal matters, please contact the Legal Services of the University of Bern, and for IT security matters and for filling out the relevant forms, please contact the IT Services. IT security at the University of Bern: Expanding your knowledge workshop (Link).

Research projects involving humans that fall under the Human Research Act (HRA) must be reviewed by ethics committees (e.g. animal experiment ethics SAMS or Cantonal Ethics Committee (CEC)). Please note that such a review may take approximately 60-90 days. For more information on the procedure, process and management of such projects, please visit the portal on human research in Switzerland Kofam.

Research projects that do not fall under the Human Research Act can be approved by the Ethics Committees of the University of Bern Phil.-hum., WISO und Animal Welfare Office UniBE.