Resources For Learning Materials » History » Version 25
Steve Welburn, 2012-06-12 02:13 PM
1 | 2 | Steve Welburn | h1. Why do Data Management ? |
---|---|---|---|
2 | 1 | Steve Welburn | |
3 | 2 | Steve Welburn | h2. Disaster recovery |
4 | 1 | Steve Welburn | |
5 | 1 | Steve Welburn | h3. Disk Drives Break |
6 | 1 | Steve Welburn | |
7 | 1 | Steve Welburn | "DataCent collection of disk drive failure sounds":http://datacent.com/hard_drive_sounds.php |
8 | 1 | Steve Welburn | |
9 | 1 | Steve Welburn | h3. Buildings burn down |
10 | 1 | Steve Welburn | |
11 | 1 | Steve Welburn | "Southampton University Mountbatten Building Fire":http://www.flickr.com/search/?q=Southampton%20University%20Mountbatten%20Building%20Fire |
12 | 1 | Steve Welburn | |
13 | 5 | Steve Welburn | h3. Laptops Break / Get Broken |
14 | 1 | Steve Welburn | |
15 | 1 | Steve Welburn | "Shot laptop":http://lilysussman.wordpress.com/tag/laptop-destroyed/ |
16 | 2 | Steve Welburn | |
17 | 2 | Steve Welburn | h2. Data Reuse |
18 | 2 | Steve Welburn | |
19 | 2 | Steve Welburn | Do you reuse other people's data ? Can they reuse your's ? |
20 | 3 | Steve Welburn | |
21 | 6 | Steve Welburn | h1. Researcher Development Framework |
22 | 6 | Steve Welburn | |
23 | 6 | Steve Welburn | "SCONUL Information Literacy 7 Pillars Diagrams":http://www.sconul.ac.uk/groups/information_literacy/diagrams.html |
24 | 6 | Steve Welburn | |
25 | 3 | Steve Welburn | h1. Licensing |
26 | 3 | Steve Welburn | |
27 | 7 | Steve Welburn | Whose data is it anyway ? |
28 | 7 | Steve Welburn | |
29 | 22 | Steve Welburn | QMUL HR Contract "Terms and Conditions":http://www.hr.qmul.ac.uk/policy/contracts/tandcs/index.html : |
30 | 20 | Steve Welburn | > 16. Patents & Copyright |
31 | 20 | Steve Welburn | > a) Any discovery, design, computer software program or other work or invention which might reasonably be exploitable (‘Invention’) which is discovered, invented or created by the Employee (either alone or with any other person) either directly or indirectly in the course of their normal duties or in the course of duties specifically assigned to him in the course of his employment shall promptly be disclosed in writing to the College. All intellectual property rights in such Invention shall be the absolute property of the College and the College shall have the right to apply for, prosecute and obtain patent or other similar protection in its own name. Intellectual property rights include all patent rights, copyright and rights in respect of confidential information and know-how. The ownership of copyright in research papers, review articles and books will normally be waived by the College in favour of the author unless subject to any conditions placed on the works by the funder. |
32 | 20 | Steve Welburn | |
33 | 20 | Steve Welburn | The important bit being... |
34 | 21 | Steve Welburn | > Any ... work ... which might reasonably be exploitable ... which is ... created by the Employee ... in the course of duties ... in the course of his employment ... shall be the absolute property of the College |
35 | 20 | Steve Welburn | |
36 | 23 | Steve Welburn | In the research contract, there is another clause: |
37 | 23 | Steve Welburn | > The Employee will be expected to publish the results of his/her research work, subject to the conditions of any contract providing funding for the research |
38 | 23 | Steve Welburn | |
39 | 23 | Steve Welburn | Therefore *if* funding bodies make funding contingent on publishing data as part of the results of research, then data publication will be allowed. |
40 | 23 | Steve Welburn | |
41 | 11 | Steve Welburn | Research policies at QMUL "Academic Registry and Council Secretariat":http://www.arcs.qmul.ac.uk/policy_zone/index.html |
42 | 11 | Steve Welburn | |
43 | 15 | Steve Welburn | 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 |
44 | 14 | Steve Welburn | |
45 | 14 | Steve Welburn | Science Commons: http://sciencecommons.org/projects/publishing/open-access-data-protocol/ |
46 | 7 | Steve Welburn | |
47 | 8 | Steve Welburn | Restrictions based on data ownership |
48 | 7 | Steve Welburn | |
49 | 7 | Steve Welburn | Restrictions based on data parentage - use of e.g. CC-SA data |
50 | 4 | Steve Welburn | |
51 | 19 | Steve Welburn | Article on "CC-BY and data":http://bibwild.wordpress.com/2011/01/25/implications-of-cc-by-on-data/ |
52 | 19 | Steve Welburn | |
53 | 16 | Steve Welburn | 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/) |
54 | 13 | Steve Welburn | |
55 | 18 | Steve Welburn | 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 chord annnotations being published commercially). |
56 | 17 | Steve Welburn | |
57 | 12 | Steve Welburn | h1. Practical Steps Towards Data Management |
58 | 12 | Steve Welburn | |
59 | 25 | Steve Welburn | Even if you don't have a readily available data repository, there are still steps you can take to manage your data even if it can't be published. |
60 | 25 | Steve Welburn | |
61 | 12 | Steve Welburn | File formats - use open formats where possible to future-proof files. |
62 | 12 | Steve Welburn | |
63 | 12 | Steve Welburn | File naming - give files meaningful names. |
64 | 12 | Steve Welburn | |
65 | 12 | Steve Welburn | Metadata - include a plain-text README file describing the contents of the files. |
66 | 12 | Steve Welburn | |
67 | 12 | Steve Welburn | License - include a plain-text LICENSE file describing the license for the dataset. |
68 | 12 | Steve Welburn | |
69 | 12 | Steve Welburn | 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. |
70 | 25 | Steve Welburn | |
71 | 25 | Steve Welburn | If you're really bothered about recovering your data make sure it's backed up off-site! |
72 | 25 | Steve Welburn | |
73 | 25 | Steve Welburn | This could be (i) in the cloud (i.e. DropBox etc.); (ii) USB drive (hard/flash); (iii) a specific network location (e.g. a NAS box at home). |
74 | 12 | Steve Welburn | |
75 | 3 | Steve Welburn | h1. Repositories |
76 | 4 | Steve Welburn | |
77 | 4 | Steve Welburn | The appropriate repository will partly depend upon the data. |
78 | 4 | Steve Welburn | |
79 | 24 | Steve Welburn | It could be... C4DM RDR, Dryad, Flickr, figshare, Archiv.Org... |
80 | 4 | Steve Welburn | |
81 | 4 | Steve Welburn | 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... |
82 | 9 | Steve Welburn | |
83 | 9 | Steve Welburn | h1. Open Source Learning Tools |
84 | 10 | Steve Welburn | |
85 | 10 | Steve Welburn | "Xerte":http://www.nottingham.ac.uk/xerte/index.htm |