Expertiza_Wiki - User contributions [en]

Documentation on Database Tables

2018-04-28T00:52:53Z

Psinha:

'''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;

'''FLOWCHART:'''

[[File:FLOWCHART1.JPG]]

'''FINDING REDUNDANT TABLES'''
STEPS:
 1. Write SQL scripts to find the duplicate records. For example in the table,deadline_types a SQL query to find duplicate records is as follows.
 
select name from deadline_types group by name having count(*)>1;
 
Running this query in the SQL prompt, we find that there are two rows with the same information, hence they are redundant.

'''WRITING SCRIPTS TO REGULARIZE THE EXPERTIZA SCHEMA:'''
STEPS:
 1. Write SQL scripts to delete the redundant scripts and tables.For example in the table, <deadline_types> a SQL query to delete the duplicate records are as follows.
 
delete from deadline_types where id not in (select * from (select min(id) from deadline_types group by name) as temp);
 
Running this query in the SQL prompt,it will delete the duplicate records except one.

'''WRITING THE DATABASE MIGRATION SCRIPTS:'''
STEPS:
 1. Write the rails migration scripts to migrate the SQL that would delete the redundant records for certain table.
 The steps to write the rails migration scripts can be explained in the below steps:
 
STEPS:
 1.1 Open a terminal
 1.2 Navigate to the expertiza folder using the command: $cd expertiza
 1.3 Generate a migration script using the command in the terminal: $ rails generate migration RemoveDuplicateDeadlineTypes
 1.4 Write the SQL query to be executed to delete the redundant records inside the migration script.
 1.5 Save the migration script.
 2. The migration scrips are present in the expertiza/db/migrate folder can be migrated using the command rails db:migrate

'''TEST PLAN :'''
STEPS:
 1. Validate the schema expertiza_development
 2. Rerun the sql scripts to find out the redundant records in the tables.It should return null records
 3. Re validate the schema expertiza_development

# '''Assignments'''
#: [[assignments]]
#: [[assignment_questionnaires]]
#: [[Assignment_badges]]
#: [[calculated_penalties]]
#: [[deadline_types]]
#: [[deadline_rights]]
#: [[due_dates]]
#: [[late_policies]]
#: [[participants]]
#: [[plagiarism_checker_comparisons]]
#: [[plagiarism_checker_assignment_submissions]]
#: [[submission_records]]
#: [[wiki_types]]
#: ''Deprecated Tables''
#:: [[assignments_questionnaires]]
# '''Answers'''
#: [[Answers]]
#: [[answer_tags]]
# '''Goldberg'''
#: [[content_pages]]
#: [[controller_actions]]
#: [[Delayed_jobs]]
#: [[markup_styles]]
#: [[menu_items]]
#: [[password_resets]]
#: [[permissions]]
#: [[plugin_schema_info]]
#: [[requested_users]]
#: [[roles]]
#: [[roles_permissions]]
#: [[schema_info]]
#: [[schema_migrations]]
#: [[site_controllers]]
#: [[users]]
#: [[user_pastebins]]
#: [[system_settings]]
# '''Reviewing'''
#: [[automated_metareviews]]
#: [[Awarded_badges]]
#: [[Badges]]
#: [[comments]]
#: [[mapping_strategies]]
#: [[responses]]
#: [[response_maps]]
#: [[review_strategies]]
#: [[Review_grades]]
#: [[Review_scores]]
#: [[review_of_review_scores]]
#: [[review_comments_paste_bins]]
#: [[score_caches]]
#: [[scores]]
#: [[suggestions]]
#: [[suggestion_comments]]
#: ''Deprecated Tables''
#:: [[review_feedbacks]]
#:: [[review_mappings]]
#:: [[review_of_review_mappings]]
#:: [[review_of_reviews]]
#:: [[reviews]]
#:: [[teammate_reviews]]
# '''Teammate'''
#: [[Bids]]
#: [[invitations]]
#: [[Join_team_requests]]
#: [[signed_up_teams]]
#: [[teams]]
#: [[teams_users]]
# '''Courses'''
#: [[Courses_table|courses]]
#: [[Courses_users]]
# '''Hierarchy'''
#: [[institutions]]
#: [[languages]]
#: [[sessions]]
#: [[sections]]
#: [[versions]]
# '''Display'''
#: [[nodes]]
#: [[notifications]]
#: [[tree_folders]]
#: [[Track_notifications]]
# '''Questionnaires/Rubrics'''
#: [[question_advices]]
#: [[questionnaires]]
#: [[Questions_table|questions]]
#: [[quiz_question_choices]]
#: ''Deprecated Tables''
#:: [[questionnaire_types]]
# '''Surveys'''
#: [[survey_deployments]]
#: [[survey_responses]]
# '''Other Features'''
#: [[bookmarks]]
#: [[bookmark_ratings]]
#: [[signed_up_users]]
#: [[sign_up_topics]]
#: [[resubmission_times]]
#: [[ta_mappings]]
#: [[Tag_prompts]]
#: [[Tag_prompt_deployments]]
# '''Views'''

#: [[score_views]]



Back to [[Expertiza_documentation]] Main page.

Documentation on Database Tables

2018-04-28T00:52:11Z

Psinha:

'''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;

'''FLOWCHART:'''

[[File:FLOWCHART1.JPG]]

'''FINDING REDUNDANT TABLES'''
STEPS:
 1. Write SQL scripts to find the duplicate records. For example in the table,deadline_types a SQL query to find duplicate records is as follows.
 
select name from deadline_types group by name having count(*)>1;
 
Running this query in the SQL prompt, we find that there are two rows with the same information, hence they are redundant.

'''WRITING SCRIPTS TO REGULARIZE THE EXPERTIZA SCHEMA:'''
STEPS:
 1. Write SQL scripts to delete the redundant scripts and tables.For example in the table, <deadline_types> a SQL query to delete the duplicate records are as follows.
 
delete from deadline_types where id not in (select * from (select min(id) from deadline_types group by name) as temp);
 
Running this query in the SQL prompt,it will delete the duplicate records except one.

'''WRITING THE DATABASE MIGRATION SCRIPTS:'''
STEPS:
 1. Write the rails migration scripts to migrate the SQL that would delete the redundant records for certain table.
 The steps to write the rails migration scripts can be explained in the below steps:
 
STEPS:
 1.1 Open a terminal
 1.2 Navigate to the expertiza folder using the command: $cd expertiza
 1.3 Generate a migration script using the command in the terminal: $ rails generate migration RemoveDuplicateDeadlineTypes
 1.4 Write the SQL query to be executed to delete the redundant records inside the migration script.
 1.5 Save the migration script.
 2. The migration scrips are present in the expertiza/db/migrate folder can be migrated using the command rails db:migrate

'''TEST PLAN :'''
STEPS:
 1. Validate the schema expertiza_development
 2. Rerun the sql scripts to find out the redundant records in the tables.It should return null records
 3. Re validate the schema expertiza_development

# '''Assignments'''
#: [[assignments]]
#: [[assignment_questionnaires]]
#: [[Assignment_badges]]
#: [[calculated_penalties]]
#: [[deadline_types]]
#: [[deadline_rights]]
#: [[due_dates]]
#: [[late_policies]]
#: [[participants]]
#: [[plagiarism_checker_comparisons]]
#: [[plagiarism_checker_assignment_submissions]]
#: [[submission_records]]
#: [[wiki_types]]

#: ''Deprecated Tables''
#:: [[assignments_questionnaires]]

# '''Answers'''
#: [[Answers]]
#: [[answer_tags]]

# '''Goldberg'''
#: [[content_pages]]
#: [[controller_actions]]
#: [[Delayed_jobs]]
#: [[markup_styles]]
#: [[menu_items]]
#: [[password_resets]]
#: [[permissions]]
#: [[plugin_schema_info]]
#: [[requested_users]]
#: [[roles]]
#: [[roles_permissions]]
#: [[schema_info]]
#: [[schema_migrations]]
#: [[site_controllers]]
#: [[users]]
#: [[user_pastebins]]
#: [[system_settings]]

