Documentation on Database Tables: Difference between revisions

From Expertiza_Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 5: Line 5:
   <br>The current Expertiza database has issues similar to what is described below:
   <br>The current Expertiza database has issues similar to what is described below:
   <br>1. redundant record. For instance, <b>deadline_types</b> table has two <b>signup</b> and <b>team_formation</b> record.
   <br>1. redundant record. For instance, <b>deadline_types</b> table has two <b>signup</b> and <b>team_formation</b> record.
   <br>2. some field name is confused. For instance, in <b>users</b> table <b>assignment_id</b> becomes <b>parent_id</b> and in <b>response_maps_assignment_id</b> becomes  
   <br>2. some field name is confused. For instance, in <b>users</b> table <b>assignment_id</b> becomes <b>parent_id</b> and in <b>response_maps</b> <b>assignment_id</b> becomes  
   <b>reviewed_object_id</b>.
   <b>reviewed_object_id</b>.



Revision as of 01:02, 22 April 2018

PROJECT TITLE: Regularize Expertiza DB schema

PROBLEM DESCRIPTION:
 
The current Expertiza database has some problems which needs to be rectified.
The current Expertiza database has issues similar to what is described below:
1. redundant record. For instance, deadline_types table has two signup and team_formation record.
2. some field name is confused. For instance, in users table assignment_id becomes parent_id and in response_maps assignment_id becomes reviewed_object_id.
 The scope of our project is to rectify these problems by performing the below steps.
 
1. Go through the Expertiza_development database to find tables that not used any more or redundant records.
2. Write migrations to regularize the Expertiza database and also change code if necessary.
3. Make sure all existing tests are passed and change test code if necessary
4. Modify database wiki page to make it up to date
DATABASE TABLE DESCRIPTION:
 
Below is the old detailed description of the tables in the Expertiza DB schema.
Our Primary Job is updating the wiki and making it more informative by including all the changes in the Expertiza Db in this wiki.
STEPS TO NAVIGATE TO expertiza_development SCHEMA:
 
1. Open terminal.
2. Change to the "expertiza" folder using the command: $cd expertiza
3. Invoke the rails database console using the command: "$rails dbconsole" and give the password "expertiza" when prompted.
4. List the databases present in the MYSQL server using the command >show databases;
5. Move to the "expertiza_development" database using the command >use expertiza_development
6. List down the tables present in the "expertiza_development" using the command >show tables;


  1. Assignments
    assignments
    assignment_questionnaires
    deadline_types
    deadline_rights
    due_dates
    late_policies
    participants
    wiki_types
    Deprecated Tables
    assignments_questionnaires
  2. Goldberg
    content_pages
    controller_actions
    markup_styles
    menu_items
    permissions
    plugin_schema_info
    roles
    roles_permissions
    schema_info
    site_controllers
    users
    system_settings
  3. Reviewing
    comments
    mapping_strategies
    responses
    response_maps
    review_strategies
    score_caches
    scores
    Deprecated Tables
    review_feedbacks
    review_mappings
    review_of_review_mappings
    review_of_reviews
    reviews
    teammate_reviews
  4. Teammate
    invitations
    teams
    teams_users
  5. Courses
    courses
  6. Hierarchy
    institutions
    languages
  7. Display
    nodes
    tree_folders
  8. Questionnaires/Rubrics
    question_advices
    questionnaires
    questions
    Deprecated Tables
    questionnaire_types
  9. Surveys
    survey_deployments
    survey_participants
    survey_responses
  10. Other Features
    signed_up_users
    sign_up_topics
    resubmission_times
    ta_mappings


Back to Expertiza_documentation Main page.