Editing User:Andy Jackson/DigiPresHack

Jump to navigation Jump to search

User account "Andy Jackson" is not registered. Please check if you want to create/edit this page.

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Latest revision Your text
Line 1: Line 1:
= Introduction =
+
== DigiPresHack Outline Proposal==
The idea behind DigiPresHack is to have recurring events in hackathon style where we build up the information we need to do digital preservation better. These could be regular fixtures alongside conferences (iPres, IIPC GA, IDCC, etc.) but would also have a strong remote-participation element. There would be three main outcomes:
+
 
 +
The idea is to have recurring events in hackathon style where we build up the information we need to do digital preservation better. These could be regular fixtures alongside conferences (iPres, IIPC GA, IDCC, etc.) but would also have a strong remote-participation element. There would be three main outcomes:
  
 
* More information documenting more formats, risks and other preservation issues.
 
* More information documenting more formats, risks and other preservation issues.
Line 8: Line 9:
 
i.e. there would always be an educational/introductory strange to help people learn about the issues and learn how to contribute to the registries/data sources.
 
i.e. there would always be an educational/introductory strange to help people learn about the issues and learn how to contribute to the registries/data sources.
  
= Potential Events =
+
== Potential Strands ==
 
 
* [[User:Andy_Jackson/DigiPresHack@IIPC-GA-2015|DigiPresHack@IIPC-GA-2015]]
 
 
 
 
 
= Potential Strands =
 
  
== Introductory Track ==
+
=== Introductory Track ===
  
 
These are tasks that only require basic technical skills and a willingness to learn how to document their findings. We would perform basic tasks where we create test files and check how they are rendered.
 
These are tasks that only require basic technical skills and a willingness to learn how to document their findings. We would perform basic tasks where we create test files and check how they are rendered.
Line 29: Line 25:
 
Goal is to better understand formats and software dependencies and document genuine preservation risks.
 
Goal is to better understand formats and software dependencies and document genuine preservation risks.
  
== Technical Track ==
+
=== Technical Track ===
  
 
Improving tools, making new ID signatures in forms suitable for PRONOM etc.
 
Improving tools, making new ID signatures in forms suitable for PRONOM etc.

Please note that all contributions to COPTR are considered to be released under the Attribution-ShareAlike 3.0 Unported (see COPTR:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)