View Source

The digital preservation community is small and under resourced. This means we have to work together if we want to make a real impact. We're now seeing the emergence of a host of exciting crowd sourced or collaborative projects. Please help yourself and the rest of the community by contributing to these initiatives:

{section}{column:width=10%}
!picture.png!
{column}
{column:width=90%}

h4. Contribute to the Atlas of Digital Damages

Visual examples of digital preservation challenges, such as graphic corruption, can be incredibly useful in communicating the digital preservation message. Barbara Sierman blogged convincingly about the need for a collection of such images. Contributing to this Flickr group is a really easy way to get involved in DP community initiatives. Follow the Atlas on Twitter here [@atlasofdd|https://twitter.com/atlasofdd]. Also see the [story focused Atlas of Digital Damages site|http://www.atlasofdigitaldamages.info] from Barbara Sierman.
{tip}
[Add an image of a digital preservation challenge, failed rendering, encoding damage, corrupt data, or visual evidence documenting to the Atlas of Digital Damages.|http://www.flickr.com/groups/2121762@N23/]{tip}{column}
{section}
{section}{column:width=10%} !noun_project_22.png!
{column}
{column:width=90%}

h4. Join the discussion

Discussion forums and active blogs provide the opportunity to share informal advice, get recommendations and discuss the finer points of digital preservation. By sharing both your intentions for digital preservation work and your results, you can ensure your work benefits from a wealth of community experience.
{tip}
Starting a new piece of work or have a specific challenge to take on? [Share your thoughts and get the views of the community on the OPF site|http://openplanetsfoundation.org/] before you go any further.
{tip}
{tip}
[Join the Digital Curation Google Group to discuss curation and preservation issues.|https://groups.google.com/forum/?fromgroups#!forum/digital-curation]
{tip}
{column}
{section}

{section}{column:width=10%} !noun_project_2248.png!
{column}
{column:width=90%}

h4. Contribute to the Digital Preservation Wikipedia Project

The [Wikipedia pages on digital preservation|http://en.wikipedia.org/wiki/Digital_preservation] could be so much better. Join a new concerted effort led by NDSA to put this right\! Sign up and and start off by checking out the [WikiProject page|http://en.wikipedia.org/wiki/Wikipedia:WikiProject_Digital_Preservation].
{tip}
[Improve the digital preservation pages on Wikipedia|http://en.wikipedia.org/wiki/Wikipedia:WikiProject_Digital_Preservation].
{tip}
{column}
{section}

{section}{column:width=10%} !noun_project_1266.png!
{column}
{column:width=90%}



h4. Contribute to a file format initiative

Everyone knows we need a decent file format registry to support digital preservation activities. But so far most of our registries are pretty empty. Three new initiatives provide a cross section of opportunities for involvement: [CRISP|http://wiki.opf-labs.org/display/SPR/Crowd+sourced+Representation+Information+for+Supporting+Preservation+%28CRISP%29], [Just solve the file format problem|http://www.archiveteam.org/index.php?title=Just_Solve_the_Problem_2012] and [UDFR|http://udfr.org/]. If you'd like to know more, [Andy Jackson expertly describes how these projects relate to each other|http://openplanetsfoundation.org/blogs/2012-07-06-biodiversity-and-registry-ecosystem].

{tip}
[Looking at a web page useful for preserving digital material? Submit it to CRISP so it is web archived and preserved for posterity.|http://wiki.opf-labs.org/display/SPR/Crowd+sourced+Representation+Information+for+Supporting+Preservation+%28CRISP%29]
{tip}

{tip}
[Add a new format risks and solutions page to the OPF wiki|TR:OPF File Format Risk Registry] ([like this excellent JP2 risks page|TR:JP2]).
{tip}


{tip}

[Just solve the File Format Problem: Contribute to the crowd sourced file format information wiki on the Archive Team site|http://justsolve.archiveteam.org].


{tip}


{tip}
[UDFR: Contribute to and refine the contents of this more formal linked data registry on file formats.|http://udfr.org/]
{tip}
{column}
{section}

{section}
{column:width=10%}

!noun_project_1050.png!{column}

{column:width=90%}



h4. Write up your digital preservation needs, and get them solved

Do you have an unsolved digital preservation challenge? Would you like someone to solve it for you? The [Open Planets Foundation wiki|REQ:Digital Preservation and Data Curation Requirements and Solutions] captures information about specific Datasets or digital collections. These link to concrete digital preservation challenges or Issues. Once those Issues have been solved, they are written up as Solutions. Capturing the requirements of preservation practitioners enables developers to target their precious resources more effectively. [Sharing our experiences in solving preservation Issues allows others to learn from the successes (and less successful approaches)|http://openplanetsfoundation.org/blogs/2012-05-17-do-others-share-your-digital-preservation-challenges-and-know-about-best-solutions].


{tip}
[Contribute your preservation challenges and requirements.|REQ:Digital Preservation and Data Curation Requirements and Solutions]
{tip}
{column}
{section}
{section}{column:width=10%}
!noun_project_566.png!{column}

{column:width=90%}

h4. Contribute a new research challenge

Some problems in this field require new tools or approaches that can be developed now. Others require research and experimentation before they can be realised as practical solutions. Enable Computer Science researchers (and other disciplines) to target your research challenge by making a contribution to the DP Research Challenges Wiki. 
{tip}
[Contribute a new research challenge to the DP Research Challenges Wiki.|http://sokrates.ifs.tuwien.ac.at/wiki/index.php/Main_Page]{tip}{column} {section}

{section}
{column:width=10%}
!noun_project_1191.png!{column}
{column:width=90%}



h4. Describe a useful digital preservation tool

Finding toolsets that automate your digital preservation processes and solve your challenges is not easy. Tool registries provide a way of browsing for useful solutions and learning from experiences others have had in applying them. [The COPTR tool registry captures information about tools on an easy to edit wiki|http://coptr.digipres.org/].

{tip}
Contribute[ a short description of a useful tool for digital preservation.|http://coptr.digipres.org/]
{tip}
{column}
{section}
{section}{column:width=10%} !noun_project_650.png!
{column}
{column:width=90%}

h4. Share or create digital object samples

Improving our digital preservation toolsets requires careful testing and evaluation of their performance. Sample data enables tool developers to easily try out their tools, discover bugs, and hone their tools ready for others to use. A test corpus can contain real digital objects from a collection, or be created specifically for exhibiting certain characteristics for testing purposes. Real data, particularly with examples of broken, badly formed or corrupted files can be particularly useful. For example, see this [JP2k test corpus|https://github.com/openplanets/format-corpus/tree/master/jp2k-test].
{tip}
Share sample digital objects for a test corpus. [Contribute to the OPF Format Corpus on Gitub|https://github.com/openplanets/format-corpus] or [contribute to the OPF Format Corpus via Google drive|https://docs.google.com/folder/d/0B8ZzGhlaygesdzNfUnB3dkpQN28/edit], with a [guide here on how to contribute|http://wiki.curatecamp.org/index.php/Collecting_format_ID_test_files] or [contact OPF|http://openplanetsfoundation.org/contact] for help on how to get involved.{tip}{column}
{section}

{section}{column:width=10%}
!noun_project_872.png!{column}
{column:width=90%}

h4. Analyse, share your data, evaluate and improve

In order to improve our digital preservation capability, we need to be able to analyse and evaluate our work in an effective manner. For example, we need to be able to compare and contrast tools and approaches, and we need to see how changes over time affect performance. Practising what we preach in this field means sharing our data about digital preservation. [Dave Tarrant explains why this is a good idea|http://openplanetsfoundation.org/blogs/2012-08-29-years-registry-why-has-preservation-community-not-solved-problem-well-managed-and].
{tip}
[Share your digital preservation data using the Linked Data Simple Storage Specification|http://www.lds3.org/]{tip}{column}{section}
{section}{column:width=10%}

!noun_project_2038.png!{column}
{column:width=90%}

h4. Improve file format identification

Identifying file formats is the bread and butter of digital preservation characterisation and assessment. Identification tool coverage and accuracy could be much better, and this primarily comes down to the signatures used to identify each format.

{tip}

[Submit a file format signature/patch to Apache Tika|https://issues.apache.org/jira/browse/TIKA] ([like this one|http://openplanetsfoundation.org/blogs/2012-02-09-basic-guide-writing-new-format-signatures]).
{tip}

{tip}

[Contribute a file format signature to DROID|http://www.nationalarchives.gov.uk/PRONOM/submitinfo.htm] ([see this guide|http://openplanetsfoundation.org/blogs/2012-02-09-basic-guide-writing-new-format-signatures] and [this official guide|http://www.nationalarchives.gov.uk/documents/information-management/pronom-file-signature-research.pdf]).
{tip}{tip}

[Contribute a file format signature to FILE|https://github.com/glensc/file] ([see this guide|http://www.openplanetsfoundation.org/blogs/2012-08-09-magic-editing-and-creation-primer]).
{tip}
{column}
{section}
{section}
{column:width=10%}
!noun_project_1330.png!
{column}
{column:width=90%}

h4. Enhance deep file characterisation

Deep file characterisation enables validation, identification of preservation risks and extraction of metadata. In developing a new characterisation capability, begin with thorough research to identify existing code to re-use or build on, develop a focused command line tool, then consider turning it into a JHOVE2 module.
{tip}
Develop a new file characterisation capability and turn it into a [JHOVE2 module|https://bitbucket.org/jhove2/main/wiki/Home].
{tip}
{column}
{section}
_All images sourced from the_ _[Noun Project|http://thenounproject.com/]__, including: Question image by Henry Ryder, Swiss Army Knife image by Olivier Guin, Add folder image by Sergio Calcara, People image by T. Weber, Cross hairs image by \__Lo.\_ and chain image by Adam Whitcroft._