Difference between revisions of "Case Study Committee Workplan"
From COST Action FP0804: FORSYS
SeanGordon (Talk | contribs) m |
SeanGordon (Talk | contribs) |
||
| Line 2: | Line 2: | ||
[[category:Meeting Nov 2011]] | [[category:Meeting Nov 2011]] | ||
<div style="float:right;">__TOC__</div> | <div style="float:right;">__TOC__</div> | ||
| + | |||
| + | ===Timeline=== | ||
| + | * 18th November 2011 – FORSYS participants submit STSM opportunities to wiki | ||
| + | * 1st February 2012 – FORSYS participants submit case study (CS) abstracts to CS technical committee (CSTC) | ||
| + | * 1st March – CSTC provides reporting format for CS | ||
| + | * 1st March - CSTC responds to abstracts | ||
| + | * 1st June - CSTC follow up on cases | ||
| + | * 1st September – FORSYS participants submit first draft of CS to CSTC | ||
| + | * 1st October – CSTC responds to drafts | ||
| + | * 1st November – FORSYS participants submit final CS | ||
| + | * 20th December 2012 – CSTC synthesis | ||
| + | * 2013 CS synthesis informs development of FORSYS guidelines | ||
| + | * technically have until 3 months after end of project (4/2013) to complete all project work | ||
==Develop case study guidelines== | ==Develop case study guidelines== | ||
| − | |||
* Figure out how cases will contribute to final Forsys guidelines | * Figure out how cases will contribute to final Forsys guidelines | ||
* E-mail Forsys participants about important guidelines updates | * E-mail Forsys participants about important guidelines updates | ||
| Line 23: | Line 35: | ||
==DONE== | ==DONE== | ||
| + | ===After the Leuven 2011 meeting=== | ||
| + | * Synthesize Leuven discussion and update [[Case Study Guidelines]] on the wiki | ||
| + | * Developed semantic wiki form for STSMs | ||
| + | |||
===Before the Leuven 2011 meeting=== | ===Before the Leuven 2011 meeting=== | ||
*Develop two (or more) documents: | *Develop two (or more) documents: | ||
Revision as of 03:11, 11 January 2012
Timeline
- 18th November 2011 – FORSYS participants submit STSM opportunities to wiki
- 1st February 2012 – FORSYS participants submit case study (CS) abstracts to CS technical committee (CSTC)
- 1st March – CSTC provides reporting format for CS
- 1st March - CSTC responds to abstracts
- 1st June - CSTC follow up on cases
- 1st September – FORSYS participants submit first draft of CS to CSTC
- 1st October – CSTC responds to drafts
- 1st November – FORSYS participants submit final CS
- 20th December 2012 – CSTC synthesis
- 2013 CS synthesis informs development of FORSYS guidelines
- technically have until 3 months after end of project (4/2013) to complete all project work
Develop case study guidelines
- Figure out how cases will contribute to final Forsys guidelines
- E-mail Forsys participants about important guidelines updates
Manage case study contributions
- Develop semantic form for entering case studies into the wiki
- Solicit case studies from the Forsys network
- Review and comment on case studies submitted
- Answer questions, resolve issues
Case study literature database
- Investigate possible technologies for managing/sharing case study literature
Publications
- Think of publication possibilities for case study work
DONE
After the Leuven 2011 meeting
- Synthesize Leuven discussion and update Case Study Guidelines on the wiki
- Developed semantic wiki form for STSMs
Before the Leuven 2011 meeting
- Develop two (or more) documents:
- Case Study Notes by Research Phase: organize information already generated about the case study guidelines
- 2011-11_Leuven_Case_Study_Agenda
- Gather further information on case studies (STC sends request to country representatives)
- Existing forest DSS case studies
- Potential forest DSS case studies
- Other relevant literature (methods, theories, etc)
At Leuven 2011 meeting
- Give case study introductory presentation
- Each STC member leads a subgroup on assigned task
- Develop & present a time line for the work on the case studies
- incl. meeting of the STC
- incl. clear division of responsibilities
