Difference between revisions of "Case Study Committee Workplan"

From COST Action FP0804: FORSYS
Jump to: navigation, search

Warning: require(): Unable to allocate memory for pool. in /data/home/fp0804/www/wiki/includes/AutoLoader.php on line 1191
m
m
 
(8 intermediate revisions by one user not shown)
Line 4: Line 4:
  
 
==Timeline==
 
==Timeline==
* 18th November 2011 FORSYS participants submit STSM opportunities to wiki
+
* 18 November 2011 : FORSYS participants submit STSM opportunities to wiki
* 1st  February 2012 – FORSYS participants submit case study (CS) abstracts to CS technical committee (CSTC)
+
* Mar - Apr 2012 : Case study technical committee (CSTC) develops example cases
* 1st March – CSTC provides reporting format for CS
+
* May (Zvolen meeting) : CSTC reports on progress and coordinates work with other WGs
* 1st March - CSTC responds to abstracts
+
* Sept 2012 : CSTC representatives participate in Wiki Task Force meeting; discuss how to integrate cases into semantic wiki
* 1st June - CSTC follow up on cases  
+
* Oct 2012: CSTC provides develops & tests [[Form:Case study|case input form]] for semantic wiki
* 1st September – FORSYS participants submit first draft of CS to CSTC
+
* Nov 2012: CSTC solicits short cases from Forsys participants
* 1st October – CSTC responds to drafts
+
* Nov 2012 - Jan 2013 : CSTC follow up on potential cases, answer any questions, provide feedback on drafts
* 1st November – FORSYS participants submit final CS
+
* Feb 2013 : CTSC meets to review and synthesize cases for presentation/publication/contributing to FORSYS guidelines
* 20th December 2012 – CSTC synthesis
+
* Mar 2013: CSTC finishes case synthesis article to inform broader FORSYS guidelines
* 2013 CS synthesis informs development of FORSYS guidelines
+
* April 2013 : Selected cases and synthesis presented at Umea conference
* technically have until 3 months after end of project (4/2013) to complete all project work
+
* (technically have until 3 months after end of project (4/2013) to complete all project work)
  
==Develop case study guidelines==
+
==Develop case study examples and guidelines==
 +
* Develop semantic form for entering case studies into 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
 
  
 
==Manage case study contributions==
 
==Manage case study contributions==
* Develop semantic form for entering case studies into the wiki
 
 
* Solicit case studies from the Forsys network
 
* Solicit case studies from the Forsys network
 
* Review and comment on case studies submitted
 
* Review and comment on case studies submitted
 
* Answer questions, resolve issues
 
* Answer questions, resolve issues
  
==Case study literature database==
+
===Use of published literature===
 +
* Assuming institutionalization of the wiki and not of the Cost Action per se, it does not matter whether a forsys member has delivered a case or a case study. Of course it does for the record of the Action, so a separate tag “Forsys member” should do.
 +
* This is a good point. The initial thinking is that these will be stored in different data structures: the wiki for forsys cases and a literature database (maybe Mendeley.com for the literature). However, somehow we would need to link from each to the guidelines they relate to.
 
* Investigate possible technologies for managing/sharing case study literature
 
* Investigate possible technologies for managing/sharing case study literature
 
