On this web page we explain the minimal requirements for the acceptance of publications in the repositories of the ETH library (Research Collection and ETH Data Archive). Furthermore, we evaluate file formats regarding their suitability for archiving. We also explain how to convert your files in suitable formats, and how you can use the software DROID to track unsuitable files even from large data collections.
1. Minimal requirements
1.1 Publications in Research Collection (text formats)
For publications of research articles the recommended text formats are accepted (table 1, left column) and also some of the text formats that are suitable to only a limited extent (first paragraph of middle column). Thus, the file formats PDF/A and PDF are accepted. Not accepted for publications of research articles are the text formats that are not suitable for archiving (table 1, right column or second paragraph in middle column). Thus, Word and PowerPoint formats are not accepted.
1.2 Research data and supplementary materials
No requirements apply to the publication of research data and supplementary materials in the repositories of the ETH Zurich. However, please be aware that the future use of some formats may become very difficult and consult our evaluation in the table below.
2. Assessment of various file formats
Table 1: Our assessment of future readability of some common file formats. (For more detailed information we refer to the recommendations of the Bundesarchiv (German), the KOST (German or French), the , the Forschungsdatenzentrums Archäologie & Altertumswissenschaften IANUS (Germany), the Library of Congress and the Harvard Library.)
Suitable to only a limited extent
Not suitable for archiving
Not accepted for publication, OK for supplementary materials:
Spreadsheet or table
|Raw data and workspace|
|Raster image (bitmap)|
2.1 Suitable to only a limited extent
If you plan using your data for up to ten years we recommend the formats in the middle and the left column of Table 1. Even less known formats that are common in your area of expertise for this type of data are usually suitable.
You should also consider the following points:
- Files in rare formats should be converted into common formats whenever possible. You should archive the original file and the converted file.
- The files should not be dependent on references to data, templates, fonts, or programs stored elsewhere, but instead, such objects should be archived too. If this is not possible, you should describe the existing dependencies on other files or programs in a plain text file ("readme"). You then archive the readme file together with the data.
- Files should not be password protected, encrypted or compressed. If you absolutely need to encypt data, please configure access rights such that data can still be opened after your departure.
- Use only letters, numbers, underscore (_) and hyphen (-) for naming folders and files. Avoid spaces, slashes, and other special characters. For more infomation see this guidline.
- The file extension should be consistent with the actual file format.
2.2 Recommended file formats
For storage over more than ten years, we recommend file formats in the left column of Table 1, such as PDF/A, ASCII text, and TIFF. Also PNG, SVG and JPEG2000 may be appropriate. Bear in mind that the future readability of a file will also strongly depend on the used file features: Reading fancy features of a format, such as video data within a PDF file, will be less reliable than reading basic features.
To use files for more than ten years, the file formats should be very common and, if possible, follow standards that are open and not proprietary. Nevertheless, it cannot be guaranteed that your data will remain readable over the long term, as this depends on future software developments.
The ETH Library will review the archived file formats regularly and will attempt to convert outdated formats into more common formats. The original file will always be kept.
3. Recommended conversion methods
We recommend the conversion methods shown in Table 2. Useful conversions also depend on the type of information that is stored in the files. You may store your Excel spread sheets in *.csv files, but if the Excel file contains also macros, equations or embedded objects, this information will be lost.
You should check the quality of your converted files. The original and the converted files should be archived.
Some more recent file types (*.docx, *.xlsx, *.pptx) are so-called container files. By attaching the file extension “.zip” to the file name you can check the single file components. You may also save such simpler files separately.
Table 2: Recommended file conversions
|File type||Recommended conversions|
|Workspace Dump in Matlab, R or S-Plus|
4. File format verification with DROID
For large data collections you can get an overview of your file formats using the free JAVA application DROID. Furthermore, this tool detects unknown file formats as well as inconsistencies between file extensions and file contents (figure 1).
With the exception of text files, files usually contain a special string of characters to indicate the file format. This character string is also referred to as signature or as magic numbers. If DROID finds a known signature within the file, this is used to determine the file type. In this case "Signature" or "Container" is indicated in the column "Method" (see figure 1). If the signature within the file is not consistent with the file extension, DROID shows a warning sign (yellow triangle with exclamation mark).
Pure text files (*.txt) or tables in text format (*.csv files) do not contain any signatures. DROID classifies such files by using the file extension. If there is no signature and the file extension does not indicate a text file, the file is not classified at all (both files at the bottom of figure 1).
The software tool docuteam packer is recommended and set up for some customers by the ETH Library. This tool detects files with unclear or unknown formats and produces a list comparable to that of DROID.
Figure 1: Screenshot showing DROID verification for some test files. Files with unclear or unknown file types can be easily detected.