Table of Contents

Compliance with legal standards and guidelines

Description

Guidelines of ETH Zurich

Are you aware of the Guidelines for Research Data Management at ETH Zurich (RDM Guidelines)?

Are you aware of the ETH Zurich Guidelines on scientific integrity (Integrity Guidelines)?

If no, we recommend consulting them before publishing research data.

Copyright

Have you obtained the permission of the rights holders?

Have the project partners agreed?

Do you have your employer's permission (e.g. according to employment or other contract)?

If no, obtain permission, advice from ETH legal services, Research Contracts Group or ETH Library

Data protection

Is the research data free of personal information?

Can the data be made anonymous?

If no, obtain permission, advice from ETH legal services, ETH transfer oder ETH Library

Confidentiality agreements

Does an obligation of secrecy preclude the publication?

If yes, obtain permission and advice from ETH transfer

Patenting

Does the publication affect a planned patent?

If yes, advice from ETH transfer, wait for patenting

If you can comply with the legal standards and guidelines, your research data is ready for publication in the Research Collection.

[back to overview]

Choose a license

  • According to the Guidelines for Research Data Management, ETH Zurich advocates the use of Creative Commons licences or public domain dedications (CC0) when publishing research data. 
  • These licences allow authors / data producers to define what types of reuse are permitted for their works. Data published without a licence can only be reused with explicit permission from the copyright holder or based on an exemption in national copyright law. Works published with a CC license can be reused as specified in the license.
  • For help in choosing a Creative Commons license check the page Creative Commons Licenses.
  • Creative Commons licences are inappropriate for software because they do not include provisions for source code or its further development. Opensource licences are inappropriate for research data, as they were designed specifically for software. For more information on software licensing, see Licensing software and programming code/scripts.

[back to overview]

Document your data

  • Include a README file with file extention to document your data. A guide can be found here: https://documentation.library.ethz.ch/x/bQBIB
  • Use meaningful file and folder names
  • Include metadata
  • Link your item to an article or other publication (example)
    Example of linked item

[back to overview]

Edit your data for publication

  • Remove temporary and backup files
  • Remove duplicate files
  • Remove personal information
  • Rename files and folders where helpful (meaningful names)
    • Avoid overly long folder and file names. Total path lengths >200 characters (files and folders combined) can lead to problems for windows users 
  • Remove third party files and software for which you don‘t have permission
  • Check for hardcoded file paths, symbolic links, references
  • Don‘t include your manuscript: Publishers PDFs, Preprints and AAMs (Author's Accepted Manuscripts) should be published as a separate entry. See Open Access articles (self-archiving)
  • Spell check your text files
  • File extensions should be consistent with file formats 
  • Avoid special characters in names of files and folders. These characters hamper compatibility because they lead to undesired effects depending on the operating system
    • Avoid the following characters:
      • \ / ? : * " > < | : # % " { } | ^ [ ] ` ~ as well as blanks
      • Non ASCII characters such as ¢ ™ ® , umlauts (ä ö ü), diacritics such as à é ô etc.
    • The following ASCII characters are permitted:
      • ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789
    • We are currently not aware of problems with the folllowing characters:
      • ! $ & ' ( ) + , - . ; = @ _ 

[back to overview]

Choose appropriate file formats

  • Choose open, well documented standards from your domain
  • For long term preservation (> 15 years) only formats from our list of recommended file formats should be used. Other Formats should be converted. Consult our list of File formats for archiving research data
  • When non-recommended formats are used, long term readability cannot be guaranteed

[back to overview]

Packagage your files for the upload

  • Upload single files directly
  • Pack file collections containing a large number of files or subfolders into a container
    • Use standard container formats: Zip or TAR-files (avoid .7z, tar.gz, .rar, and so on)
    • Use preferably uncompressed containers (compression level “store”)
    • Do not use archives within your ZIP or tar files.
    • Don't use encryption or password protection
  • Large datasets can lead to problems with up- and downloads of your dataset. Limit single files to around 10 GB for a limit of 50 GB per entry.
    • Please split larger folder structures manually into meaningful subunits and package them separately.
    • Don't use the automatic split features of your software. 
    • Datasets larger than 50 GB can be published using our service libdrive.

Instructions for Windows

On Windows operating systems, you should create ZIP archives by using the software tool 7-Zip.

You start by selecting your files and folders in Windows. Then, click your right mouse button to open a menu. Select the software tool “7-Zip”, and “Add to archive …” A dialog box opens as shown below. In the white field on top, you write the name of your archive file. Use the option “zip” and the compression level “store”.

Screenshot dialog box

Intructions for macOS

On a Macintosh computer, you should create tar archives.

You may create tar container files either by using the command line (tar -cvf <archive_name.tar> <folder_to_tar>) or by using the software Keka. If you choose the second option, you start the program Keka and select “Compression” in “Preferences”. You then select the default format “TAR” as in the dialog box shown below. You finally drag your folder onto the Keka icon and fill in the name of your archival file. You should select the option "Exclude Mac resource forks (e.g. .DS_Store)" in the Keka settings. This prevents the inclusion of macOS specific hidden files. 

Screenshot compression

[back to overview]

  • No labels