Sound Data Management Training » History » Version 34

Steve Welburn, 2012-07-30 03:20 PM

1 5 Steve Welburn
h1. WP1.2 Online Training Material
2 1 Steve Welburn
3 7 Steve Welburn
(back to [[Wiki]])
4 7 Steve Welburn
5 9 Steve Welburn
{{>toc}}
6 9 Steve Welburn
7 28 Steve Welburn
h2. By Stage Of Research
8 28 Steve Welburn
9 34 Steve Welburn
h3. Before Research - Planning Research Data Management
10 28 Steve Welburn
11 32 Steve Welburn
It is likely that some form of data management plan will be required as part of a grant proposal. The data management plan is an opportunity to think about the resources that will be required during the lifetime of the research project and to make sure that any necessary resources can be funded through the project.
12 32 Steve Welburn
13 32 Steve Welburn
The main three questions the plan will cover are:
14 1 Steve Welburn
* What type of storage do you require ?
15 34 Steve Welburn
Do you need a lot of local disk space to store copies of standard datasets ? Will you be creating data which should be deposited in a long-term archive, or published online ? How will you back up your data ?
16 1 Steve Welburn
* How much storage do you require ?
17 34 Steve Welburn
Does it fit within the standard allocation for backed-up storage ?
18 1 Steve Welburn
* How long will you require the storage for ?
19 34 Steve Welburn
Is data If data is being archived or published
20 32 Steve Welburn
21 1 Steve Welburn
Appropriate answers will relate to: the types of data you will be using and creating; available existing resources; funder requirements; and relevant policies (e.g. research group, institutional).
22 34 Steve Welburn
23 34 Steve Welburn
It is likely that actual requirements will differ from initial estimates. Reviewing the data management plan against actual data use will allow you to assess whether additional resources are required.
24 28 Steve Welburn
25 28 Steve Welburn
h3. During Research
26 28 Steve Welburn
27 31 Steve Welburn
During the course of a piece of research, dat management is largely risk mitigation - it makes your research more robust and allows you to continue if something goes wrong.
28 31 Steve Welburn
29 31 Steve Welburn
The two main areas to consider are:
30 31 Steve Welburn
* backing up research data - in case you lose, or corrupt, the main copy of your data;
31 31 Steve Welburn
* documenting data - in case you need to to return to it later.
32 28 Steve Welburn
33 28 Steve Welburn
h3. At The End Of A Piece of Research
34 28 Steve Welburn
35 28 Steve Welburn
(Includes on publication of a paper based on your research)
36 28 Steve Welburn
37 28 Steve Welburn
* Archiving research data
38 28 Steve Welburn
* Publishing research data
39 30 Steve Welburn
* Reviewing the data management plan
40 28 Steve Welburn
41 29 Steve Welburn
h2. Researcher use cases
42 1 Steve Welburn
43 29 Steve Welburn
h3. Quantitative research
44 1 Steve Welburn
45 1 Steve Welburn
bq. A common use-case in C4DM research is to run a newly-developed analysis algorithm on a set of audio examples and evaluate the algorithm by comparing its output with that of a human annotator. Results are then compared with published results using the same input data to determine whether the newly proposed approach makes any improvement on the state of the art.
46 1 Steve Welburn
47 29 Steve Welburn
There are two main types of quantitative research which we consider:
48 29 Steve Welburn
* Testing new data using existing algorithms
49 29 Steve Welburn
* Using existing data, and algoritghms, to test a new algorithm.
50 26 Steve Welburn
51 1 Steve Welburn
Data involved includes:
52 1 Steve Welburn
* Software for the algorithm (which can be hosted on "Sound Software":http://www.soundsoftware.ac.uk)
53 1 Steve Welburn
* An annotated dataset against which the algorithm can be tested
54 1 Steve Welburn
* Results of applying the new algorithm and competing algorithms to the dataset
55 1 Steve Welburn
* Documentation of the testing methodology
56 1 Steve Welburn
57 22 Steve Welburn
Note that *if* other algorithms have published results using the same dataset and methodology, then results should be directly comparable between the published results and the results for the new algorithm. In this case, most of the methodology is already documented and only details specific to the new algorithm (e.g. parameters) need separately recording.
58 1 Steve Welburn
59 23 Steve Welburn
Also, if the testing is scripted, then the code used would be sufficient documentation during the research - readable documentation only being required at publication.
60 1 Steve Welburn
61 1 Steve Welburn
If no suitable annotated dataset already exists, a new dataset may be created including:
62 12 Steve Welburn
* Selection of underlying (audio) data (the actual audio may be in the dataset or the dataset may reference material - e.g. for [[Copyright|copyright]] reasons)
63 11 Steve Welburn
* Ground-truth annotations for the audio and the type of algorithm (e.g. chord sequences for chord estimation, onset times for onset detection)
64 1 Steve Welburn
65 25 Steve Welburn
h3. Qualitative testing
66 1 Steve Welburn
67 27 Steve Welburn
An example would be using interviews with performers to evaluate a new instrument design.
68 1 Steve Welburn
69 24 Steve Welburn
Data involved may include:
70 24 Steve Welburn
* the interface design
71 24 Steve Welburn
* Captured audio from performances
72 24 Steve Welburn
* Recorded interviews with performers (possibly audio or video)
73 24 Steve Welburn
* Interview transcripts
74 1 Steve Welburn
75 24 Steve Welburn
The research may also involve:
76 1 Steve Welburn
* Demographic details of participants
77 3 Steve Welburn
* Identifiable participants (Data Protection])
78 24 Steve Welburn
* Release forms for people taking part
79 1 Steve Welburn
80 1 Steve Welburn
and *will* involve:
81 1 Steve Welburn
* ethics-board approval
82 1 Steve Welburn
83 1 Steve Welburn
h3. Publication
84 1 Steve Welburn
85 1 Steve Welburn
Additionally, publication of results will require:
86 1 Steve Welburn
* Summarising the results
87 1 Steve Welburn
* Publishing the paper
88 8 Steve Welburn
89 17 Steve Welburn
Note that the EPSRC data management principles require sources of data to be referenced.
90 17 Steve Welburn
91 15 Steve Welburn
h3. Primary Investigator (PI)
92 14 Steve Welburn
93 14 Steve Welburn
The data management concerns of a PI will largely revolve around planning and appraisal of data management for research projects.
94 14 Steve Welburn
95 14 Steve Welburn
Areas of interest may involve:
96 14 Steve Welburn
* legalities (Freedom of Information, Copyright and Data Protection)
97 14 Steve Welburn
* data management plan
98 14 Steve Welburn
** covering the research council requirements
99 14 Steve Welburn
** during the project
100 14 Steve Welburn
** data archiving
101 14 Steve Welburn
** data publication
102 14 Steve Welburn
* After the project is completed, an appraisal of how the data was managed should be carried out as part of the project's "lessons learned"
103 14 Steve Welburn
104 16 Steve Welburn
Data management training should provide an overview of all the above, and keep PIs informed of any changes in the above that affect data management requirements.
105 16 Steve Welburn
106 19 Steve Welburn
The DCC DMP Online tool provides a series of questions which allow the user to build a data management plan which will match research council requirements.
107 18 Steve Welburn
108 8 Steve Welburn
h2. Overarching concerns
109 8 Steve Welburn
110 8 Steve Welburn
Human participation - ethics, data protection
111 8 Steve Welburn
112 8 Steve Welburn
Audio data - copyright
113 10 Steve Welburn
114 10 Steve Welburn
Storage - where ? how ? SLA ?
115 20 Steve Welburn
116 21 Steve Welburn
Short-term resilient storage for work-in-progress
117 20 Steve Welburn
118 21 Steve Welburn
Long-term archival storage for research data outputs
119 1 Steve Welburn
120 1 Steve Welburn
Curation of archived data - refreshing media and formats
121 21 Steve Welburn
122 21 Steve Welburn
Drivers - FoI, RCUK