Difference between revisions of "Adding Custom Fields through Web Application"

From LearnLab
Jump to: navigation, search
(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...)
 
(Notes/Comments)
 
(5 intermediate revisions by one other user not shown)
Line 1: Line 1:
'''Status: Design, Req, SW Design needed'''
+
'''Status: Definition 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'''
+
* This is related to the [[Web Services - Add Custom Fields]] 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>
 
=== ''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>
 
----
 
----
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]]

Latest revision as of 20:46, 5 January 2011

Status: Definition Needed

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.

Notes/Comments



See completed DataShop 3.x Features
See on-going DataShop 4.x Features
See prioritized DataShop Feature Wish List
See unordered Collected User Requests