Proposed management of the exchange of research data

1
Proposed management of the exchange of research
data Dr Simon Gardner SKEP ERA-NET
Project Manager
2
Proposed timeline for the exchange of research
data
November 2005 - circulation of draft data
exchange template - circulation of draft
classification framework and associated guidance
December 2005 - Work Package 2 workshop -
Feedback on data-exchange template - Feedback on
classification framework
January 2006 - Refine data-exchange template -
Refine classification framework
Start February 2006 - Consortium members to be
sent a blank database to populate (.mdb .xls)
End February 2006 - Return of exchanged research
Programme and Project level information
3
A questionnaire to allow us to collect basic
information on how environmental research data is
stored by different project participants
4
A proposed list of fields for exchange between
project participants
5
Potential changes to consider to the template for
exchange of data
Should a stakeholders field be added?
In assessing the effectiveness of environmental
research could we use work undertaken under WP3
and WP4 to help produce a SKEP rating?
Is the budgetary information too detailed, or
not detailed enough?
Should a field be added on Reason for
commissioning research?
Should the GeographicalScope field be combined
with use of the classification framework
Location code?
6
(No Transcript)
7
(No Transcript)
8
Proposed timeline for the exchange of research
data
November 2005 - circulation of draft data
exchange template - circulation of draft
classification framework and associated guidance
December 2005 - Work Package 2 workshop -
Feedback on data-exchange template - Feedback on
classification framework
January 2006 - Refine data-exchange template -
Refine classification framework
Start February 2006 - Consortium members to be
sent a blank database to populate (.mdb .xls)
End February 2006 - Return of exchanged research
Programme and Project level information
9
The fields in the data template will form the
basis of a SKEP database which will be populated
in early 2006
10
Proposed timeline for the exchange of research
data
End February 2006 - Return of exchanged research
Programme and Project level information
Mid March 2006 - Research portfolio data
consolidated into a SKEP database - Database
placed on SKEP website - Coding software enabled
on SKEP website
Mid-March - End May 2006 - Remote coding of
research information by project participants
according to SKEP classification framework
End June 2006 - Launch of Knowledge Management
tool on project website
11
Different approaches to coding of exchanged
research information
I. Self-coding by Consortium members
?
Advantages
- autonomy over the presentation of research
activities - intra-organisational consistency in
classification - cost-effective - multiple coders
can work on the organisational database at the
same time
?
Disadvantages
- potential for variations in coding across the
Consortium (different interpretations by
different participants). But, guidance and advice
will be provided.
12
Different approaches to coding of exchanged
research information
II. Coding by the co-ordination team
?
Advantages
- consistency of approach
?
Disadvantages
- costly in terms of time and resources (small
number of people vs. large number of people
coding in parallel) - not budgeted for in the
Description of Work - imperfect access to
information (which may need to be requested
from Consortium members) - diminished autonomy
coding of projects may be at odds to the
perception of project participants
13
(No Transcript)