Difference between revisions of "DB Merge"

From LearnLab
Jump to: navigation, search
Line 16: Line 16:
 
See completed [[DataShop 3.x Features]]<br>
 
See completed [[DataShop 3.x Features]]<br>
 
See on-going [[DataShop 4.x Features]]<br>
 
See on-going [[DataShop 4.x Features]]<br>
 +
See prioritized [[DataShop Feature Wish List]]
 
See unordered [[Collected User Requests]]
 
See unordered [[Collected User Requests]]
 
[[Category:Protected]]
 
[[Category:Protected]]
 
[[Category:DataShop]]
 
[[Category:DataShop]]
 
[[Category:DataShop Feature]]
 
[[Category:DataShop Feature]]

Revision as of 14:23, 29 October 2010

Status: In Progress, December 2010

User Story

As a DataShop administrator, I want to merge two analysis databases, so that I can get a mysql dump from Tristan at Carnegie Learning instead of running the munger.

Notes/Comments

  • Carnegie Learning maintains a database equivalent to the DataShop analysis_db schema. They log their tutoring data to a file and then use their Munger tool to import it to their database. Previously, we used the same Munger on our database to import their logged data, which was slow and redundant. The idea of DBMerge is after Carnegie Learning has munged the data to their database they can perform a sql database dump to give us. DataShop will create a new database identical to analysis_db to import the db file to. A new stored procedure will be run to quickly integrate analysis_db with the Carnegie Learning data while maintaining key integrity.
  • Carnegie Learning has a massive amount of data already in our format but not in DataShop yet, with the potential to at least double, the amount of data in the repository.
  • Eliminates some of the manual workflow of munging one dataset at a time.
  • Prerequisite for redesign of the import tool and future database changes
  • Alida 14:48, 10 September 2010 (EDT)



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