Adding Custom Fields through Web Application - Revision history

Bleber: /* Notes/Comments */

2011-01-05T20:46:21Z

Notes/Comments

← Older revision		Revision as of 20:46, 5 January 2011
Line 4:		Line 4:

	== Notes/Comments ==		== Notes/Comments ==
	* This is related to the [[Web Services]] feature.		* This is related to the [[Web Services - Add Custom Fields]] feature.
	* First, implement at the '''Transaction Level'''.		* First, implement at the '''Transaction Level'''.

Alida at 18:46, 29 October 2010

2010-10-29T18:46:08Z

← Older revision		Revision as of 18:46, 29 October 2010
Line 6:		Line 6:
	* This is related to the [[Web Services]] feature.		* This is related to the [[Web Services]] feature.
	* First, implement at the '''Transaction Level'''.		* First, implement at the '''Transaction Level'''.


	<br>		<br>
	----		----
	See ~~complete~~ [[DataShop Feature Wish List]].		See completed [[DataShop 3.x Features]]<br>
			See on-going [[DataShop 4.x Features]]<br>
			See prioritized [[DataShop Feature Wish List]]<br>
			See unordered [[Collected User Requests]]
	[[Category:Protected]]		[[Category:Protected]]
	[[Category:DataShop]]		[[Category:DataShop]]
			[[Category:DataShop Feature]]

Alida at 13:34, 1 September 2009

2009-09-01T13:34:30Z

← Older revision		Revision as of 13:34, 1 September 2009
Line 1:		Line 1:
	'''Status: ~~Design, Req, SW Design needed~~'''		'''Status: Definition Needed'''
	== User Story ==		== User Story ==
	As a researcher, I want to add custom fields through the web application instead of using a program, so that I can blah blah blah.		As a researcher, I want to add custom fields through the web application instead of using a program, so that I can blah blah blah.

Alida at 13:34, 1 September 2009

2009-09-01T13:34:09Z

← Older revision		Revision as of 13:34, 1 September 2009
Line 4:		Line 4:

	== Notes/Comments ==		== Notes/Comments ==
	* ~~Adding custom fields~~ to ~~existing datasets~~ at '''Transaction Level ~~only~~'''		* This is related to the [[Web Services]] feature.
	* Needed for M&M and CMDM clusters [Ryan Baker, October 2008]		* First, implement at the '''Transaction Level'''.
	* Will enable researchers to use output from existing models
	** Gaming Detector [Arnon Hershkovitz, Mihaela Cocea, Summer 2008]
	** Bayesian Knowledge Tracing. [Hao Cen, migrated from feature wish list]
	* Key to collaboration.
	* Ability to automatically add columns to DataShop data sets at transaction level [Ryan, Startup Memo, summer 2008]<br>
	* Points:
	** Tx level, Need user incentive to upload values, need associated notes, need graphing of
	* Users to interview:<br>
	** Ryan, Phil Pavlik, Joe Beck (note to Joe, this is not about adding the models yet, just the results from running them outside of DS)<br>

Alida: /* User Story */

2009-09-01T13:33:19Z

User Story

← Older revision		Revision as of 13:33, 1 September 2009
Line 1:		Line 1:
	'''Status: Design, Req, SW Design needed'''		'''Status: Design, Req, SW Design needed'''
	== User Story ==		== User Story ==
	As a researcher ~~(EDM, M&M, CMDM)~~, I want to ~~retrieve transaction data programmatically and append~~ custom fields ~~to transactions in DataShop~~ so that I can ~~more easily run my models on the data outside of DataShop and put the results back in~~.		As a researcher, I want to add custom fields through the web application instead of using a program, so that I can blah blah blah.

	== Notes/Comments ==		== Notes/Comments ==
	* Adding custom fields to existing datasets at '''Transaction Level only'''		* Adding custom fields to existing datasets at '''Transaction Level only'''

Alida: /* ''Semi-structured interviews with researchers'' */

2009-08-31T20:29:57Z

''Semi-structured interviews with researchers''

← Older revision		Revision as of 20:29, 31 August 2009
Line 14:		Line 14:
	* Users to interview:<br>		* Users to interview:<br>
	** Ryan, Phil Pavlik, Joe Beck (note to Joe, this is not about adding the models yet, just the results from running them outside of DS)<br>		** Ryan, Phil Pavlik, Joe Beck (note to Joe, this is not about adding the models yet, just the results from running them outside of DS)<br>
	~~=== ''Semi-structured interviews with researchers'' ===~~

	* [[Ido Roll - January 19, 2009\|Ido Roll]]: main conclusions are that being able to use the new columns in the same ways one can use DataShop-native colums might be crucial; data is often not at transaction level (eg, student variable), so DS might do the tx-level mapping for the user based on key column(s)<br>
	* Phil Pavlik, email: "I guess I might use the adding of a column by itself if the opportunity was there to look at it as a model graph in DataShop. Often it is good to visualize the results of a model." [Follow up to determine what "model graphs" Phil has in mind]

	<br>		<br>

Alida: New page: '''Status: Design, Req, SW Design needed''' == User Story == As a researcher (EDM, M&M, CMDM), I want to retrieve transaction data programmatically and append custom fields to transact...

2009-08-31T20:27:06Z

New page: '''Status: Design, Req, SW Design needed''' == User Story == As a researcher (EDM, M&M, CMDM), I want to retrieve transaction data programmatically and append custom fields to transact...

New page

'''Status: Design, Req, SW Design needed'''
== User Story ==
As a researcher (EDM, M&M, CMDM), I want to retrieve transaction data programmatically and append custom fields to transactions in DataShop so that I can more easily run my models on the data outside of DataShop and put the results back in.
== Notes/Comments ==
* Adding custom fields to existing datasets at '''Transaction Level only'''
* Needed for M&M and CMDM clusters [Ryan Baker, October 2008]
* Will enable researchers to use output from existing models
** Gaming Detector [Arnon Hershkovitz, Mihaela Cocea, Summer 2008]
** Bayesian Knowledge Tracing. [Hao Cen, migrated from feature wish list]
* Key to collaboration.
* Ability to automatically add columns to DataShop data sets at transaction level [Ryan, Startup Memo, summer 2008] 
* Points:
** Tx level, Need user incentive to upload values, need associated notes, need graphing of
* Users to interview: 
** Ryan, Phil Pavlik, Joe Beck (note to Joe, this is not about adding the models yet, just the results from running them outside of DS) 
=== ''Semi-structured interviews with researchers'' ===

* [[Ido Roll - January 19, 2009|Ido Roll]]: main conclusions are that being able to use the new columns in the same ways one can use DataShop-native colums might be crucial; data is often not at transaction level (eg, student variable), so DS might do the tx-level mapping for the user based on key column(s) 
* Phil Pavlik, email: "I guess I might use the adding of a column by itself if the opportunity was there to look at it as a model graph in DataShop. Often it is good to visualize the results of a model." [Follow up to determine what "model graphs" Phil has in mind]

 
----
See complete [[DataShop Feature Wish List]].
[[Category:Protected]]
[[Category:DataShop]]