Resources For Learning Materials » History » Version 17
Version 16 (Steve Welburn, 2012-06-11 03:31 PM) → Version 17/30 (Steve Welburn, 2012-06-11 03:34 PM)
h1. Why do Data Management ?
h2. Disaster recovery
h3. Disk Drives Break
"DataCent collection of disk drive failure sounds":http://datacent.com/hard_drive_sounds.php
h3. Buildings burn down
"Southampton University Mountbatten Building Fire":http://www.flickr.com/search/?q=Southampton%20University%20Mountbatten%20Building%20Fire
h3. Laptops Break / Get Broken
"Shot laptop":http://lilysussman.wordpress.com/tag/laptop-destroyed/
h2. Data Reuse
Do you reuse other people's data ? Can they reuse your's ?
h1. Researcher Development Framework
"SCONUL Information Literacy 7 Pillars Diagrams":http://www.sconul.ac.uk/groups/information_literacy/diagrams.html
h1. Licensing
Whose data is it anyway ?
Research policies at QMUL "Academic Registry and Council Secretariat":http://www.arcs.qmul.ac.uk/policy_zone/index.html
Creative Commons: http://wiki.creativecommons.org/Data "CC Licenses":http://wiki.creativecommons.org/Data_and_CC_licenses / "CC0":http://wiki.creativecommons.org/CC0_use_for_data
Science Commons: http://sciencecommons.org/projects/publishing/open-access-data-protocol/
Restrictions based on data ownership
Restrictions based on data parentage - use of e.g. CC-SA data
Where possible, CC0 with a request for citations is preferred ("Why does Dyad use CC0":http://blog.datadryad.org/2011/10/05/why-does-dryad-use-cc0/)
If data is based on copyright works it may be appropriate to restrict the license to allow only research / non-commercial use (e.g. this would prevent Beatles chord annnotations being published commercially).
h1. Practical Steps Towards Data Management
File formats - use open formats where possible to future-proof files.
File naming - give files meaningful names.
Metadata - include a plain-text README file describing the contents of the files.
License - include a plain-text LICENSE file describing the license for the dataset.
Check that a copy of your data will be backed up - e.g. check that the network drive you store your data on is actually backed up.
h1. Repositories
The appropriate repository will partly depend upon the data.
It could be... C4DM RDR, Dryad, Flick, Archiv.Org...
However, if you want data to be reused in a citable manner remember to package the license and the *required citation* with the data. It means that however the data reaches the final user the only excuse for not being able to cite the data is that someone has bothered to remove the info...
h1. Open Source Learning Tools
"Xerte":http://www.nottingham.ac.uk/xerte/index.htm
h2. Disaster recovery
h3. Disk Drives Break
"DataCent collection of disk drive failure sounds":http://datacent.com/hard_drive_sounds.php
h3. Buildings burn down
"Southampton University Mountbatten Building Fire":http://www.flickr.com/search/?q=Southampton%20University%20Mountbatten%20Building%20Fire
h3. Laptops Break / Get Broken
"Shot laptop":http://lilysussman.wordpress.com/tag/laptop-destroyed/
h2. Data Reuse
Do you reuse other people's data ? Can they reuse your's ?
h1. Researcher Development Framework
"SCONUL Information Literacy 7 Pillars Diagrams":http://www.sconul.ac.uk/groups/information_literacy/diagrams.html
h1. Licensing
Whose data is it anyway ?
Research policies at QMUL "Academic Registry and Council Secretariat":http://www.arcs.qmul.ac.uk/policy_zone/index.html
Creative Commons: http://wiki.creativecommons.org/Data "CC Licenses":http://wiki.creativecommons.org/Data_and_CC_licenses / "CC0":http://wiki.creativecommons.org/CC0_use_for_data
Science Commons: http://sciencecommons.org/projects/publishing/open-access-data-protocol/
Restrictions based on data ownership
Restrictions based on data parentage - use of e.g. CC-SA data
Where possible, CC0 with a request for citations is preferred ("Why does Dyad use CC0":http://blog.datadryad.org/2011/10/05/why-does-dryad-use-cc0/)
If data is based on copyright works it may be appropriate to restrict the license to allow only research / non-commercial use (e.g. this would prevent Beatles chord annnotations being published commercially).
h1. Practical Steps Towards Data Management
File formats - use open formats where possible to future-proof files.
File naming - give files meaningful names.
Metadata - include a plain-text README file describing the contents of the files.
License - include a plain-text LICENSE file describing the license for the dataset.
Check that a copy of your data will be backed up - e.g. check that the network drive you store your data on is actually backed up.
h1. Repositories
The appropriate repository will partly depend upon the data.
It could be... C4DM RDR, Dryad, Flick, Archiv.Org...
However, if you want data to be reused in a citable manner remember to package the license and the *required citation* with the data. It means that however the data reaches the final user the only excuse for not being able to cite the data is that someone has bothered to remove the info...
h1. Open Source Learning Tools
"Xerte":http://www.nottingham.ac.uk/xerte/index.htm