Adding Custom Fields through Web Application: Difference between revisions

From Theory Wiki
Jump to navigation Jump to search
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'''

Revision as of 13:33, 1 September 2009

Status: Design, Req, SW Design 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

  • 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)




See complete DataShop Feature Wish List.