# '''Reviewing'''
#: [[automated_metareviews]]
#: [[Awarded_badges]]
#: [[Badges]]
#: [[comments]]
#: [[mapping_strategies]]
#: [[responses]]
#: [[response_maps]]
#: [[review_strategies]]
#: [[Review_grades]]
#: [[Review_scores]]
#: [[review_of_review_scores]]
#: [[review_comments_paste_bins]]
#: [[score_caches]]
#: [[scores]]
#: [[suggestions]]
#: [[suggestion_comments]]

#: ''Deprecated Tables''
#:: [[review_feedbacks]]
#:: [[review_mappings]]
#:: [[review_of_review_mappings]]
#:: [[review_of_reviews]]
#:: [[reviews]]
#:: [[teammate_reviews]]

# '''Teammate'''
#: [[Bids]]
#: [[invitations]]
#: [[Join_team_requests]]
#: [[signed_up_teams]]
#: [[teams]]
#: [[teams_users]]

# '''Courses'''
#: [[Courses_table|courses]]
#: [[Courses_users]]

# '''Hierarchy'''
#: [[institutions]]
#: [[languages]]
#: [[sessions]]
#: [[sections]]
#: [[versions]]

# '''Display'''
#: [[nodes]]
#: [[notifications]]
#: [[tree_folders]]
#: [[Track_notifications]]

# '''Questionnaires/Rubrics'''
#: [[question_advices]]
#: [[questionnaires]]
#: [[Questions_table|questions]]
#: [[quiz_question_choices]]
#: ''Deprecated Tables''
#:: [[questionnaire_types]]

# '''Surveys'''
#: [[survey_deployments]]
#: [[survey_responses]]

# '''Other Features'''
#: [[bookmarks]]
#: [[bookmark_ratings]]
#: [[signed_up_users]]
#: [[sign_up_topics]]
#: [[resubmission_times]]
#: [[ta_mappings]]
#: [[Tag_prompts]]
#: [[Tag_prompt_deployments]]

# '''Views'''

#: [[score_views]]



Back to [[Expertiza_documentation]] Main page.

Documentation on Database Tables

2018-04-28T00:50:13Z

Psinha:

'''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;

'''FLOWCHART:'''

[[File:FLOWCHART1.JPG]]

'''FINDING REDUNDANT TABLES'''
STEPS:
 1. Write SQL scripts to find the duplicate records. For example in the table,deadline_types a SQL query to find duplicate records is as follows.
 
select name from deadline_types group by name having count(*)>1;
 
Running this query in the SQL prompt, we find that there are two rows with the same information, hence they are redundant.

'''WRITING SCRIPTS TO REGULARIZE THE EXPERTIZA SCHEMA:'''
STEPS:
 1. Write SQL scripts to delete the redundant scripts and tables.For example in the table, <deadline_types> a SQL query to delete the duplicate records are as follows.
 
delete from deadline_types where id not in (select * from (select min(id) from deadline_types group by name) as temp);
 
Running this query in the SQL prompt,it will delete the duplicate records except one.

'''WRITING THE DATABASE MIGRATION SCRIPTS:'''
STEPS:
 1. Write the rails migration scripts to migrate the SQL that would delete the redundant records for certain table.
 The steps to write the rails migration scripts can be explained in the below steps:
 
STEPS:
 1.1 Open a terminal
 1.2 Navigate to the expertiza folder using the command: $cd expertiza
 1.3 Generate a migration script using the command in the terminal: $ rails generate migration RemoveDuplicateDeadlineTypes
 1.4 Write the SQL query to be executed to delete the redundant records inside the migration script.
 1.5 Save the migration script.
 2. The migration scrips are present in the expertiza/db/migrate folder can be migrated using the command rails db:migrate

'''TEST PLAN :'''
STEPS:
 1. Validate the schema expertiza_development
 2. Rerun the sql scripts to find out the redundant records in the tables.It should return null records
 3. Re validate the schema expertiza_development

# '''Assignments'''
#: [[assignments]]
#: [[assignment_questionnaires]]
#: [[Assignment_badges]]
#: [[calculated_penalties]]
#: [[deadline_types]]
#: [[deadline_rights]]
#: [[due_dates]]
#: [[late_policies]]
#: [[participants]]
#: [[plagiarism_checker_comparisons]]
#: [[plagiarism_checker_assignment_submissions]]
#: [[submission_records]]
#: [[wiki_types]]

#: ''Deprecated Tables''
#:: [[assignments_questionnaires]]

# '''Answers'''
#: [[Answers]]
#: [[answer_tags]]

# '''Goldberg'''
#: [[content_pages]]
#: [[controller_actions]]
#: [[Delayed_jobs]]
#: [[markup_styles]]
#: [[menu_items]]
#: [[password_resets]]
#: [[permissions]]
#: [[plugin_schema_info]]
#: [[requested_users]]
#: [[roles]]
#: [[roles_permissions]]
#: [[schema_info]]
#: [[schema_migrations]]
#: [[site_controllers]]
#: [[users]]
#: [[user_pastebins]]
#: [[system_settings]]

# '''Reviewing'''
#: [[automated_metareviews]]
#: [[Awarded_badges]]
#: [[Badges]]
#: [[comments]]
#: [[mapping_strategies]]
#: [[responses]]
#: [[response_maps]]
#: [[review_strategies]]
#: [[Review_grades]]
#: [[Review_scores]]
#: [[review_of_review_scores]]
#: [[review_comments_paste_bins]]
#: [[score_caches]]
#: [[scores]]
#: [[suggestions]]
#: [[suggestion_comments]]

#: ''Deprecated Tables''
#:: [[review_feedbacks]]
#:: [[review_mappings]]
#:: [[review_of_review_mappings]]
#:: [[review_of_reviews]]
#:: [[reviews]]
#:: [[teammate_reviews]]

# '''Teammate'''
#: [[Bids]]
#: [[invitations]]
#: [[Join_team_requests]]
#: [[signed_up_teams]]
#: [[teams]]
#: [[teams_users]]

# '''Courses'''
#: [[Courses_table|courses]]
#: [[Courses_users]]

# '''Hierarchy'''
#: [[institutions]]
#: [[languages]]
#: [[sessions]]
#: [[sections]]
#: [[versions]]

# '''Display'''
#: [[nodes]]
#: [[notifications]]
#: [[tree_folders]]
#: [[Track_notifications]]

# '''Questionnaires/Rubrics'''
#: [[question_advices]]
#: [[questionnaires]]
#: [[Questions_table|questions]]
#: [[quiz_question_choices]]
#: ''Deprecated Tables''
#:: [[questionnaire_types]]

# '''Surveys'''
#: [[survey_deployments]]
#: [[survey_responses]]

# '''Other Features'''
#: [[bookmarks]]
#: [[bookmark_ratings]]
#: [[signed_up_users]]
#: [[sign_up_topics]]
#: [[resubmission_times]]
#: [[ta_mappings]]
#: [[Tag_prompts]]
#: [[Tag_prompt_deployments]]

# ''Views''

#: [[score_views]]



Back to [[Expertiza_documentation]] Main page.

Documentation on Database Tables

2018-04-28T00:49:20Z

Psinha:

'''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;

'''FLOWCHART:'''

[[File:FLOWCHART1.JPG]]

'''FINDING REDUNDANT TABLES'''
STEPS:
 1. Write SQL scripts to find the duplicate records. For example in the table,deadline_types a SQL query to find duplicate records is as follows.
 
select name from deadline_types group by name having count(*)>1;
 
Running this query in the SQL prompt, we find that there are two rows with the same information, hence they are redundant.

'''WRITING SCRIPTS TO REGULARIZE THE EXPERTIZA SCHEMA:'''
STEPS:
 1. Write SQL scripts to delete the redundant scripts and tables.For example in the table, <deadline_types> a SQL query to delete the duplicate records are as follows.
 
delete from deadline_types where id not in (select * from (select min(id) from deadline_types group by name) as temp);
 
Running this query in the SQL prompt,it will delete the duplicate records except one.

'''WRITING THE DATABASE MIGRATION SCRIPTS:'''
STEPS:
 1. Write the rails migration scripts to migrate the SQL that would delete the redundant records for certain table.
 The steps to write the rails migration scripts can be explained in the below steps:
 
