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
 
(24 intermediate revisions by one user not shown)
Line 1: Line 1:
 
[[category:Case Studies]]
 
[[category:Case Studies]]
 
[[category:Meeting Nov 2011]]
 
[[category:Meeting Nov 2011]]
 +
<div style="float:right;">__TOC__</div>
  
−
'''How to maneuver the discussions/work if we are something like 35 persons with 2 rather big rooms at our disposal (and perhaps smaller groups can find some space in the surroundings as well)? Having a common discussion all along might be difficult (or not so productive). Depending on how we divide the sessions, one may start thinking about how to compose the guidelines out of your material.'''
+
==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 [[Form:Case study|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)
  
−
Here are some ideas for group feedback:
+
==Develop case study examples and guidelines==
−
*[30 minutes] begin with a brief common presentation and discussion on progress to date and next steps for subgroups (build more details on framework for conduction case studies); answer any general questions
+
* Develop semantic form for entering case studies into the wiki
−
*[1.5 hours] Break into ~4 subgroups with ~8 people each, trying to get even representation from each WG in each, including one of us in each (because it looks like case studies have already been discussed by each WG in Greece, now we could try to synthesize across WGs). All groups would have the same assignment: to review the current state of the case study framework, provide feedback, and develop more detail.
+
* Figure out how cases will contribute to final Forsys guidelines
−
*[30 min] Groups would report a summary of their suggestions back to whole group
+
−
*[30 min] Synthesis discussion
+
  
−
'''Another matter is the case study STC and how it can be fruitfully used before, at and after the meeting? Is there some kind of assignments we should give to the STC (with one member from each WG)?'''
+
==Manage case study contributions==
−
*Plan the Nov 2011 activities
+
* Solicit case studies from the Forsys network
−
*Develop two (or more) documents for the Nov meeting:
+
* Review and comment on case studies submitted
−
** [[Case Study Guidelines]]: the basic framework we want people to build on at the Nov meeting (most important points for discussion)
+
* Answer questions, resolve issues
−
** [[Case Study Notes by Research Phase]]: further background information to consider in developing the guidelines
+
 
−
*Gather further information on case studies
+
===Use of published literature===
−
** Existing forest DSS case study 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.
−
** Other relevant literature (methods, etc)
+
* 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
 +
** e.g. [http://www.mendeley.com/ Mendeley] or [http://www.citeulike.org/ Citeulike]
 +
 
 +
===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===
 +
* Synthesized Leuven discussion and updated [[Case Study Guidelines]] on the wiki
 +
* 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===
 +
*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)

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)
Retrieved from "http://fp0804.emu.ee/wiki/index.php?title=Case_Study_Committee_Workplan&oldid=5420"