** e.g. [http://www.mendeley.com/ Mendeley] or [http://www.citeulike.org/ Citeulike]
 
** e.g. [http://www.mendeley.com/ Mendeley] or [http://www.citeulike.org/ Citeulike]
  
==Publications==
+
===Categorization and searching of cases===
* Think of publication possibilities for case study work
+
* The case study semantic form
 +
** tags each case with the general [[:Category:Case]]
 +
** uses the other fields in the case form as tags/categorizies (e.g. Country, Decision phase)
 +
* Cases can be searched/filtered using custom semantic queries or pre-build semantic query pages
 +
 
 +
==Synthesis of cases==
 +
* Synthesis of the cases will focus on their recorded lessons, and how these lessons contribute to the overall FORSYS lessons/guidelines
 +
 
 +
==Sharing results==
 +
* The CTSC is hosting all cases to the FORSYS wiki
 +
* The CSTC has submitted a presentation proposal for the final FORSYS conference in April 2013
 +
* The CSTC has also proposed a case synthesis journal article for the FORSYS conference issue of the Scandinavian Journal of Forest Research
 +
* Other ideas???
  
  
 
==DONE==
 
==DONE==
 
===After the Leuven 2011 meeting===
 
===After the Leuven 2011 meeting===
* Synthesize Leuven discussion and update [[Case Study Guidelines]] on the wiki
+
* Synthesized Leuven discussion and updated [[Case Study Guidelines]] on the wiki
 
* Developed semantic wiki form for [[STSM Opportunities]]
 
* Developed semantic wiki form for [[STSM Opportunities]]
 +
 +
===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
  
 
===Before the Leuven 2011 meeting===
 
===Before the Leuven 2011 meeting===
Line 47: Line 67:
 
** Potential forest DSS case studies  
 
** Potential forest DSS case studies  
 
** Other relevant literature (methods, theories, etc)
 
** 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
 

Latest revision as of 21:16, 18 November 2012

Timeline

  • 18 November 2011 : FORSYS participants submit STSM opportunities to wiki
  • Mar - Apr 2012 : Case study technical committee (CSTC) develops example cases
  • May (Zvolen meeting) : CSTC reports on progress and coordinates work with other WGs
  • Sept 2012 : CSTC representatives participate in Wiki Task Force meeting; discuss how to integrate cases into semantic wiki
  • Oct 2012: CSTC provides develops & tests case input form for semantic wiki
  • Nov 2012: CSTC solicits short cases from Forsys participants
  • Nov 2012 - Jan 2013 : CSTC follow up on potential cases, answer any questions, provide feedback on drafts
  • Feb 2013 : CTSC meets to review and synthesize cases for presentation/publication/contributing to FORSYS guidelines
  • Mar 2013: CSTC finishes case synthesis article to inform broader FORSYS guidelines
  • April 2013 : Selected cases and synthesis presented at Umea conference
  • (technically have until 3 months after end of project (4/2013) to complete all project work)

Develop case study examples and guidelines

  • Develop semantic form for entering case studies into the wiki
  • Figure out how cases will contribute to final Forsys guidelines

Manage case study contributions

  • Solicit case studies from the Forsys network
  • Review and comment on case studies submitted
  • Answer questions, resolve issues

Use of published literature

  • Assuming institutionalization of the wiki and not of the Cost Action per se, it does not matter whether a forsys member has delivered a case or a case study. Of course it does for the record of the Action, so a separate tag “Forsys member” should do.
  • This is a good point. The initial thinking is that these will be stored in different data structures: the wiki for forsys cases and a literature database (maybe Mendeley.com for the literature). However, somehow we would need to link from each to the guidelines they relate to.
  • Investigate possible technologies for managing/sharing case study literature

Categorization and searching of cases

  • The case study semantic form
    • tags each case with the general Category:Case
    • uses the other fields in the case form as tags/categorizies (e.g. Country, Decision phase)
  • Cases can be searched/filtered using custom semantic queries or pre-build semantic query pages

Synthesis of cases

  • Synthesis of the cases will focus on their recorded lessons, and how these lessons contribute to the overall FORSYS lessons/guidelines

Sharing results

  • The CTSC is hosting all cases to the FORSYS wiki
  • The CSTC has submitted a presentation proposal for the final FORSYS conference in April 2013
  • The CSTC has also proposed a case synthesis journal article for the FORSYS conference issue of the Scandinavian Journal of Forest Research
  • Other ideas???


DONE

After the Leuven 2011 meeting

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

Before the Leuven 2011 meeting

  • Develop two (or more) documents:
  • 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)