STEPS:
 1.1 Open a terminal
 1.2 Navigate to the expertiza folder using the command: $cd expertiza
 1.3 Generate a migration script using the command in the terminal: $ rails generate migration RemoveDuplicateDeadlineTypes
 1.4 Write the SQL query to be executed to delete the redundant records inside the migration script.
 1.5 Save the migration script.
 2. The migration scrips are present in the expertiza/db/migrate folder can be migrated using the command rails db:migrate

'''TEST PLAN :'''
STEPS:
 1. Validate the schema expertiza_development
 2. Rerun the sql scripts to find out the redundant records in the tables.It should return null records
 3. Re validate the schema expertiza_development

# '''Answers'''
#: [[Answers]]
#: [[answer_tags]]

# '''Assignments'''
#: [[assignments]]
#: [[assignment_questionnaires]]
#: [[Assignment_badges]]
#: [[calculated_penalties]]
#: [[deadline_types]]
#: [[deadline_rights]]
#: [[due_dates]]
#: [[late_policies]]
#: [[participants]]
#: [[plagiarism_checker_comparisons]]
#: [[plagiarism_checker_assignment_submissions]]
#: [[submission_records]]
#: [[wiki_types]]

#: ''Deprecated Tables''
#:: [[assignments_questionnaires]]

# '''Goldberg'''
#: [[content_pages]]
#: [[controller_actions]]
#: [[Delayed_jobs]]
#: [[markup_styles]]
#: [[menu_items]]
#: [[password_resets]]
#: [[permissions]]
#: [[plugin_schema_info]]
#: [[requested_users]]
#: [[roles]]
#: [[roles_permissions]]
#: [[schema_info]]
#: [[schema_migrations]]
#: [[site_controllers]]
#: [[users]]
#: [[user_pastebins]]
#: [[system_settings]]

# '''Reviewing'''
#: [[automated_metareviews]]
#: [[Awarded_badges]]
#: [[Badges]]
#: [[comments]]
#: [[mapping_strategies]]
#: [[responses]]
#: [[response_maps]]
#: [[review_strategies]]
#: [[Review_grades]]
#: [[Review_scores]]
#: [[review_of_review_scores]]
#: [[review_comments_paste_bins]]
#: [[score_caches]]
#: [[scores]]
#: [[suggestions]]
#: [[suggestion_comments]]

#: ''Deprecated Tables''
#:: [[review_feedbacks]]
#:: [[review_mappings]]
#:: [[review_of_review_mappings]]
#:: [[review_of_reviews]]
#:: [[reviews]]
#:: [[teammate_reviews]]

# '''Teammate'''
#: [[Bids]]
#: [[invitations]]
#: [[Join_team_requests]]
#: [[signed_up_teams]]
#: [[teams]]
#: [[teams_users]]

# '''Courses'''
#: [[Courses_table|courses]]
#: [[Courses_users]]

# '''Hierarchy'''
#: [[institutions]]
#: [[languages]]
#: [[sessions]]
#: [[sections]]
#: [[versions]]

# '''Display'''
#: [[nodes]]
#: [[notifications]]
#: [[tree_folders]]
#: [[Track_notifications]]

# '''Questionnaires/Rubrics'''
#: [[question_advices]]
#: [[questionnaires]]
#: [[Questions_table|questions]]
#: [[quiz_question_choices]]
#: ''Deprecated Tables''
#:: [[questionnaire_types]]

# '''Surveys'''
#: [[survey_deployments]]
#: [[survey_responses]]

# '''Other Features'''
#: [[bookmarks]]
#: [[bookmark_ratings]]
#: [[signed_up_users]]
#: [[sign_up_topics]]
#: [[resubmission_times]]
#: [[ta_mappings]]
#: [[Tag_prompts]]
#: [[Tag_prompt_deployments]]

# ''Views'''

#: [[score_views]]



Back to [[Expertiza_documentation]] Main page.

Documentation on Database Tables

2018-04-28T00:48:59Z

Psinha:

'''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;

'''FLOWCHART:'''

[[File:FLOWCHART1.JPG]]

'''FINDING REDUNDANT TABLES'''
STEPS:
 1. Write SQL scripts to find the duplicate records. For example in the table,deadline_types a SQL query to find duplicate records is as follows.
 
select name from deadline_types group by name having count(*)>1;
 
Running this query in the SQL prompt, we find that there are two rows with the same information, hence they are redundant.

'''WRITING SCRIPTS TO REGULARIZE THE EXPERTIZA SCHEMA:'''
STEPS:
 1. Write SQL scripts to delete the redundant scripts and tables.For example in the table, <deadline_types> a SQL query to delete the duplicate records are as follows.
 
delete from deadline_types where id not in (select * from (select min(id) from deadline_types group by name) as temp);
 
Running this query in the SQL prompt,it will delete the duplicate records except one.

'''WRITING THE DATABASE MIGRATION SCRIPTS:'''
STEPS:
 1. Write the rails migration scripts to migrate the SQL that would delete the redundant records for certain table.
 The steps to write the rails migration scripts can be explained in the below steps:
 
STEPS:
 1.1 Open a terminal
 1.2 Navigate to the expertiza folder using the command: $cd expertiza
 1.3 Generate a migration script using the command in the terminal: $ rails generate migration RemoveDuplicateDeadlineTypes
 1.4 Write the SQL query to be executed to delete the redundant records inside the migration script.
 1.5 Save the migration script.
 2. The migration scrips are present in the expertiza/db/migrate folder can be migrated using the command rails db:migrate

'''TEST PLAN :'''
STEPS:
 1. Validate the schema expertiza_development
 2. Rerun the sql scripts to find out the redundant records in the tables.It should return null records
 3. Re validate the schema expertiza_development

# '''Answers'''
#: [[Answers]]
#: [[answers_tags]]

# '''Assignments'''
#: [[assignments]]
#: [[assignment_questionnaires]]
#: [[Assignment_badges]]
#: [[calculated_penalties]]
#: [[deadline_types]]
#: [[deadline_rights]]
#: [[due_dates]]
#: [[late_policies]]
#: [[participants]]
#: [[plagiarism_checker_comparisons]]
#: [[plagiarism_checker_assignment_submissions]]
#: [[submission_records]]
#: [[wiki_types]]

#: ''Deprecated Tables''
#:: [[assignments_questionnaires]]

# '''Goldberg'''
#: [[content_pages]]
#: [[controller_actions]]
#: [[Delayed_jobs]]
#: [[markup_styles]]
#: [[menu_items]]
#: [[password_resets]]
#: [[permissions]]
#: [[plugin_schema_info]]
#: [[requested_users]]
#: [[roles]]
#: [[roles_permissions]]
#: [[schema_info]]
#: [[schema_migrations]]
#: [[site_controllers]]
#: [[users]]
#: [[user_pastebins]]
#: [[system_settings]]

# '''Reviewing'''
#: [[automated_metareviews]]
#: [[Awarded_badges]]
#: [[Badges]]
#: [[comments]]
#: [[mapping_strategies]]
#: [[responses]]
#: [[response_maps]]
#: [[review_strategies]]
#: [[Review_grades]]
#: [[Review_scores]]
#: [[review_of_review_scores]]
#: [[review_comments_paste_bins]]
#: [[score_caches]]
#: [[scores]]
#: [[suggestions]]
#: [[suggestion_comments]]

#: ''Deprecated Tables''
#:: [[review_feedbacks]]
#:: [[review_mappings]]
#:: [[review_of_review_mappings]]
#:: [[review_of_reviews]]
#:: [[reviews]]
#:: [[teammate_reviews]]

# '''Teammate'''
#: [[Bids]]
#: [[invitations]]
#: [[Join_team_requests]]
#: [[signed_up_teams]]
#: [[teams]]
#: [[teams_users]]

# '''Courses'''
#: [[Courses_table|courses]]
#: [[Courses_users]]

# '''Hierarchy'''
#: [[institutions]]
#: [[languages]]
#: [[sessions]]
#: [[sections]]
#: [[versions]]

# '''Display'''
#: [[nodes]]
#: [[notifications]]
#: [[tree_folders]]
#: [[Track_notifications]]

# '''Questionnaires/Rubrics'''
#: [[question_advices]]
#: [[questionnaires]]
#: [[Questions_table|questions]]
#: [[quiz_question_choices]]
#: ''Deprecated Tables''
#:: [[questionnaire_types]]

# '''Surveys'''
#: [[survey_deployments]]
#: [[survey_responses]]

# '''Other Features'''
#: [[bookmarks]]
#: [[bookmark_ratings]]
#: [[signed_up_users]]
#: [[sign_up_topics]]
#: [[resubmission_times]]
#: [[ta_mappings]]
#: [[Tag_prompts]]
#: [[Tag_prompt_deployments]]

# ''Views'''

