Difference between revisions of "Case Study Committee Workplan"
From COST Action FP0804: FORSYS
SeanGordon (Talk | contribs) m |
SeanGordon (Talk | contribs) m |
||
Line 4: | Line 4: | ||
==Develop case study guidelines== | ==Develop case study guidelines== | ||
− | * Synthesize Leuven discussion and update [[ | + | * Synthesize Leuven discussion and update [[Case Study Guidelines]] on the wiki |
* 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 |
Revision as of 19:11, 30 November 2011
Develop case study guidelines
- Synthesize Leuven discussion and update Case Study Guidelines on the wiki
- 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
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