RecordsDNA is part of a one-year multidisciplinary international research network on the DNA of digital records. We are bringing people together from different disciplines to gather perspectives on their needs for the future digital evidence base and to try to reconceptualise a digital record in terms of its components (DNA), and identify a future global research agenda.
To do this we need YOUR help!
We are holding a series of wiki surveys to crowdsource and rank concerns with managing the digital record base. This mechanism creates long lists in a prioritized order for our further consideration. Each survey will be open for a small number of days so please log in and add your ideas. The first, asking ‘What are the risks to maintaining digital evidence over time?’ The survey is at:
The survey does keep comparing the choices so you can keep scrolling through your rankings for some time. Do not feel you must get to the end but ranking even some of the choices and priorities is helpful. If you would like to add a longer response to this challenging question feel free to post and share your answer on this listserv. We are going to try to crowdsource some of the issues. Join the discussion/debate and help to influence the future research and development agenda
The anchor for this work is our blog https://recorddna.wordpress.com/ and you can follow us on Twitter @RecordDNA ( https://twitter.com/RecordDNA ). The hashtag is #RecordDNA
Thanks for all your help – pass this on far and wide please!
[log in to unmask]
University College London
All archives of messages are stored permanently and are
available to the world wide web community at large at
If you wish to leave this list please send the command
leave data-protection to [log in to unmask]
All user commands can be found at https://www.jiscmail.ac.uk/help/subscribers/subscribercommands.html
Any queries about sending or receiving messages please send to the list owner
[log in to unmask]
Full help Desk - please email [log in to unmask] describing your needs
To receive these emails in HTML format send the command:
SET data-protection HTML to [log in to unmask]
(all commands go to [log in to unmask] not the list please)