Difference between revisions of "Web Services"

From LearnLab
Jump to: navigation, search
 
(9 intermediate revisions by 2 users not shown)
Line 1: Line 1:
'''Status: API Complete, Prototyping Started, Requirements Needed'''
+
This page collects links to web services features.
  
== User Story ==
+
* [[DataShop_3.x_Features#Web_Services_Feature_.28Authentication.2C_Get_Dataset_Metadata.2C_Get_Sample_Metadata.29 | Web Services - Authentication, Get Dataset Metadata, Get Sample Metadata]]
 +
* [[Web Services - Get Transactions and Student-Step Records]]
 +
* [[Web Services - Add Custom Fields]]
  
As a researcher (EDM, M&amp;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.<br>
+
== User Stories ==
As a researcher with a machine learning background, I want to retrieve student-step data programmatically so that I can more easily run my analyses on the data without much human intervention.
 
  
== Notes/Comments ==
+
# As a researcher (EDM, M&amp;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 with a machine learning background, I want to retrieve student-step data programmatically so that I can more easily run my analyses on the data without much human intervention.
 +
# As a researcher who has created a custom field for an existing data set, I want to import that new field into the step rollup table so that it is both preserved and available in DataShop tools. - Ryan Baker, 12/15/2008
  
* Adding custom fields to existing datasets at '''Transaction Level only'''
 
* Needed for M&amp;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''
+
----
 +
See completed [[DataShop 3.x Features]]<br>
 +
See on-going [[DataShop 4.x Features]]<br>
 +
See unordered [[Collected User Requests]]
  
* [[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."
 
 
<br>
 
----
 
See complete [[DataShop Feature Wish List]].
 
 
[[Category:Protected]]
 
[[Category:Protected]]
 
[[Category:DataShop]]
 
[[Category:DataShop]]
 +
[[Category:DataShop Completed Feature]]

Latest revision as of 20:27, 5 January 2011

This page collects links to web services features.

User Stories

  1. 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.
  2. As a researcher with a machine learning background, I want to retrieve student-step data programmatically so that I can more easily run my analyses on the data without much human intervention.
  3. As a researcher who has created a custom field for an existing data set, I want to import that new field into the step rollup table so that it is both preserved and available in DataShop tools. - Ryan Baker, 12/15/2008



See completed DataShop 3.x Features
See on-going DataShop 4.x Features
See unordered Collected User Requests