Difference between revisions of "Case Studies"

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
Line 4: Line 4:
 
<b>All Forsys participants are requested to submit one or more case studies to the wiki.</b>  
 
<b>All Forsys participants are requested to submit one or more case studies to the wiki.</b>  
  
From <b>June - Dec 2012</b> the [[Case Study Technical Committee]] will solicit and follow up on potential cases, answer any questions, provide feedback on drafts.
+
From <b>June 2012 - Jan 2013</b> the [[Case Study Technical Committee]] will solicit and follow up on potential cases, answer any questions, provide feedback on drafts.
  
 
==Purpose==
 
==Purpose==
The purpose of thes case studies is to identify 'lessons learned' which will contribute to the overall Forsys objective of providing guidelines on DSS development and use.  
+
The purpose of thes case studies is to identify and share 'lessons learned' which will contribute to the overall Forsys objective of providing guidelines on DSS development and use.  
 +
 
 
==Sources==
 
==Sources==
 
Two sources of cases are possible:
 
Two sources of cases are possible:
 
# Unpublished cases contributed by Forsys members and STSMs: We ask that each Forsys participant try to identify one or more case from their personal knowledge and enter some basic information on it in the wiki (including lessons). We are in the proces of designing a semantic wiki form for members to enter this information.
 
# Unpublished cases contributed by Forsys members and STSMs: We ask that each Forsys participant try to identify one or more case from their personal knowledge and enter some basic information on it in the wiki (including lessons). We are in the proces of designing a semantic wiki form for members to enter this information.
 
# Cases from the literature: We also ask that Forsys participants identify existing cases in the literature and extract lessons learned. We are in the process of reviewing possible databases to enter and store this information, such as [http://www.citeulike.org/group/16172 Citeulike] and [http://www.mendeley.com/ Mendeley]
 
# Cases from the literature: We also ask that Forsys participants identify existing cases in the literature and extract lessons learned. We are in the process of reviewing possible databases to enter and store this information, such as [http://www.citeulike.org/group/16172 Citeulike] and [http://www.mendeley.com/ Mendeley]
==Example==
+
 
 +
==Case Studies List==
 
Similar to the DSS descriptions, we have identified certain types of information we would like to collect about each case. Please see this [[USA_Watershed_Condition_Assessment_for_the_Northwest_Forest_Plan | example case]].  
 
Similar to the DSS descriptions, we have identified certain types of information we would like to collect about each case. Please see this [[USA_Watershed_Condition_Assessment_for_the_Northwest_Forest_Plan | example case]].  
  
==Case Study Template==
+
==Contributing Case Studies ==
You can use this [[Case Study Template]] to create your own case on the wiki.
+
Please note that you must be logged into the wiki to add information. Click on the 'log in' text in the upper right corner and enter your existing account information or create a new account.
 +
 
 +
Once you are logged in, you can use this [[Form:Case_study|Case_study form]] to contribute a case to the wiki.
  
 
The focus of each case should be on 'lessons learned', so please pay special attention to linking the case description supports the lessons list at the end of the case.
 
The focus of each case should be on 'lessons learned', so please pay special attention to linking the case description supports the lessons list at the end of the case.
  
The [[Case Study Technical Committee]] is also working on a semantic wiki form for case entry, and we will send out the request to all Forsys members when the forms for entering case studies are ready.
+
Please contact the [[Case Study Technical Committee]] with any questions or problems - we are ready to help you!
 +
 
 
==More Information==
 
==More Information==
For more details on the Forsys case studies, please see the case studies category page at the link below:
+
For more background information on the Forsys case studies, please see the case studies category page at the link below:

Revision as of 01:57, 12 November 2012

All Forsys participants are requested to submit one or more case studies to the wiki.

From June 2012 - Jan 2013 the Case Study Technical Committee will solicit and follow up on potential cases, answer any questions, provide feedback on drafts.

Purpose

The purpose of thes case studies is to identify and share 'lessons learned' which will contribute to the overall Forsys objective of providing guidelines on DSS development and use.

Sources

Two sources of cases are possible:

  1. Unpublished cases contributed by Forsys members and STSMs: We ask that each Forsys participant try to identify one or more case from their personal knowledge and enter some basic information on it in the wiki (including lessons). We are in the proces of designing a semantic wiki form for members to enter this information.
  2. Cases from the literature: We also ask that Forsys participants identify existing cases in the literature and extract lessons learned. We are in the process of reviewing possible databases to enter and store this information, such as Citeulike and Mendeley

Case Studies List

Similar to the DSS descriptions, we have identified certain types of information we would like to collect about each case. Please see this example case.

Contributing Case Studies

Please note that you must be logged into the wiki to add information. Click on the 'log in' text in the upper right corner and enter your existing account information or create a new account.

Once you are logged in, you can use this Case_study form to contribute a case to the wiki.

The focus of each case should be on 'lessons learned', so please pay special attention to linking the case description supports the lessons list at the end of the case.

Please contact the Case Study Technical Committee with any questions or problems - we are ready to help you!

More Information

For more background information on the Forsys case studies, please see the case studies category page at the link below: