Difference between revisions of "Case Studies and Lessons Learned Workgroup Progress Reports"

From forestDSS
Jump to: navigation, search
Line 7: Line 7:
 
* Mar - Apr 2012 : Case study technical committee (CSTC) develops example cases
 
* Mar - Apr 2012 : Case study technical committee (CSTC) develops example cases
 
* May (Zvolen meeting) : CSTC reports on progress and coordinates work with other WGs
 
* May (Zvolen meeting) : CSTC reports on progress and coordinates work with other WGs
−
* Jun 2012: CSTC provides reporting form for CS and solicits short cases from Forsys participants
+
* Sept 2012 : CSTC representatives participate in Wiki Task Force meeting; discuss how to integrate cases into semantic wiki
−
* June - Dec 2012 : CSTC follow up on potential cases, answer any questions, provide feedback on drafts
+
* Oct 2012: CSTC provides develops & tests case input form for semantic wiki
−
* Jan 2013 : CTSC assesses potential for publication, solicits longer cases as needed, starts synthesis
+
* Nov 2012: CSTC solicits short cases from Forsys participants
−
* Mar 2013: CSTC finishes CS synthesis article to inform broader FORSYS guidelines  
+
* 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
 
* 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
  
−
===What do we do with the case study ideas we receive?===
+
===Use of published literature===
−
* Cases with STSM opportunities should be entered on the wiki at http://fp0804.emu.ee/wiki/index.php/Category:STSM_Opportunity
+
* 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.
−
* For cases generally, the idea was to create a semantic form similar to what is being developed for the DSS, but this will take some time to develop. In the meantime, maybe we can just post them directly to the standard wiki. I added a subcategory to [[:Category:Case Studies]] that is [[:Category:Forsys Case Studies]] (but this is just a temporary strategy). It may be important to somehow separate cases that Forsys participants plan to use to contribute towards the project guidelines from general cases in the literature, but we are not sure exactly how yet - see Forsys vs Literature question.
+
* 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.
−
 
+
−
===How to we tag/categorize the cases?===
+
−
* It seems to me that tags need to be smaller than “Cases of participatory planning in forestry”. The point is modularity. So “case study” is enough for a case study. And “case” is enough for a case. (without describing the study –methodology, theory- behind it). Then “participation” is another tag.
+
−
* True in principle, but there do seem to be some differences between wiki categories and keywords more generally (although we're all just learning). The fundamental difference seems to be that there is no way to use multiple wiki categories at once to find, for example, all “cases” with “participation”. This leads to the use of long categories involving multiple concepts. Also, wiki categories are used as the title of pages and longer ones are helpful for this. As we move to the semantic wiki, it looks like the modular approach will be possible.
+
−
 
+
−
==Case study literature database==
+
 
* 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]
  
−
===Do we separate cases from Forsys participants from cases from the literature?===
+
===Categorization and searching of cases===
−
* 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.
+
* The case study semantic form
−
* 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.
+
** 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
  
−
==Publications==
+
==Sharing results==
−
* Think of publication possibilities for case study work
+
* The CTSC is hosting all cases to the FORSYS wiki
−
===Possibilities===
+
* The CSTC has submitted a presentation proposal for the final FORSYS conference in April 2013
−
* Book: similar to country reports book; would require a high level of effort and good contributions
+
* The CSTC has also proposed a case synthesis journal article for the FORSYS conference issue of the Scandinavian Journal of Forest Research
−
* Journal special issue: what possible journals? Forest Systems, ???
+
* Other ideas???
−
* Individual journal articles: just encourage/help cases submit articles individually
+
−
* Wiki: as a minimum, we'll post all cases to the wiki and use the semantic forms to make connections between them
+
−
* Other???
+
  
  

Revision as of 01:56, 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://www.forestdss.org/wiki/index.php?title=Case_Studies_and_Lessons_Learned_Workgroup_Progress_Reports&oldid=5416"