Condition in Student-Step Rollup - Revision history

Alida at 14:34, 16 May 2011

2011-05-16T14:34:24Z

← Older revision		Revision as of 14:34, 16 May 2011
Line 20:		Line 20:
	<br>		<br>
	----		----
	See ~~completed~~ [[DataShop ~~3.x~~ Features]]<br>		See [[DataShop Completed Features\|completed features]]<br>
	See ~~on-going~~ [[DataShop ~~4.x~~ Features]]<br>		See [[DataShop On-going Features\|on-going features]]<br>
	See unordered [[Collected User Requests]]		See unordered [[Collected User Requests]]<br>
			See the [[:Category:DataShop Glossary\|DataShop Glossary]]
	[[Category:Protected]]		[[Category:Protected]]
	[[Category:DataShop]]		[[Category:DataShop]]
	[[Category:DataShop Completed Feature]]		[[Category:DataShop Completed Feature]]

2010-10-29T18:08:10Z

← Older revision		Revision as of 18:08, 29 October 2010
Line 20:		Line 20:
	<br>		<br>
	----		----
	See ~~complete~~ [[DataShop ~~Feature Wish List~~]].		See completed [[DataShop 3.x Features]]<br>
			See on-going [[DataShop 4.x Features]]<br>
			See unordered [[Collected User Requests]]
	[[Category:Protected]]		[[Category:Protected]]
	[[Category:DataShop]]		[[Category:DataShop]]
			[[Category:DataShop Completed Feature]]

2010-10-29T17:53:19Z

← Older revision		Revision as of 17:53, 29 October 2010
Line 1:		Line 1:
	'''Status: ~~Requirements Started~~ (~~planned to be released in December 2009 as part of~~ DataShop v4.0)'''		'''Status: Done (DataShop v4.0 December 2009)'''

	== User Story ==		== User Story ==

2009-11-05T15:08:10Z

← Older revision		Revision as of 15:08, 5 November 2009
Line 1:		Line 1:
	'''Status: Requirements Started (planned to be released in December 2009 as part of DataShop v4.0'''		'''Status: Requirements Started (planned to be released in December 2009 as part of DataShop v4.0)'''

	== User Story ==		== User Story ==

2009-11-05T15:08:00Z

← Older revision		Revision as of 15:08, 5 November 2009
Line 1:		Line 1:
	'''Status: ~~Design Needed~~'''		'''Status: Requirements Started (planned to be released in December 2009 as part of DataShop v4.0'''

	== User Story ==		== User Story ==

2009-10-29T20:22:05Z

Notes/Comments

← Older revision		Revision as of 20:22, 29 October 2009
Line 16:		Line 16:
	** Variable number of condition columns in step rollup is OK, but so is concatenating condition names with a delimiter in between them.		** Variable number of condition columns in step rollup is OK, but so is concatenating condition names with a delimiter in between them.
	* Vincent votes for a single column describing condition.		* Vincent votes for a single column describing condition.
	** By definition, each student is in one condition, so a single column should suffice. (I believe what you are describing is a "factor" in a factorial design. That could be useful but could always be derived from the condition in a very straightforward manner. And vice versa. So to keep things simple I'd go with a single column.		** By definition, each student is in one condition, so a single column should suffice. (I believe what you are describing is a "factor" in a factorial design. That could be useful but could always be derived from the condition in a very straightforward manner. And vice versa. So to keep things simple I'd go with a single column. -- Vincent email 9/3/2009

	<br>		<br>

2009-10-29T20:19:03Z

Notes/Comments

@@ Line 17: / Line 17: @@
 * Vincent votes for a single column describing condition.
 ** By definition, each student is in one condition, so a single column should suffice.  (I believe what you are describing is a "factor" in a factorial design. That could be useful but could always be derived from the condition in a very straightforward manner. And vice versa. So to keep things simple I'd go with a single column.
 <br>

2009-10-29T20:18:41Z

Notes/Comments

← Older revision		Revision as of 20:18, 29 October 2009
Line 16:		Line 16:
	** Variable number of condition columns in step rollup is OK, but so is concatenating condition names with a delimiter in between them.		** Variable number of condition columns in step rollup is OK, but so is concatenating condition names with a delimiter in between them.
	* Vincent votes for a single column describing condition.		* Vincent votes for a single column describing condition.
	** By definition, each student is in one condition, so a single column should suffice. (I believe what you are describing is a "factor" in a factorial design. That could be useful but could always be derived from the condition in a very straightforward manner. And vice versa. So to		** By definition, each student is in one condition, so a single column should suffice. (I believe what you are describing is a "factor" in a factorial design. That could be useful but could always be derived from the condition in a very straightforward manner. And vice versa. So to keep things simple I'd go with a single column.
	keep things simple I'd go with a single column.

	Brett		Brett

2009-10-29T20:18:22Z

Notes/Comments

@@ Line 14: / Line 14: @@
 * Ken, 8/14/2009: To use the step roll-up table in 'R', the condition is important in this table.&nbsp; Also take out the '#' sign from the headers as that is a comment and causes problems in 'R'. [Ken Meeting 8/14/2009]
 * How to show the conditions, multiple columns? one column? use labels or 1's and 0's? -- [[User:Koedinger|Koedinger]], DataShop Team Meeting, Aug 28, 2009
 ** Variable number of condition columns in step rollup is OK, but so is concatenating condition names with a delimiter in between them.
 <br>

2009-09-14T13:55:27Z

Notes/Comments

← Older revision		Revision as of 13:55, 14 September 2009
Line 13:		Line 13:
	* Alida, 4/30/2008: You can create a sample per condition, then select all those samples and then export the Step Rollup Table. Sample is one of the columns in the Step Rollup Table and export. This would be better than trying to get the same information from a transaction export.		* Alida, 4/30/2008: You can create a sample per condition, then select all those samples and then export the Step Rollup Table. Sample is one of the columns in the Step Rollup Table and export. This would be better than trying to get the same information from a transaction export.
	* Ken, 8/14/2009: To use the step roll-up table in 'R', the condition is important in this table.  Also take out the '#' sign from the headers as that is a comment and causes problems in 'R'. [Ken Meeting 8/14/2009]		* Ken, 8/14/2009: To use the step roll-up table in 'R', the condition is important in this table.  Also take out the '#' sign from the headers as that is a comment and causes problems in 'R'. [Ken Meeting 8/14/2009]
			* How to show the conditions, multiple columns? one column? use labels or 1's and 0's? -- [[User:Koedinger\|Koedinger]], DataShop Team Meeting, Aug 28, 2009
			** Variable number of condition columns in step rollup is OK, but so is concatenating condition names with a delimiter in between them.

	<br>		<br>