Difference between revisions of "Case Studies"

Warning: require(): Unable to allocate memory for pool. in /data/home/fp0804/www/wiki/includes/AutoLoader.php on line 1191

Revision as of 15:02, 9 May 2012 (view source) SeanGordon (Talk | contribs) m ← Older edit		Latest revision as of 18:59, 5 May 2013 (view source) SeanGordon (Talk | contribs) m
(20 intermediate revisions by one user not shown)
Line 1:		Line 1:
−	All Forsys participants are requested to submit one or more case studies to the wiki (similar to the DSS descriptions). 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.	+	[[Category:Case Studies]]
		+	<div style="float:right;">__TOC__</div>
−	Two sources of cases are envisioned:	+	<b>All Forsys participants are requested to submit one or more case studies to the wiki.</b>
−	# 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]	+
−	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]]. Then you can use this [[Case Study Template]] to create your own case on the wiki.	+	From <b>June 2012 - March 2013</b> the [[Case Study Technical Committee]] (CSTC) will solicit and follow up on potential cases, answer any questions, provide feedback on drafts.
−	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.	+	==Purpose==
		+	The main purpose of these 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.
−	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.	+	==Sources==
		+	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 cases from their personal knowledge and enter its basic information into the wiki (see below).
		+	# Published cases: We also encourage Forsys participants identify existing cases in the literature and enter the relevant information into the wiki (same process).
		+
		+	==Case Studies List==
		+	Follow this link to see a list of case studies already entered in our semantic mediawiki database: [[Case Studies List]]
		+
		+	Cases entered using our older standard wiki format can be found here: [[:Category:Forsys Case Studies]]
		+
		+	==Contributing New 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 [[Form:Case|Case study form]] to contribute a case to the wiki.
		+
		+	If you are transferring information from an existing case on the (regular, non-semantic) wiki, right-click on the following link to open a new window where you can find your case and then cut and paste from this window to the semantic form: [[:Category:Forsys Case Studies]]
		+
		+	The focus of each case should be on 'lessons learned' (which will contribute to the overall FORSYS DSS guidelines), so please consider what lessons you can derive from the case and make sure that your case description supports these lessons.
		+
		+	Please contact the [[Case Study Technical Committee]] with any questions or problems - we are ready to help you!
		+
		+	==Editing Existing 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.''
		+
		+	# Follow this link to see a list of case studies already entered in our semantic mediawiki database: [[Case Studies List]]
		+	# Click on the name of the case study you want to edit
		+	# Click on the 'edit with form' tab at the top of the page
		+
		+	==Analysis of Case Studies==
		+	* The CSTC is analyzing the cases and lessons collected; see the [[Case Studies Analysis]] page
		+
		+	==More Information==
		+	For more background information on the Forsys case studies, please see the case studies category page at the link below

---

Latest revision as of 18:59, 5 May 2013

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

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

Purpose

The main purpose of these 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 cases from their personal knowledge and enter its basic information into the wiki (see below).
2. Published cases: We also encourage Forsys participants identify existing cases in the literature and enter the relevant information into the wiki (same process).

Case Studies List

Follow this link to see a list of case studies already entered in our semantic mediawiki database: Case Studies List

Cases entered using our older standard wiki format can be found here: Category:Forsys Case Studies

Contributing New 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.

If you are transferring information from an existing case on the (regular, non-semantic) wiki, right-click on the following link to open a new window where you can find your case and then cut and paste from this window to the semantic form: Category:Forsys Case Studies

The focus of each case should be on 'lessons learned' (which will contribute to the overall FORSYS DSS guidelines), so please consider what lessons you can derive from the case and make sure that your case description supports these lessons.

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

Editing Existing 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.

1. Follow this link to see a list of case studies already entered in our semantic mediawiki database: Case Studies List
2. Click on the name of the case study you want to edit
3. Click on the 'edit with form' tab at the top of the page

Analysis of Case Studies

• The CSTC is analyzing the cases and lessons collected; see the Case Studies Analysis page

More Information

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