Archiving research data » History » Version 27
Steve Welburn, 2013-02-05 03:00 PM
1 | 1 | Steve Welburn | h1. Archiving research data |
---|---|---|---|
2 | 1 | Steve Welburn | |
3 | 1 | Steve Welburn | For archival purposes data needs to be stored in a location which provides facilities for long-term preservation of data. As well as standard data management concerns (e.g. backup, documentation) the media and the file formats will need to be appropriate for long-term use. |
4 | 1 | Steve Welburn | |
5 | 15 | Steve Welburn | Whereas work-in-progress data is expected to change regularly during the research process, archived data will change rarely, if at all. Archived data can therefore be stored on write-once media (e.g. CD-R). |
6 | 15 | Steve Welburn | |
7 | 26 | Steve Welburn | In addition, it is not necessary to archive all intermediate results - reuse of archived data mean that requiring a few days to regenerate results is reasonable. However, all necessary documentation, software and data should be archived to allow results to be recreated. Existing archived datasets will not need archiving "again". However, if the archiving system supports deduplication then storing multiple copies of the same content will require minimal additional storage. |
8 | 26 | Steve Welburn | |
9 | 15 | Steve Welburn | Once archived, the archive copy should not be modified directly and data access should only be required to create a new work-in-progress copy of the data to work from. Access to archived data will therefore be sporadic. Hence, it is possible to store archived data "off-line" only to be accessed when required. |
10 | 15 | Steve Welburn | |
11 | 25 | Steve Welburn | It is important that archiving data is performed in an appropriate manner to allow future use of the data. This will require the use of appropriate formats for the data and storage on suitable media. |
12 | 18 | Steve Welburn | |
13 | 20 | Steve Welburn | If the original content is not in an open format, then providing copies in multiple formats may be appropriate - e.g. an original Microsoft Word document, a PDF version to show how the document should look and the plain-text content so the document can be recreated. |
14 | 18 | Steve Welburn | |
15 | 24 | Steve Welburn | Within C4DM, there are currently few [[Data_management_resources|resources]] available to support this. The best available option is the research group network folder as this is backed up to tape. |
16 | 23 | Steve Welburn | |
17 | 20 | Steve Welburn | {{include(Archiving_Properly)}} |
18 | 18 | Steve Welburn | |
19 | 3 | Steve Welburn | h2. Media |
20 | 3 | Steve Welburn | |
21 | 5 | Steve Welburn | Archive copies of data may be held on the same types of media as used during research. Additionally, Write-Once media (e.g. CD-R, DVD+/-R, BDR) may be appropriate. |
22 | 5 | Steve Welburn | |
23 | 5 | Steve Welburn | Removable drives (e.g. USB flash drives, firewire HDD) may be used, but there is a risk of hardware failure with these devices - they are not "just" data storage. |
24 | 5 | Steve Welburn | |
25 | 5 | Steve Welburn | Removable media (e.g. CD-R, tapes) do not have the risk of hardware failure but the media themselves may be damaged or become unusable - the estimated lifetime of an optical disc is 2-100 years. Whether a specific disc will last 2 years or 100 is not something that can easily be judged - although buying high quality media rather than cheap packs of 100 discs may help. |
26 | 5 | Steve Welburn | |
27 | 14 | Steve Welburn | As with all technology, there is a risk of obsolescence |
28 | 6 | Steve Welburn | * devices to read removable media may no longer be commonplace (e.g. floppy disc drives, ZIP drives) |
29 | 1 | Steve Welburn | * formats used for removable media may no longer be supported (e.g. various formats for DVD-RAM discs) |
30 | 6 | Steve Welburn | * interfaces used for removable drives may no longer be commonplace (e.g. parallel or SCSI ports, PATA/IDE disc drives) |
31 | 6 | Steve Welburn | |
32 | 6 | Steve Welburn | All media decay / become obsolete over time. It is therefore necessary to refresh the media by copying the data to new media at intervals. Doing this regularly reduces the risk of discovering that your archived data is inaccessible. |
33 | 5 | Steve Welburn | |
34 | 12 | Steve Welburn | If data is stored on a RAID (Redundant Array of Independent Disks), then it is possible to replace an individual disk in the array and rebuild it's content, thus refreshing the media. |
35 | 12 | Steve Welburn | |
36 | 12 | Steve Welburn | Archived data is still at risk of data loss, and should be backed up somewhere else! |
37 | 12 | Steve Welburn | |
38 | 16 | Steve Welburn | Archiving data is best supported through provision of a data archiving service (e.g. through a library). The burden of maintaining archival standards of storage for the media is then taken on by the service provider. This may appear to the user as a network drive, or as an archive system to which data packages may be submitted. Such a system may be part of a data management system which also supports publication of data. |
39 | 16 | Steve Welburn | |
40 | 3 | Steve Welburn | h2. File Formats |
41 | 4 | Steve Welburn | |
42 | 10 | Steve Welburn | File formats also become obsolete. Although the original data should be archived, it is also recommended that copies of data are stored in more accessible formats. e.g. storing PDF outputs from LaTeX source, TIFF versions of images, FLAC copies of audio files. The more specific the source format the stronger the requirement for readable formats! Closed formats (e.g. Microsoft Word documents) are particularly vulnerable to obsolescence - e.g. if you change the application you use from MS Word to Open Office, even if the document can be opened you may find that the formatting no longer works without purchasing MS Office. |
43 | 8 | Steve Welburn | |
44 | 1 | Steve Welburn | * LaTeX source - will all the required packages be available if you want to rebuild the document ? |
45 | 13 | Steve Welburn | * Images - will the format be available ? is it a closed format (e.g. GIF) ? |
46 | 13 | Steve Welburn | |
47 | 13 | Steve Welburn | If data is stored in lossy formats (e.g. MP3) then future decoders for that format may not produce precisely the same output (audio) as the decoder used in the initial experiments. A copy of the data should always include a lossless version of the data (e.g. PCM or FLAC for audio). Preferably, research should take place on lossless data extracted from the lossy files. |
48 | 1 | Steve Welburn | |
49 | 22 | Steve Welburn | In the future, current audio formats may become obsolete, we therefore recommend that when archiving audio files, copies of the data should be stored in an open lossless format as well as in the original format. We would currently recommend using "FLAC":http://flac.sourceforge.net/ to compress audio files - FLAC files use less space than the raw data and allow metadata tags to be included (e.g. artist and track name). If the use of compressed files is not appropriate we would recommend use of uncompressed PCM audio in WAV format. |
50 | 9 | Steve Welburn | |
51 | 9 | Steve Welburn | h2. Summary |
52 | 9 | Steve Welburn | |
53 | 9 | Steve Welburn | Archiving data requires: |
54 | 9 | Steve Welburn | * refreshing the media at suitable intervals by moving data onto new media |
55 | 9 | Steve Welburn | * creating copies of the data in new formats to allow their use (e.g. converting data in closed formats to open formats, updating data to new versions of file formats). |