{tip:title=Preparing to Attend}
This page provides a quick checklist of preparation items to consider before joining us at the hackathons in Copenhagen and Chapel Hill. Please be prepared to take part, this is an interactive and inclusive event\!
{tip}
# *Participation in the hackathon activities is mandatory: observers are not allowed\! So it's important to consider what role you would like to play at the event. There are 2 options, and it's worth noting that you can wear more than one hat if so desired:*
## *Practitioner :* you will bring digital data representing an example of a real preservation issue and champion it throughout the event. We will team you up with other experts to develop solutions for your content. You do not need technical skills, and we'll provide all the support you require, in a friendly and welcoming workshop environment
## *Developer :* you will come armed with your best coding, scripting, command line, or geek skills and will be teamed up with practitioners who set and describe your challenges. You will brainstorm, problem solve and troubleshoot with the support of other developers and our experts.
# *If you are playing the part of a Practitioner, you will need to bring with you a collection sample:*
## *This would ideally be*
Disk images containing sample data that is representative of a real preservation challenge at your organisation.
## *Please refrain from bringing*
Physical media, Hard Drives are not the most robust items in the world, as anyone who's dropped a laptop probably knows.
Your only copy of anything
# *OPF Hackathon event results will be captured on the OPF git repository and wiki. If you want you can* *[sign up for these in advance|SPR:Sign up for Github and the Wiki]**.*
# *Remember to bring your laptop\! You must have one for the event\! Please make sure you have installed:*
## [Firefox | http://www.mozilla.org] or [Chrome | https://www.google.com/intl/en_uk/chrome/browser/?hl=en-GB], IE does not always play nicely with our Wiki.
## [VirtualBox | https://www.virtualbox.org/] to host the [BitCurator | http://www.bitcurator.net/aboutbc/] virtual machine.
## Developers, please bring your development weapons of choice, i.e. compilers, IDEs, etc.
# *Dress code: casual. We're all friends here, or at least will be by Day 3\!*
h3.Advance Reading
{info:title=Just for the curious, it's not required reading}
This list will be added to in the lead up to the event so do check back.
{info}
* The [FIDO project|http://fido.cerch.kcl.ac.uk/] investigated the application of forensic techniques to a working Higher Education archive's practises. The [project report page | http://fido.cerch.kcl.ac.uk/fido-reports/] holds publications covering various forensic tools and techniques. The [final project report | http://fido.cerch.kcl.ac.uk/wp-uploads/2012/12/FIDO-Final-Report_v12.pdf] gives an overview of the project and details its conclusions.
* [The Forensic Curator | http://ijdc.net/index.php/ijdc/article/view/218] is a DLIB article that gives a detailed overview of forensic techniques and their application to digital preservation.
* The [BitCurator site's nice related resources section | http://www.bitcurator.net/related-resources-2] has plenty of further reading, [Digital Forensics and Born-Digital Content in Cultural Heritage Collections | http://www.clir.org/pubs/abstract/reports/pub149] is not for the faint hearted (it's long) but covers the subject in some detail.
This page provides a quick checklist of preparation items to consider before joining us at the hackathons in Copenhagen and Chapel Hill. Please be prepared to take part, this is an interactive and inclusive event\!
{tip}
# *Participation in the hackathon activities is mandatory: observers are not allowed\! So it's important to consider what role you would like to play at the event. There are 2 options, and it's worth noting that you can wear more than one hat if so desired:*
## *Practitioner :* you will bring digital data representing an example of a real preservation issue and champion it throughout the event. We will team you up with other experts to develop solutions for your content. You do not need technical skills, and we'll provide all the support you require, in a friendly and welcoming workshop environment
## *Developer :* you will come armed with your best coding, scripting, command line, or geek skills and will be teamed up with practitioners who set and describe your challenges. You will brainstorm, problem solve and troubleshoot with the support of other developers and our experts.
# *If you are playing the part of a Practitioner, you will need to bring with you a collection sample:*
## *This would ideally be*
Disk images containing sample data that is representative of a real preservation challenge at your organisation.
## *Please refrain from bringing*
Physical media, Hard Drives are not the most robust items in the world, as anyone who's dropped a laptop probably knows.
Your only copy of anything
# *OPF Hackathon event results will be captured on the OPF git repository and wiki. If you want you can* *[sign up for these in advance|SPR:Sign up for Github and the Wiki]**.*
# *Remember to bring your laptop\! You must have one for the event\! Please make sure you have installed:*
## [Firefox | http://www.mozilla.org] or [Chrome | https://www.google.com/intl/en_uk/chrome/browser/?hl=en-GB], IE does not always play nicely with our Wiki.
## [VirtualBox | https://www.virtualbox.org/] to host the [BitCurator | http://www.bitcurator.net/aboutbc/] virtual machine.
## Developers, please bring your development weapons of choice, i.e. compilers, IDEs, etc.
# *Dress code: casual. We're all friends here, or at least will be by Day 3\!*
h3.Advance Reading
{info:title=Just for the curious, it's not required reading}
This list will be added to in the lead up to the event so do check back.
{info}
* The [FIDO project|http://fido.cerch.kcl.ac.uk/] investigated the application of forensic techniques to a working Higher Education archive's practises. The [project report page | http://fido.cerch.kcl.ac.uk/fido-reports/] holds publications covering various forensic tools and techniques. The [final project report | http://fido.cerch.kcl.ac.uk/wp-uploads/2012/12/FIDO-Final-Report_v12.pdf] gives an overview of the project and details its conclusions.
* [The Forensic Curator | http://ijdc.net/index.php/ijdc/article/view/218] is a DLIB article that gives a detailed overview of forensic techniques and their application to digital preservation.
* The [BitCurator site's nice related resources section | http://www.bitcurator.net/related-resources-2] has plenty of further reading, [Digital Forensics and Born-Digital Content in Cultural Heritage Collections | http://www.clir.org/pubs/abstract/reports/pub149] is not for the faint hearted (it's long) but covers the subject in some detail.