#: [[score_views]]



Back to [[Expertiza_documentation]] Main page.

Documentation on Database Tables

2018-04-27T22:03:34Z

Psinha:

'''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;

'''FLOWCHART:'''

[[File:FLOWCHART1.JPG]]

'''FINDING REDUNDANT TABLES'''
STEPS:
 1. Write SQL scripts to find the duplicate records. For example in the table,deadline_types a SQL query to find duplicate records is as follows.
 
select name from deadline_types group by name having count(*)>1;
 
Running this query in the SQL prompt, we find that there are two rows with the same information, hence they are redundant.

'''WRITING SCRIPTS TO REGULARIZE THE EXPERTIZA SCHEMA:'''
STEPS:
 1. Write SQL scripts to delete the redundant scripts and tables.For example in the table, <deadline_types> a SQL query to delete the duplicate records are as follows.
 
delete from deadline_types where id not in (select * from (select min(id) from deadline_types group by name) as temp);
 
Running this query in the SQL prompt,it will delete the duplicate records except one.

'''WRITING THE DATABASE MIGRATION SCRIPTS:'''
STEPS:
 1. Write the rails migration scripts to migrate the SQL that would delete the redundant records for certain table.
 The steps to write the rails migration scripts can be explained in the below steps:
 
STEPS:
 1.1 Open a terminal
 1.2 Navigate to the expertiza folder using the command: $cd expertiza
 1.3 Generate a migration script using the command in the terminal: $ rails generate migration RemoveDuplicateDeadlineTypes
 1.4 Write the SQL query to be executed to delete the redundant records inside the migration script.
 1.5 Save the migration script.
 2. The migration scrips are present in the expertiza/db/migrate folder can be migrated using the command rails db:migrate

'''TEST PLAN :'''
STEPS:
 1. Validate the schema expertiza_development
 2. Rerun the sql scripts to find out the redundant records in the tables.It should return null records
 3. Re validate the schema expertiza_development

# '''Assignments'''
#: [[assignments]]
#: [[assignment_questionnaires]]
#: [[deadline_types]]
#: [[deadline_rights]]
#: [[due_dates]]
#: [[late_policies]]
#: [[participants]]
#: [[wiki_types]]
#: ''Deprecated Tables''
#:: [[assignments_questionnaires]]
# '''Goldberg'''
#: [[content_pages]]
#: [[controller_actions]]
#: [[markup_styles]]
#: [[menu_items]]
#: [[permissions]]
#: [[plugin_schema_info]]
#: [[roles]]
#: [[roles_permissions]]
#: [[schema_info]]
#: [[site_controllers]]
#: [[users]]
#: [[system_settings]]
# '''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]]
# '''Teammate'''
#: [[invitations]]
#: [[teams]]
#: [[teams_users]]
# '''Courses'''
#: [[Courses_table|courses]]
# '''Hierarchy'''
#: [[institutions]]
#: [[languages]]
# '''Display'''
#: [[nodes]]
#: [[tree_folders]]
# '''Questionnaires/Rubrics'''
#: [[question_advices]]
#: [[questionnaires]]
#: [[Questions_table|questions]]
#: ''Deprecated Tables''
#:: [[questionnaire_types]]
# '''Surveys'''
#: [[survey_deployments]]
#: [[survey_responses]]
# '''Other Features'''
#: [[signed_up_users]]
#: [[sign_up_topics]]
#: [[resubmission_times]]
#: [[ta_mappings]]
# '''New Tables'''

#: [[versions]]
#: [[user_pastebins]]
#: [[Track_notifications]]
#: [[Tag_prompts]]
#: [[Tag_prompt_deployments]]
#: [[suggestions]]
#: [[suggestion_comments]]
#: [[submission_records]]
#: [[signed_up_teams]]
#: [[sessions]]
#: [[sections]]
#: [[score_views]]
#: [[schema_migrations]]
#: [[Review_grades]]
#: [[Review_scores]]
#: [[review_of_review_scores]]
#: [[review_comments_paste_bins]]
#: [[requested_users]]
#: [[quiz_question_choices]]
#: [[plagiarism_checker_comparisons]]
#: [[plagiarism_checker_assignment_submissions]]
#: [[password_resets]]
#: [[notifications]]
#: [[Join_team_requests]]
#: [[Delayed_jobs]]
#: [[Courses_users]]
#: [[calculated_penalties]]
#: [[bookmarks]]
#: [[bookmark_ratings]]
#: [[Bids]]
#: [[Badges]]
#: [[Awarded_badges]]
#: [[automated_metareviews]]
#: [[Answers]]
#: [[Assignment_badges]]
#: [[answer_tags]]



Back to [[Expertiza_documentation]] Main page.

Documentation on Database Tables

2018-04-27T21:22:41Z

Psinha:

'''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;

'''FLOWCHART:'''

[[File:FLOWCHART1.JPG]]

'''FINDING REDUNDANT TABLES'''
STEPS:
 1. Write SQL scripts to find the duplicate records. For example in the table,deadline_types a SQL query to find duplicate records is as follows.
 
select name from deadline_types group by name having count(*)>1;
 
Running this query in the SQL prompt, we find that there are two rows with the same information, hence they are redundant.

'''WRITING SCRIPTS TO REGULARIZE THE EXPERTIZA SCHEMA:'''
STEPS:
 1. Write SQL scripts to delete the redundant scripts and tables.For example in the table, <deadline_types> a SQL query to delete the duplicate records are as follows.
 
delete from deadline_types where id not in (select * from (select min(id) from deadline_types group by name) as temp);
 
Running this query in the SQL prompt,it will delete the duplicate records except one.

'''WRITING THE DATABASE MIGRATION SCRIPTS:'''
STEPS:
 1. Write the rails migration scripts to migrate the SQL that would delete the redundant records for certain table.
 The steps to write the rails migration scripts can be explained in the below steps:
 
STEPS:
 1.1 Open a terminal
 1.2 Navigate to the expertiza folder using the command: $cd expertiza
 1.3 Generate a migration script using the command in the terminal: $ rails generate migration RemoveDuplicateDeadlineTypes
 1.4 Write the SQL query to be executed to delete the redundant records inside the migration script.
 1.5 Save the migration script.
 2. The migration scrips are present in the expertiza/db/migrate folder can be migrated using the command rails db:migrate

'''TEST PLAN :'''
STEPS:
 1. Validate the schema expertiza_development
 2. Rerun the sql scripts to find out the redundant records in the tables.It should return null records
 3. Re validate the schema expertiza_development

# '''Assignments'''
#: [[assignments]]
#: [[assignment_questionnaires]]
#: [[deadline_types]]
#: [[deadline_rights]]
#: [[due_dates]]
#: [[late_policies]]
#: [[participants]]
#: [[wiki_types]]
#: ''Deprecated Tables''
#:: [[assignments_questionnaires]]
# '''Goldberg'''
#: [[content_pages]]
#: [[controller_actions]]
#: [[markup_styles]]
#: [[menu_items]]
#: [[permissions]]
#: [[plugin_schema_info]]
#: [[roles]]
#: [[roles_permissions]]
#: [[schema_info]]
#: [[site_controllers]]
#: [[users]]
#: [[system_settings]]
# '''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]]
# '''Teammate'''
#: [[invitations]]
#: [[teams]]
#: [[teams_users]]
# '''Courses'''
#: [[Courses_table|courses]]
# '''Hierarchy'''
#: [[institutions]]
#: [[languages]]
# '''Display'''
#: [[nodes]]
#: [[tree_folders]]
# '''Questionnaires/Rubrics'''
#: [[question_advices]]
#: [[questionnaires]]
#: [[Questions_table|questions]]
#: ''Deprecated Tables''
#:: [[questionnaire_types]]
# '''Surveys'''
#: [[survey_deployments]]
#: [[survey_participants]]
#: [[survey_responses]]
# '''Other Features'''
#: [[signed_up_users]]
#: [[sign_up_topics]]
#: [[resubmission_times]]
#: [[ta_mappings]]
# '''New Tables'''

