Difference between revisions of "DB Merge"
(New page: '''Status: Prioritization Needed''' == User Story == As a [type of user], I want to [perform some task] so that I can [achieve some goal]. == Notes/Comments == * Describe your problem ...) |
m |
||
| (7 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | '''Status: | + | '''Status: Done (DataShop v4.4 December 2010)''' |
== User Story == | == User Story == | ||
| − | As a | + | 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 == | == 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 | ||
| + | * [[User:Alida|Alida]] 14:48, 10 September 2010 (EDT) | ||
<br> | <br> | ||
---- | ---- | ||
| − | See | + | See [[DataShop Completed Features|completed features]]<br> |
| + | See [[DataShop On-going Features|on-going features]]<br> | ||
| + | See unordered [[Collected User Requests]]<br> | ||
| + | See the [[:Category:DataShop Glossary|DataShop Glossary]] | ||
[[Category:Protected]] | [[Category:Protected]] | ||
[[Category:DataShop]] | [[Category:DataShop]] | ||
| + | [[Category:DataShop Completed Feature]] | ||
Latest revision as of 14:36, 16 May 2011
Status: Done (DataShop v4.4 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 features
See on-going features
See unordered Collected User Requests
See the DataShop Glossary
