Difference between revisions of "Web Services"
(→Notes/Comments) |
|||
| Line 16: | Line 16: | ||
* Points: | * Points: | ||
** Tx level, Need user incentive to upload values, need associated notes, need graphing of | ** Tx level, Need user incentive to upload values, need associated notes, need graphing of | ||
| − | * | + | |
| − | * | + | === ''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." | ||
---- | ---- | ||
Revision as of 20:30, 31 August 2009
Status: API Complete, Prototyping Started, Requirements 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
Semi-structured interviews with researchers
- 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."
See complete DataShop Feature Wish List.