#: [[versions]]
#: [[user_pastebins]]
#: [[Track_notifications]]
#: [[Tag_prompts]]
#: [[Tag_prompt_deployments]]
#: [[suggestions]]
#: [[suggestion_comments]]
#: [[submission_records]]
#: [[signed_up_teams]]
#: [[sessions]]
#: [[sections]]
#: [[score_views]]
#: [[schema_migrations]]
#: [[Review_grades]]
#: [[Review_scores]]
#: [[review_of_review_scores]]
#: [[review_comments_paste_bins]]
#: [[requested_users]]
#: [[quiz_question_choices]]
#: [[plagiarism_checker_comparisons]]
#: [[plagiarism_checker_assignment_submissions]]
#: [[password_resets]]
#: [[notifications]]
#: [[Join_team_requests]]
#: [[Delayed_jobs]]
#: [[Courses_users]]
#: [[calculated_penalties]]
#: [[bookmarks]]
#: [[bookmark_ratings]]
#: [[Bids]]
#: [[Badges]]
#: [[Awarded_badges]]
#: [[automated_metareviews]]
#: [[Answers]]
#: [[Assignment_badges]]
#: [[answer_tags]]



Back to [[Expertiza_documentation]] Main page.

File:Responses exported.png

2018-04-25T22:49:17Z

Psinha:

Responses

2018-04-25T22:49:05Z

Psinha:

Responses provide a means or communicating information from one user to another about the activity. A response uses a [[response_maps|response map]] to define the communication between a reviewer and a reviewee.

==Response variable documentation==

{| class="wikitable"
!Field Name !!Type !!Description
|-
!id
|int(11)
|The unique record id
|-
!map_id
|int(11)
|The ID of the [[response_maps|response map]] defining the relationship that this response applies to
|-
!additional_comment
|text
|An additional comment provided by the reviewer to support his/her response
|-
!updated_at
|datetime
|The timestamp indicating when this response was last modified
|-
!created_at
|datetime
|The timestamp indicating when this response was created
|-
!version_num
|int(11)
|The version of the review.
|-
!round
|int(11)
|The round the review is connected to.
|-
!is_submitted
|tinyint(1)
|Boolean Field to indicate whether the review is submitted.
|}

== E/R diagram for Parents Tables ==
No Tables were referred by the Resubmission times Table as Foreign Key Relationship.

== E/R diagram for Child Tables ==
Tables referred by the Resubmission times Table as Foreign Key Relationship.

[[File:responses_exported.png]]

Back to [http://wiki.expertiza.ncsu.edu/index.php/Documentation_on_Database_Tables Database Tables] Main page.

File:Resubmission times imported.png

2018-04-25T22:44:24Z

Psinha:

Resubmission times

2018-04-25T22:44:14Z

Psinha:

Designed for support of multi-round [[responses]]. Currently unused

==Resubmission times variable documentation==

{| class="wikitable"
!Field Name !!Type !!Description
|-
!id
|int(11)
|The unique record id
|-
!participant_id
|int(11)
|The [[participants|participant]] submitting material
|-
!resubmitted_at
|datetime
|The timestamp at which the material was resubmitted
|}

== E/R diagram for Parents Tables ==
Tables referred by the Resubmission times Table as Foreign Key Relationship.

[[File:resubmission_times_imported.png]]

== E/R diagram for Child Tables ==
No Tables were referred by the Resubmission times Table as Foreign Key Relationship.

Back to [http://wiki.expertiza.ncsu.edu/index.php/Documentation_on_Database_Tables Database Tables] Main page.

File:Review comment paste imported.png

2018-04-25T22:42:22Z

Psinha:

Review comments paste bins

2018-04-25T22:42:08Z

Psinha: Created page with "Review Comment Paste Bins is just a table to save the data which can be later submitted. '''Deprecated''' ==Review Comment Paste Bins variable documentation== {| class="wikitab..."

Review Comment Paste Bins is just a table to save the data which can be later submitted.
'''Deprecated'''

==Review Comment Paste Bins variable documentation==

{| class="wikitable"
!Field Name !!Type !!Description
|-
!id
|int(11)
|The unique record ID
|-
!review_grade_id
|int(11)
|ID of the grader of the review.
|-
!title
|varchar(255)
|The title of the review.
|-
!review_comment
|text
|Comment provided by the instructor to the reviewer.
|-
!created_at
|datetime
|Date time value when the record was created.
|-
!updated_at
|datetime
|Date time value when the record was updated.
|}

== E/R diagram for Parents Tables ==
Tables referred by the Review Comment Paste Bins Table as Foreign Key Relationship.

[[File:review_comment_paste_imported.png]]

== E/R diagram for Child Tables ==
No Tables were referred by the Review Comment Paste Bins Table as Foreign Key Relationship.

Back to [http://wiki.expertiza.ncsu.edu/index.php/Documentation_on_Database_Tables Database Tables] Main page.

Review grades

2018-04-25T22:38:13Z

Psinha: /* E/R diagram for Child Tables */

Review grades table gives information regarding the grade given to the reviewer for reviewing.

==Review Grades variable documentation==

{| class="wikitable"
!Field Name !!Type !!Description
|-
!id
|int(11)
|The unique record id
|-
!participant_id
|int(11)
|The ID of the [[Participants|participant]] who created the reviewed content.
|-
!grade_for_reviewer
|int(11)
|The grade given to the reviewer.
|-
!comment_for_reviewer
|text
|The comment given by the instructor to the reviewer.
|-
!review_graded_at
|datetime
|The date time value when the review was graded.
|-
!reviewer_id
|int(11)
|The [[Users|user]] performing the review
|}

== E/R diagram for Parents Tables ==
Tables referred by the Review Grades Table as Foreign Key Relationship.

[[File:review_grades_imported.png]]

== E/R diagram for Child Tables ==
Tables referred by the Review Grades Table as Foreign Key Relationship.

[[File:review_grades_exported.png]]

Back to [http://wiki.expertiza.ncsu.edu/index.php/Documentation_on_Database_Tables Database Tables] Main page.

File:Review feedbacks imported.png

2018-04-25T22:37:50Z

Psinha:

Review feedbacks

2018-04-25T22:37:40Z

Psinha:

Contains communciation between an author and a reviewer in an [[Assignments|assignment]]

'''Deprecated'''

==Review feedback variable documentation==

{| class="wikitable"
!Field Name !!Type !!Description
|-
!id
|int(11)
|The unique record ID
|-
!assignment_id
|int(11)
|The [[Assignments|assignment]] to which this review feedback is associated.
|-
!review_id
|int(11)
|The [[Reviews|review]] for which this feedback was created.
|-
!user_id
|int(11)
|The [[Users|user]] who provided the review.
|-
!feedback_at
|datetime
|Meant to contain the timestamp of when the feedback was created. Should use created_at and updated_at.
|-
!txt
|text
|The feedback content
|-
!additional_content
|text
|The feedback conent - needs to be removed
|-
!author_id
|int(11)
|The [[Users|user]] who provided the feedback.
|-
!team_id
|int(11)
|The [[Teams|team]] containing the user who provided the feedback.
|}

== E/R diagram for Parents Tables ==
Tables referred by the Review Feedbacks Table as Foreign Key Relationship.

[[File:review_feedbacks_imported.png]]

== E/R diagram for Child Tables ==
No Tables were referred by the Review Feedbacks Table as Foreign Key Relationship.

Back to [http://wiki.expertiza.ncsu.edu/index.php/Documentation_on_Database_Tables Database Tables] Main page.

File:Review grades imported.png

2018-04-25T22:34:24Z

Psinha:

File:Review grades exported.png

2018-04-25T22:34:14Z

Psinha:

Review grades

2018-04-25T22:34:03Z

Psinha: Created page with "Review grades table gives information regarding the grade given to the reviewer for reviewing. ==Review Grades variable documentation== {| class="wikitable" !Field Name !!Type..."

Review grades table gives information regarding the grade given to the reviewer for reviewing.

==Review Grades variable documentation==

{| class="wikitable"
!Field Name !!Type !!Description
|-
!id
|int(11)
|The unique record id
|-
!participant_id
|int(11)
|The ID of the [[Participants|participant]] who created the reviewed content.
|-
!grade_for_reviewer
|int(11)
|The grade given to the reviewer.
|-
!comment_for_reviewer
|text
|The comment given by the instructor to the reviewer.
|-
!review_graded_at
|datetime
|The date time value when the review was graded.
|-
!reviewer_id
|int(11)
|The [[Users|user]] performing the review
|}

== E/R diagram for Parents Tables ==
Tables referred by the Review Grades Table as Foreign Key Relationship.

[[File:review_grades_imported.png]]

== E/R diagram for Child Tables ==
No Tables were referred by the Review Grades Table as Foreign Key Relationship.

[[File:review_grades_exported.png]]

Back to [http://wiki.expertiza.ncsu.edu/index.php/Documentation_on_Database_Tables Database Tables] Main page.

Review mappings

2018-04-25T22:30:00Z

Psinha:

Maps a connection between the [[participants]]

'''Deprecated'''

==Review mappings variable documentation==

{| class="wikitable"
!Field Name !!Type !!Description
|-
!id
|int(11)
|The unique record id
|-
!author_id
|int(11)
|The [[Participants|participant]] who created the reviewed content
|-
!team_id
|int(11)
|For team [[assignments]] contains the [[Teams|team]] who created the reviewed content
|-
!reviewer_id
|int(11)
|The [[Users|user]] performing the review
|-
!assignment_id
|int(11)
|The [[Assignments|assignment]] content being reviewed
|-
!round
|int(11)
|Preliminary support for multiple rounds of review - not fully implemented
|}

== E/R diagram for Parents Tables ==
Tables referred by the Review Mappings Table as Foreign Key Relationship.

[[File:review_mappings_imported.png]]

== E/R diagram for Child Tables ==
No Tables were referred by the Review Mappings Table as Foreign Key Relationship.

[[File:review_of_mappings_exported.png]]

Back to [http://wiki.expertiza.ncsu.edu/index.php/Documentation_on_Database_Tables Database Tables] Main page.

Review mappings

2018-04-25T22:29:12Z

Psinha:

Maps a connection between the [[participants]]

'''Deprecated'''

==Review mappings variable documentation==

{| class="wikitable"
!Field Name !!Type !!Description
|-
!id
|int(11)
|The unique record id
|-
!author_id
|int(11)
|The [[Participants|participant]] who created the reviewed content
|-
!team_id
|int(11)
|For team [[assignments]] contains the [[Teams|team]] who created the reviewed content
|-
!reviewer_id
|int(11)
|The [[Users|user]] performing the review
|-
!assignment_id
|int(11)
|The [[Assignments|assignment]] content being reviewed
|-
!round
|int(11)
|Preliminary support for multiple rounds of review - not fully implemented
|}

== E/R diagram for Parents Tables ==
Tables referred by the Review Mappings Table as Foreign Key Relationship.

[[File:review_mappings_imported.png]]

== E/R diagram for Child Tables ==
No Tables were referred by the Review Mappings Table as Foreign Key Relationship.

[[File:review_mappings_exported.png]]

Back to [http://wiki.expertiza.ncsu.edu/index.php/Documentation_on_Database_Tables Database Tables] Main page.

File:Review mappings imported.png

2018-04-25T22:28:29Z

Psinha:

File:Review of mappings exported.png

2018-04-25T22:28:18Z

Psinha:

Review of review mappings

2018-04-25T22:26:05Z

Psinha: /* E/R diagram for Child Tables */

Maps a connection between the [[participants]] providing a [[Reviews|review]] and those providing a metareview/review of review

'''Deprecated'''

==Metareview/Review of review mappings variable documentation==

{| class="wikitable"
!Field Name !!Type !!Description
|-
!id
|int(11)
|The unique record id
|-
!review_reviewer_id
|int(10)
|The [[Participants|participant]] who is creating the metareview - needs to be depracated.
|-
!review_mapping_id
|int(11)
|The [[Review_mappings|review_mapping]] which defines the relationship between author/team and reviewer.
|}

== E/R diagram for Parents Tables ==
No Tables were referred by the Review of Review Mappings Table as Foreign Key Relationship.

== E/R diagram for Child Tables ==
Tables referred by the Review of Reviews Mappings Table as Foreign Key Relationship.

[[File:review_of_reviews_imported.png]]

Back to [http://wiki.expertiza.ncsu.edu/index.php/Documentation_on_Database_Tables Database Tables] Main page.

Review of review mappings

2018-04-25T22:24:20Z

Psinha: /* E/R diagram for Child Tables */

Maps a connection between the [[participants]] providing a [[Reviews|review]] and those providing a metareview/review of review

'''Deprecated'''

==Metareview/Review of review mappings variable documentation==

{| class="wikitable"
!Field Name !!Type !!Description
|-
!id
|int(11)
|The unique record id
|-
!review_reviewer_id
|int(10)
|The [[Participants|participant]] who is creating the metareview - needs to be depracated.
|-
!review_mapping_id
|int(11)
|The [[Review_mappings|review_mapping]] which defines the relationship between author/team and reviewer.
|}

== E/R diagram for Parents Tables ==
No Tables were referred by the Review of Review Mappings Table as Foreign Key Relationship.

== E/R diagram for Child Tables ==
Tables referred by the Review of Reviews Mappings Table as Foreign Key Relationship.

[[File:review_of_review_mappings_imported.png]]

Back to [http://wiki.expertiza.ncsu.edu/index.php/Documentation_on_Database_Tables Database Tables] Main page.

Review of review mappings

2018-04-25T22:24:01Z

Psinha:

Maps a connection between the [[participants]] providing a [[Reviews|review]] and those providing a metareview/review of review

'''Deprecated'''

==Metareview/Review of review mappings variable documentation==

{| class="wikitable"
!Field Name !!Type !!Description
|-
!id
|int(11)
|The unique record id
|-
!review_reviewer_id
|int(10)
|The [[Participants|participant]] who is creating the metareview - needs to be depracated.
|-
!review_mapping_id
|int(11)
|The [[Review_mappings|review_mapping]] which defines the relationship between author/team and reviewer.
|}

== E/R diagram for Parents Tables ==
No Tables were referred by the Review of Review Mappings Table as Foreign Key Relationship.

== E/R diagram for Child Tables ==
No Tables were referred by the Review of Reviews Mappings Table as Foreign Key Relationship.

[[File:review_of_review_mappings_imported.png]]

Back to [http://wiki.expertiza.ncsu.edu/index.php/Documentation_on_Database_Tables Database Tables] Main page.

File:Review of review scores imported.png

2018-04-25T22:21:49Z

Psinha:

Review of review scores

2018-04-25T22:21:40Z

Psinha: Created page with "Review of Reviews scores gives information regarding the scores given by the instructor to the review of the reviews. ==Review of Reviews Scores variable documentation== {| cla..."

Review of Reviews scores gives information regarding the scores given by the instructor to the review of the reviews.

==Review of Reviews Scores variable documentation==

{| class="wikitable"
!Field Name !!Type !!Description
|-
!id
|int(11)
|The unique record id
|-
!review_of_review_id
|int(11)
|ID of the Review given to the review.
|-
!question_id
|int(11)
|ID of the question associated with the Review.
|-
!score
|int(11)
|Score given to that Review.
|-
!comments
|text
|Comments given by the instructor.
|}

== E/R diagram for Parents Tables ==
Tables referred by the Review of Reviews Scores Table as Foreign Key Relationship.

[[File:review_of_review_scores_imported.png]]

== E/R diagram for Child Tables ==
No Tables were referred by the Review of Reviews Scores Table as Foreign Key Relationship.

Back to [http://wiki.expertiza.ncsu.edu/index.php/Documentation_on_Database_Tables Database Tables] Main page.

File:Review of reviews imported.png

2018-04-25T22:18:23Z

Psinha:

File:Review of reviews exported.png

2018-04-25T22:18:13Z

Psinha:

Review of reviews

2018-04-25T22:18:02Z

Psinha:

Contains metareview definitions for each of the reviews given.

'''Deprecated'''

== Metareview/Review of review variable documentation==

{| class="wikitable"
!Field Name !!Type !!Description
|-
!id
|int(11)
|The unique record id
|-
!reviewed_at
|datetime
|Meant to contain the time stamp for when the review of review was created. Should be deprecated. Use created_at instead.
|-
!review_of_review_mapping_id
|int(11)
|The ID for a [[Review_of_review_mappings|review of review mapping]]
|-
!review_num_for_author
|int(11)
|Number of authors who recieved the review.
|-
!review_num_for_reviewer
|int(11)
|Number of reviewers who reviewed.
|}

== E/R diagram for Parents Tables ==
Tables referred by the Review of Reviews Table as Foreign Key Relationship.

[[File:review_of_reviews_imported.png]]

== E/R diagram for Child Tables ==
Tables referred by the Review of Reviews Table as Foreign Key Relationship.

[[File:review_of_reviews_exported.png]]

Back to [http://wiki.expertiza.ncsu.edu/index.php/Documentation_on_Database_Tables Database Tables] Main page.

File:Review scores imported.png

2018-04-25T22:14:04Z

Psinha:

Review scores

2018-04-25T22:13:54Z

Psinha: Created page with "Review scores gives information regarding the scores given by the instructor to the reviews. ==Review Scores variable documentation== {| class="wikitable" !Field Name !!Type !..."

Review scores gives information regarding the scores given by the instructor to the reviews.

==Review Scores variable documentation==

{| class="wikitable"
!Field Name !!Type !!Description
|-
!id
|int(11)
|The unique record id
|-
!review_id
|int(11)
|ID of the Review.
|-
!question_id
|int(11)
|ID of the question associated with the Review.
|-
!score
|int(11)
|Score given to that Review.
|-
!comments
|text
|Comments given by the instructor.
|-
!questionnaire_type_id
|int(11)
|ID of the questionnaire the question is associated to.
|}

== E/R diagram for Parents Tables ==
Tables referred by the Review Scores Table as Foreign Key Relationship.

[[File:review_scores_imported.png]]

== E/R diagram for Child Tables ==
No Tables were referred by the Review Scores Table as Foreign Key Relationship.

Back to [http://wiki.expertiza.ncsu.edu/index.php/Documentation_on_Database_Tables Database Tables] Main page.

Review strategies

2018-04-25T22:09:20Z

Psinha:

Review strategies gives information regarding different strategies for reviewing.

==Review Strategies variable documentation==

{| class="wikitable"
!Field Name !!Type !!Description
|-
!id
|int(11)
|The unique record id
|-
!name
|varchar(255)
|The strategy name
|}

== E/R diagram for Parents Tables ==
No Tables were referred by the Review Strategies Table as Foreign Key Relationship.

== E/R diagram for Child Tables ==
No Tables were referred by the Review Strategies Table as Foreign Key Relationship.

Back to [http://wiki.expertiza.ncsu.edu/index.php/Documentation_on_Database_Tables Database Tables] Main page.

File:Reviews imported.png

2018-04-25T22:07:13Z

Psinha:

File:Reviews exported.png

2018-04-25T22:07:02Z

Psinha:

Reviews

2018-04-25T22:06:12Z

Psinha:

Reviews provide a means or communicating information from one user to another about the submission content.

'''Deprecated'''

==Reviews variable documentation==

{| class="wikitable"
!Field Name !!Type !!Description
|-
!id
|int(11)
|The unique record id
|-
!review_mapping_id
|int(11)
|The ID of the [[Review_mappings|review mapping]] used to define the relationship between and author/team and a reviewer
|-
!review_num_for_author
|int(11)
|(Unused at present?) This is supposed to be the review number, as seen by the author. [Should be changed to review_num_for_creator]
|-
!review_num_for_reviewer
|int(11)
|(Unused at present?) This is supposed to be the review number, as seen by the reviewer. Normally for non-team assignments, it will be the same as the review_num_for_author. For team assignments, it often differs from review_num_for_author, because the creator receives more reviews than each individual reviewer creates.
|-
!ignore
|tinyint(4)
|Designate that a given review is not included in the score. May be unused
|-
!additional_comment
|text
|An additional comment provided by the reviewer to support his/or her review content
|-
!updated_at
|datetime
|The timestamp indicating when this review was last modified
|-
!created_at
|datetime
|The timestamp indicating when this review was created
|}

== E/R diagram for Parents Tables ==
Tables referred by the Reviews Table as Foreign Key Relationship.

[[File:reviews_imported.png]]

== E/R diagram for Child Tables ==
Tables referred by the Reviews Table as Foreign Key Relationship.

[[File:reviews_exported.png]]

Back to the [[Documentation_on_Database_Tables|database documentation]]

Roles

2018-04-25T22:03:31Z

Psinha:

The Roles table gives information regarding different user roles.
== Roles Variable Documentation ==

{| class="wikitable"
!Name !!Datatype !!Description
|-
!id
|int(11)
|Primary key of the entry in table, auto increments by default
|-
!name
|varchar(255)
|Name of the role detailed
|-
!parent_id
|int(11)
|The role that is created by this particular user; By default, students may not be parents of any role.
|-
!description
|varchar(255)
|The description associated with the nature of the role
|-
!default_page_id
|int(11)
|NULL at the moment, the default page_id that is displayed to the user, depending on the role
|-
!cache
|text
|Cache storage information
|-
!created_at
|datetime
|Time stamp of the date created
|-
!updated_at
|datetime
|Time stamp of the date updated.
|}

== E/R diagram for Parents Tables ==
No Tables were referred by the Roles Table as Foreign Key Relationship.

== E/R diagram for Child Tables ==
No Tables were referred by the Roles Table as Foreign Key Relationship.

Back to [http://wiki.expertiza.ncsu.edu/index.php/Documentation_on_Database_Tables Database Tables] Main page.

Roles

2018-04-25T22:03:17Z

Psinha:

Submission records

2018-04-25T00:20:55Z

Psinha:

The Submission Records table gives information regarding submissions done which are associated with a particular assignment ID.
== Submission Records Variable Documentation ==

{| class="wikitable"
!Name !!Datatype !!Description
|-
!id
|int(11)
|Primary key of the entry in table, auto increments by default
|-
!created_at
|datetime
|Date time value when the record was created.
|-
!updated_at
|datetime
|Date time value when the record was updated.
|-
!type
|text
|Type description of the Submission record.
|-
!content
|varchar(255)
|Content of the submission record.
|-
!operation
|varchar(255)
|Operation allowed on the record.
|-
!team_id
|int(11)
|Team ID associated with this submission.
|-
!user
|vharchar(255)
|User who did the submission.
|-
!assignment_id
|int(11)
|ID of the assignment the submission is associated to.
|}

== E/R diagram for Parents Tables ==
No Tables were referred by the Submission Records Table as Foreign Key Relationship.

== E/R diagram for Child Tables ==
No Tables were referred by the Submission Records Table as Foreign Key Relationship.

Back to [http://wiki.expertiza.ncsu.edu/index.php/Documentation_on_Database_Tables Database Tables] Main page.

Submission records

2018-04-25T00:20:16Z

Psinha: Created page with "The Submission Records table gives information regarding controllers with each of their permissions associated to it. == Submission Records Variable Documentation == {| class="w..."

The Submission Records table gives information regarding controllers with each of their permissions associated to it.
== Submission Records Variable Documentation ==

{| class="wikitable"
!Name !!Datatype !!Description
|-
!id
|int(11)
|Primary key of the entry in table, auto increments by default
|-
!created_at
|datetime
|Date time value when the record was created.
|-
!updated_at
|datetime
|Date time value when the record was updated.
|-
!type
|text
|Type description of the Submission record.
|-
!content
|varchar(255)
|Content of the submission record.
|-
!operation
|varchar(255)
|Operation allowed on the record.
|-
!team_id
|int(11)
|Team ID associated with this submission.
|-
!user
|vharchar(255)
|User who did the submission.
|-
!assignment_id
|int(11)
|ID of the assignment the submission is associated to.
|}

== E/R diagram for Parents Tables ==
No Tables were referred by the Submission Records Table as Foreign Key Relationship.

== E/R diagram for Child Tables ==
No Tables were referred by the Submission Records Table as Foreign Key Relationship.

Back to [http://wiki.expertiza.ncsu.edu/index.php/Documentation_on_Database_Tables Database Tables] Main page.

Signed up teams

2018-04-25T00:16:08Z

Psinha: /* E/R diagram for Child Tables */

The Signed Up Teams table gives information regarding teams that are Signed Up.
== Signed Up Teams Variable Documentation ==

{| class="wikitable"
!Name !!Datatype !!Description !
|-
!id
|int(11)
|Unique ID for each of the record. Primary Key
|-
!topic_id
|int(11)
|ID of the topic the team is associated with.
|-
!team_id
|int(11)
|ID of the team.
|-
!is_waitlisted
|tinyint(1)
|Boolean Field to indicate whether the team is waitlisted or not.
|-
!preference_priority_number
|int(11)
|Priority level for this Topic assigned by the team.
|}

== E/R diagram for Parents Tables ==
Tables referred by the Signed Up Teams Table as Foreign Key Relationship.

[[File:signed_up_teams_imported.png]]

== E/R diagram for Child Tables ==
No Tables were referred by the Signed Up Teams Table as Foreign Key Relationship.

Back to [http://wiki.expertiza.ncsu.edu/index.php/Documentation_on_Database_Tables Database Tables] Main page.

Site controllers

2018-04-25T00:15:41Z

Psinha: /* E/R diagram for Child Tables */

The Site Controllers table gives information regarding controllers with each of their permissions associated to it.
== Site Controllers Variable Documentation ==

{| class="wikitable"
!Name !!Datatype !!Description
|-
!id
|int(11)
|Primary key of the entry in table, auto increments by default
|-
!name
|varchar(255)
|Names of the site_controllers provisioned; site-controllers are tables such as content_pages(typically the functions of a control panel)
|-
!permission_id
|int(11)
|The permission with which the controller is available.
|-
!builtin
|int(11)
|If the controller was builtin or was added later
|}

== E/R diagram for Parents Tables ==
No Tables were referred by the Site Controllers Table as Foreign Key Relationship.

== E/R diagram for Child Tables ==
No Tables were referred by the Site Controllers Table as Foreign Key Relationship.

Back to [http://wiki.expertiza.ncsu.edu/index.php/Documentation_on_Database_Tables Database Tables] Main page.

Site controllers

2018-04-25T00:14:17Z

Psinha: /* Site Controllers Variable Documentation */

The Site Controllers table gives information regarding controllers with each of their permissions associated to it.
== Site Controllers Variable Documentation ==

{| class="wikitable"
!Name !!Datatype !!Description
|-
!id
|int(11)
|Primary key of the entry in table, auto increments by default
|-
!name
|varchar(255)
|Names of the site_controllers provisioned; site-controllers are tables such as content_pages(typically the functions of a control panel)
|-
!permission_id
|int(11)
|The permission with which the controller is available.
|-
!builtin
|int(11)
|If the controller was builtin or was added later
|}

== E/R diagram for Parents Tables ==
No Tables were referred by the Site Controllers Table as Foreign Key Relationship.

== E/R diagram for Child Tables ==
No Tables were eferred by the Signed Up Teams Table as Foreign Key Relationship.

Back to [http://wiki.expertiza.ncsu.edu/index.php/Documentation_on_Database_Tables Database Tables] Main page.

Site controllers

2018-04-25T00:13:53Z

Psinha:

The Site Controllers table gives information regarding controllers with each of their permissions associated to it.
== Site Controllers Variable Documentation ==

{| class="wikitable"
!Name !!Datatype !!Description
|-
!id
|int(11)
|Primary key of the entry in table, auto increments by default
|-
!name
|varchar(255)
|Names of the site_controllers provisioned; site-controllers are tables such as content_pages(typically the functions of a control panel)
|-
!permission_id
|int(11)
|The permission with which the controller is available to: FK into the PERMISSIONS table
|-
!builtin
|int(11)
|If the controller was builtin or was added later
|}

== E/R diagram for Parents Tables ==
No Tables were referred by the Site Controllers Table as Foreign Key Relationship.

== E/R diagram for Child Tables ==
No Tables were eferred by the Signed Up Teams Table as Foreign Key Relationship.

Back to [http://wiki.expertiza.ncsu.edu/index.php/Documentation_on_Database_Tables Database Tables] Main page.

File:Signed up teams imported.png

2018-04-25T00:11:44Z

Psinha:

Signed up teams

2018-04-25T00:11:36Z

Psinha: Created page with "The Signed Up Teams table gives information regarding teams that are Signed Up. == Signed Up Teams Variable Documentation == {| class="wikitable" !Name !!Datatype !!Description..."

The Signed Up Teams table gives information regarding teams that are Signed Up.
== Signed Up Teams Variable Documentation ==

{| class="wikitable"
!Name !!Datatype !!Description !
|-
!id
|int(11)
|Unique ID for each of the record. Primary Key
|-
!topic_id
|int(11)
|ID of the topic the team is associated with.
|-
!team_id
|int(11)
|ID of the team.
|-
!is_waitlisted
|tinyint(1)
|Boolean Field to indicate whether the team is waitlisted or not.
|-
!preference_priority_number
|int(11)
|Priority level for this Topic assigned by the team.
|}

== E/R diagram for Parents Tables ==
Tables referred by the Signed Up Teams Table as Foreign Key Relationship.

[[File:signed_up_teams_imported.png]]

== E/R diagram for Child Tables ==
No Tables were eferred by the Signed Up Teams Table as Foreign Key Relationship.

Back to [http://wiki.expertiza.ncsu.edu/index.php/Documentation_on_Database_Tables Database Tables] Main page.

Sign up topics

2018-04-25T00:08:54Z

Psinha: /* Sign Up Topics Variable Documentation */

The Sign Up Topics table gives information regarding topics that are associated to a particular assignment.
== Sign Up Topics Variable Documentation ==

{| class="wikitable"
!Name !!Datatype !!Description !
|-
!id
|int(11)
|Unique ID for each of the record. Primary Key
|-
!topic_name
|text
|Name of the topic.
|-
!assignment_id
|int(11)
|ID of the assignment the topic is associated with.
|-
!max_choosers
|int(11)
|Number of people that can take this particular topic.
|-
!category
|text
|Category this topic belongs to.
|-
!topic_identifier
|varchar(10)
|Identifier for each of the topics.
|-
!micropayment
|int(11)
|Micropayment value for the topic. ********************
|-
!private_to
|int(11)
|ID of the User this topic is private to.
|-
!description
|text
|Description of the Topic.
|-
!link
|varchar(255)
|URL of the Topic Details Page.
|}

== E/R diagram for Parents Tables ==
Tables referred by the Sign Up Topics Table as Foreign Key Relationship.

[[File:sign_up_topics_imported.png]]

== E/R diagram for Child Tables ==
Tables referred by the Sign Up Topics Table as Foreign Key Relationship.

[[File:sign_up_topics_exported.png]]

Back to [http://wiki.expertiza.ncsu.edu/index.php/Documentation_on_Database_Tables Database Tables] Main page.

File:Sign up topics imported.png

2018-04-25T00:05:42Z

Psinha:

File:Sign up topics exported.png

2018-04-25T00:05:21Z

Psinha: