Expertiza_Wiki - User contributions [en]

Questionnaires

2025-12-09T05:41:15Z

Bvgowda:

==Questionnaires documentation (Reimplementation)==
{| class="wikitable"
!Field Name !!Type !!Description
|-
!id
|int(11)
|This object's unique ID value. One per object.
|-
!name
|varchar(64)
|name of the questionnaire
|-
!instructor_id
|int(11)
|id of instructor who created the questionnaire
|-
!private
|tinyint(1)
|whether questionnaire is visible to other instructors
|-
!min_question_score
|int(11)
|the minimum score that the reviewer can give for a question in this questionnaire
|-
!max_question_score
|int(11)
|the maximum score that the reviewer can give for a question in this questionnaire
|-
!created_at
|datetime
|the date and time at which the questionnaire was created at
|-
!updated_at
|datetime
|the date and time at which the questionnaire was last updated
|-
!default_num_choices
|int(11)
|default number of scoring increments
|-
!type
|varchar(255)
|Subclassing for the questionnaire. Possible types are ReviewQuestionnaire, MetareviewQuestionnaire, AuthorFeedbackQuestionnaire, QuizQuestionniare, SurveyQuestionnaire, CourseEvaluationQuestionnaire, TeammateReviewQuestionnaire, GlobalSurveyQuestionnaire
|-
!instruction_loc
|TEXT
|
|}
==Questionnaires documentation (2023 version)==
{| class="wikitable"
!Field Name !!Type !!Description
|-
!id
|int(11)
|This object's unique ID value. One per object.
|-
!name
|varchar(64)
|name of the questionnaire
|-
!instructor_id
|int(11)
|id of instructor who created the questionnaire
|-
!private
|tinyint(1)
|whether questionnaire is visible to other instructors
|-
!min_question_score
|int(11)
|the minimum score that the reviewer can give for a question in this questionnaire
|-
!max_question_score
|int(11)
|the maximum score that the reviewer can give for a question in this questionnaire
|-
!created_at
|datetime
|the date and time at which the questionnaire was created at
|-
!updated_at
|datetime
|the date and time at which the questionnaire was last updated
|-
!default_num_choices
|int(11)
|default number of scoring increments
|-
!type
|varchar(255)
|Subclassing for the questionnaire. Possible types are ReviewQuestionnaire, MetareviewQuestionnaire, AuthorFeedbackQuestionnaire, QuizQuestionniare, SurveyQuestionnaire, CourseEvaluationQuestionnaire, TeammateReviewQuestionnaire, GlobalSurveyQuestionnaire
|-
!display_type
|varchar(255)
|Character representation of type used in tree display. Possible values are Review, Metareview, AuthorFeedback, Survey, CourseEvaluation, TeammateReview GlobalSurvey
|-
!instruction_loc
|TEXT
|
|}

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

Documentation on Database Tables

2025-12-09T05:30:34Z

Bvgowda:

'''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]]
#: [[deadline_types]]
#: [[deadline_rights]]
#: [[due_dates]]
#: [[late_policies]]
#: [[participants]]
#: [[submission_records]]
#: [[wiki_types]]
#: ''Deprecated Tables''
#:: [[assignments_questionnaires]]
#:: [[calculated_penalties]]
#:: [[plagiarism_checker_assignment_submissions]]
#:: [[plagiarism_checker_comparisons]]
# '''Answers'''
#: [[answers]]
#: [[answer_tags]]
# '''Goldberg'''
#: [[password_resets]]
#: [[permissions]]
#: [[plugin_schema_info]]
#: [[requested_users]]
#: [[roles]]
#: [[roles_permissions]]
#: [[schema_info]]
#: [[schema_migrations]]
#: [[users]]
#: [[user_pastebins]]
#: ''Deprecated Tables''
#:: [[site_controllers]]
#:: [[controller_actions]]
#:: [[delayed_jobs]]
#:: [[content_pages]]
#:: [[markup_styles]]
#:: [[menu_items]]
#:: [[system_settings]]
# '''Reviewing'''
#: [[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''
#:: [[automated_metareviews]]
#:: [[badges]]
#:: [[awarded_badges]]
#:: [[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]]
# '''Hierarchy'''
#: [[institutions]]
#: [[languages]]
#: [[sessions]]
#: [[versions]]
#: ''Deprecated Tables''
#:: [[sections]]
# '''Display'''
#: [[nodes]]
#: [[notifications]]
#: [[tree_folders]]
#: [[track_notifications]]
#: ''Deprecated Tables''
#:: [[notifications]]
# '''Questionnaires/Rubrics'''
#: [[question_advices]]
#: [[questionnaires]]
#: [[questions_table|questions]]
#: [[quiz_question_choices]]
#: [[questionnaire_types]]
# '''Surveys'''
#: [[survey_deployments]]
#: [[survey_responses]]
# '''Other Features'''
#: [[bookmarks]]
#: [[bookmark_ratings]]
#: [[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

2025-12-09T05:29:47Z

Bvgowda:

'''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]]
#: [[deadline_types]]
#: [[deadline_rights]]
#: [[due_dates]]
#: [[late_policies]]
#: [[participants]]
#: [[submission_records]]
#: [[wiki_types]]
#: ''Deprecated Tables''
#:: [[assignments_questionnaires]]
#:: [[calculated_penalties]]
#:: [[plagiarism_checker_assignment_submissions]]
#:: [[plagiarism_checker_comparisons]]
# '''Answers'''
#: [[answers]]
#: [[answer_tags]]
# '''Goldberg'''
#: [[password_resets]]
#: [[permissions]]
#: [[plugin_schema_info]]
#: [[requested_users]]
#: [[roles]]
#: [[roles_permissions]]
#: [[schema_info]]
#: [[schema_migrations]]
#: [[users]]
#: [[user_pastebins]]
#: ''Deprecated Tables''
#:: [[site_controllers]]
#:: [[controller_actions]]
#:: [[delayed_jobs]]
#:: [[content_pages]]
#:: [[markup_styles]]
#:: [[menu_items]]
#:: [[system_settings]]
# '''Reviewing'''
#: [[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''
#:: [[automated_metareviews]]
#:: [[badges]]
#:: [[awarded_badges]]
#:: [[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_participants]]
# '''Courses'''
#: [[courses_table|courses]]
# '''Hierarchy'''
#: [[institutions]]
#: [[languages]]
#: [[sessions]]
#: [[versions]]
#: ''Deprecated Tables''
#:: [[sections]]
# '''Display'''
#: [[nodes]]
#: [[notifications]]
#: [[tree_folders]]
#: [[track_notifications]]
#: ''Deprecated Tables''
#:: [[notifications]]
# '''Questionnaires/Rubrics'''
#: [[question_advices]]
#: [[questionnaires]]
#: [[questions_table|questions]]
#: [[quiz_question_choices]]
#: [[questionnaire_types]]
# '''Surveys'''
#: [[survey_deployments]]
#: [[survey_responses]]
# '''Other Features'''
#: [[bookmarks]]
#: [[bookmark_ratings]]
#: [[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

2025-12-09T05:27:17Z

Bvgowda:

Questionnaire types

2025-12-09T05:26:39Z

Bvgowda:

{| class="wikitable"
!Field Name !!Type !!Description
|-
!id
|int(11)
|id of the questionnaire type
|-
!display_type
|varchar(255)
|specifies the type information of the questionnaire For Ex:Rubric,Survey,Global Survey etc.
|}

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

Notifications

2025-12-09T05:23:57Z

Bvgowda:

Sections

2025-12-09T05:23:43Z

Bvgowda:

Review feedbacks

2025-12-09T05:22:42Z

Bvgowda:

<div style="background-color: #ffcccc; border: 1px solid #cc0000; padding: 10px; margin-bottom: 20px; text-align: center;">
'''⚠ DEPRECATED: This table has been removed from the database in the latest release. This documentation is retained for historical reference only.'''
</div>
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.

Automated metareviews

2025-12-09T05:22:18Z

Bvgowda:

<div style="background-color: #ffcccc; border: 1px solid #cc0000; padding: 10px; margin-bottom: 20px; text-align: center;">
'''⚠ DEPRECATED: This table has been removed from the database in the latest release. This documentation is retained for historical reference only.'''
</div>
This table has meta values for each of the reponses in the Reponses table to indicate whether the review has Summary, Problem, Tone etc.
== Automated Metareviews Variable Documentation ==

{| class="wikitable"
!Field Name !!Type !!Description
|-
!id
|int(11)
|The unique record id
|-
!relevance
|float
|This gives the float value for the relevance of the metareviews
|-
!content_summative
|float
|This gives the float value for how much the review is categorised as Summary.
|-
!content_problem
|float
|This gives the float value for how much the review is categorised as Problem.
|-
!content_advisory
|float
|This gives the float value for how much the review is categorised as Advice.
|-
!tone_positive
|float
|This gives the float value for the Positive tone of the review.
|-
!tone_negative
|float
|This gives the float value for the Negative tone of the review.
|-
!tone_neutral
|float
|This gives the float value for the Neutral tone of the review.
|-
!quantity
|int(11)
|This gives the quantity(word count) of the review.
|-
!plagiarism
|tinyint(1)
|Boolean field to indicate whether the review is plagiarised or not.
|-
!version_num
|int(11)
|This gives the version number of the review.
|-
!response_id
|int(11)
|This is Foreign key reference to the Response table (id).
|-
!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 Automated Metareviews Table as Foreign Key Relationship.

[[File:automated_metareviews_imported.png]]

== E/R diagram for Child Tables ==
No Tables refer the Automated Metareviews Table as Foreign Key Relationship.

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

Content pages

2025-12-09T05:21:39Z

Bvgowda:

<div style="background-color: #ffcccc; border: 1px solid #cc0000; padding: 10px; margin-bottom: 20px; text-align: center;">
'''⚠ DEPRECATED: This table has been removed from the database in the latest release. This documentation is retained for historical reference only.'''
</div>
The Content Pages table gives information regarding the Content in each of the pages of Expertiza.
== Content Pages Variable Documentation ==

{| class="wikitable"
!Name !!Datatype !!Description
|-
!id
|int(11)
|Primary key of the entry in table, auto increments by default
|-
!title
|varchar(255)
|Title of the page being referred to; for display in the browser
|-
!name
|varchar(255)
|Name identifier of the page.
|-
!markup_style_id
|int(11)
|The id of the markup style used in the page; FK into the MARKUP_STYLES table
|-
!content
|text
|HTML based content of the page
|-
!permission_id
|int(11)
|Specifies the permission level to which this page is associated; FK into the permissions table.
|-
!created_at
|datetime
|Time stamp of date this page was created
|-
!updated_at
|datetime
|Time stamp of date this page was last modified.
|-
!content_cache
|text
|Cache storage information
|}

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

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

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

System settings

2025-12-09T05:20:50Z

Bvgowda:

Markup styles

2025-12-09T05:20:28Z

Bvgowda:

Controller actions

2025-12-09T05:20:05Z

Bvgowda:

Site controllers

2025-12-09T05:19:52Z

Bvgowda:

Plagiarism checker comparisons

2025-12-09T05:19:33Z

Bvgowda:

Plagiarism checker assignment submissions

2025-12-09T05:19:18Z

Bvgowda:

Assignments questionnaires

2025-12-09T05:19:00Z

Bvgowda:

<div style="background-color: #ffcccc; border: 1px solid #cc0000; padding: 10px; margin-bottom: 20px; text-align: center;">
'''⚠ DEPRECATED: This table has been removed from the database in the latest release. This documentation is retained for historical reference only.'''
</div>
'''Deprecated'''
== Assignments Questionnaire Variable Documentation ==

{| class="wikitable"
!Field Name !!Type !!Description
|-
!id
|int(11)
|The unique record id
|-
!questionnaire_id
|int(11)
|This references a questionnaire that is used in t he assignment
|-
!assignment_id
|int(11)
|This references the assignment in which the questionnaire is used
|-
!notification_limit
|int
|If a new review has a score that is more than this # of percentage points away from the current average review score for this artifact, then the instructor will be emailed.
|-
!questionnaire_weight
|int
|Gives the percentage of the contributor's overall score that is based on this questionnaire.
|-
!used_in_round
|int
|Tells which round (1, 2, ...) of review this questionnaire is used in. If null, I suspect that the questionnaire is used in all rounds.
|-
!dropdown
|tinyint(1)
|I believe that if this is true, instead of using a rubric to evaluate this kind of work (e.g., review of work, teammate review), a simple dropdown with integers from 1 to MAX_SCORE is used instead.
|-
!topic_id
|int
|If this field is non-null, then this rubric is used only to review this particular topic.
|-
!duty_id
|int
|If this is non-null, then this rubric is used only to review a team member who takes on a particular role (such as scrum master, tester, or documentor).
|-
|}

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

[[File:assignments_questionnaires_imported.png]]

== E/R diagram for Child Tables ==
No Tables refer the Assignment Badges Table as Foreign Key Relationship.

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

Documentation on Database Tables

2025-12-09T05:15:49Z

Bvgowda:

'''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]]
#: [[deadline_types]]
#: [[deadline_rights]]
#: [[due_dates]]
#: [[late_policies]]
#: [[participants]]
#: [[submission_records]]
#: [[wiki_types]]
#: ''Deprecated Tables''
#:: [[assignments_questionnaires]]
#:: [[calculated_penalties]]
#:: [[plagiarism_checker_assignment_submissions]]
#:: [[plagiarism_checker_comparisons]]
# '''Answers'''
#: [[answers]]
#: [[answer_tags]]
# '''Goldberg'''
#: [[password_resets]]
#: [[permissions]]
#: [[plugin_schema_info]]
#: [[requested_users]]
#: [[roles]]
#: [[roles_permissions]]
#: [[schema_info]]
#: [[schema_migrations]]
#: [[users]]
#: [[user_pastebins]]
#: ''Deprecated Tables''
#:: [[site_controllers]]
#:: [[controller_actions]]
#:: [[delayed_jobs]]
#:: [[content_pages]]
#:: [[markup_styles]]
#:: [[menu_items]]
#:: [[system_settings]]
# '''Reviewing'''
#: [[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''
#:: [[automated_metareviews]]
#:: [[badges]]
#:: [[awarded_badges]]
#:: [[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]]
# '''Hierarchy'''
#: [[institutions]]
#: [[languages]]
#: [[sessions]]
#: [[versions]]
#: ''Deprecated Tables''
#:: [[sections]]
# '''Display'''
#: [[nodes]]
#: [[notifications]]
#: [[tree_folders]]
#: [[track_notifications]]
#: ''Deprecated Tables''
#:: [[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]]
#: [[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

2025-12-09T04:40:47Z

Bvgowda:

'''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_badges]]
#: [[assignment_questionnaires]]
#: [[deadline_rights]]
#: [[deadline_types]]
#: [[due_dates]]
#: [[late_policies]]
#: [[participants]]
#: [[submission_records]]
#: [[wiki_types]]
#: ''Deprecated Tables''
#:: [[assignments_questionnaires]]
#:: [[calculated_penalties]]
#:: [[plagiarism_checker_assignment_submissions]]
#:: [[plagiarism_checker_comparisons]]

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

# '''Courses'''
#: [[courses_table|courses]]

# '''Display'''
#: [[nodes]]
#: [[notifications]]
#: [[track_notifications]]
#: [[tree_folders]]
#: ''Deprecated Tables''
#:: [[notifications]]

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

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

# '''Other Features'''
#: [[bookmark_ratings]]
#: [[bookmarks]]
#: [[resubmission_times]]
#: [[sign_up_topics]]
#: [[ta_mappings]]
#: [[tag_prompt_deployments]]
#: [[tag_prompts]]

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

# '''Reviewing'''
#: [[comments]]
#: [[mapping_strategies]]
#: [[response_maps]]
#: [[responses]]
#: [[review_comments_paste_bins]]
#: [[review_grades]]
#: [[review_of_review_scores]]
#: [[review_scores]]
#: [[review_strategies]]
#: [[score_caches]]
#: [[scores]]
#: [[suggestion_comments]]
#: [[suggestions]]
#: ''Deprecated Tables''
#:: [[automated_metareviews]]
#:: [[awarded_badges]]
#:: [[badges]]
#:: [[review_feedbacks]]
#:: [[review_mappings]]
#:: [[review_of_review_mappings]]
#:: [[review_of_reviews]]
#:: [[reviews]]
#:: [[teammate_reviews]]

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

# '''Teammate'''
#: [[bids]]
#: [[invitations]]
#: [[join_team_requests]]
#: [[signed_up_teams]]
#: [[teams]]
#: [[teams_users]]

# '''Views'''
#: [[score_views]]

Back to [[Expertiza_documentation]] Main page.

Documentation on Database Tables

2025-12-09T04:36:56Z

Bvgowda:

'''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]]
#: [[deadline_types]]
#: [[deadline_rights]]
#: [[due_dates]]
#: [[late_policies]]
#: [[participants]]
#: [[submission_records]]
#: [[wiki_types]]
#: ''Deprecated Tables''
#:: [[plagiarism_checker_comparisons]]
#:: [[plagiarism_checker_assignment_submissions]]
#:: [[assignments_questionnaires]]
#:: [[calculated_penalties]]
# '''Answers'''
#: [[answers]]
#: [[answer_tags]]
# '''Goldberg'''
#: [[password_resets]]
#: [[permissions]]
#: [[plugin_schema_info]]
#: [[requested_users]]
#: [[roles]]
#: [[roles_permissions]]
#: [[schema_info]]
#: [[schema_migrations]]
#: [[users]]
#: [[user_pastebins]]
#: ''Deprecated Tables''
#:: [[site_controllers]]
#:: [[controller_actions]]
#:: [[content_pages]]
#:: [[markup_styles]]
#:: [[menu_items]]
#:: [[delayed_jobs]]
#:: [[system_settings]]
# '''Reviewing'''
#: [[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''
#:: [[automated_metareviews]]
#:: [[badges]]
#:: [[awarded_badges]]
#:: [[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]]
# '''Hierarchy'''
#: [[institutions]]
#: [[languages]]
#: [[sessions]]
#: [[versions]]
#: ''Deprecated Tables''
#:: [[sections]]
# '''Display'''
#: [[nodes]]
#: [[notifications]]
#: [[tree_folders]]
#: [[track_notifications]]
#: ''Deprecated Tables''
#:: [[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]]
#: [[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

2025-12-09T04:31:44Z

Bvgowda:

'''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]]
#: [[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''
#:: [[badges]]
#:: [[awarded_badges]]
#:: [[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]]
# '''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]]
#: [[sign_up_topics]]
#: [[resubmission_times]]
#: [[ta_mappings]]
#: [[tag_prompts]]
#: [[tag_prompt_deployments]]
# '''Views'''

#: [[score_views]]



Back to [[Expertiza_documentation]] Main page.

Assignments

2025-12-02T16:53:59Z

Bvgowda:

The Assignments table contains one record for each assignment created by an [[users|instructor]] or [[users|administrator]].

== Current Assignment Variable Documentation ==
<div style="background-color: #e6f7ff; border: 1px solid #0077b3; padding: 10px; margin-bottom: 20px;">
'''Structure Update:''' This table structure was updated in the latest release. Several columns were renamed (e.g., ''spec_location'' to ''URL'') and unused columns were removed.
</div>

{| class="wikitable"
!Field Name !!Type !!Description
|-
!id
|int(11)
|This object's unique ID value. One per object.
|-
!created_at
|datetime
|The date/time stamp when this record was created
|-
!updated_at
|datetime
|The date/time stamp when this record was last modified
|-
!name
|varchar(255)
|The name given to this assignment by the instructor/administrator who created it
|-
!directory_path
|varchar(255)
|If this is an assignment to which files are being submitted, this is the first part of the directory path for the submissions.
|-
!submitter_count
|int(10)
|Number of creators who have submitted so far to this assignment
|-
!course_id
|int(11)
|ID in the [http://wiki.expertiza.ncsu.edu/index.php/Courses_table Courses] table of the course with which this assignment is associated
|-
!instructor_id
|int(11)
|ID of a instructor who created the assignment
|-
!private
|tinyint(1)
|whether assignment is visible to other instructors
|-
!num_reviews
|int(11)
|number of reviews done by a student for this assignment
|-
!num_review_of_reviews
|int(10)
|number of reviews of reviews done by a student for this assignment
|-
!num_review_of_reviewers
|int(11)
|number of reviewers who have reviewed the assignment.
|-
!reviews_visible_to_all
|tinyint(1)
|if false, other reviewers can't see this reviewer's review.
|-
!num_reviewers
|int(10)
|Number of reviewers.
|-
!URL
|text
|URL of the assignment (formerly spec_location).
|-
!max_team_size
|int(11)
|Maximum number of participants allowed on the team.
|-
!staggered_deadline
|tinyint(1)
|Indicating whether deadlines are staggered or not.
|-
!allow_suggestions
|tinyint(1)
|Indicating whether participants in an assignment with topics may suggest additional topics.
|-
!days_between_submissions
|int(11)
|Number of Days available between submissions.
|-
!review_assignment_strategy
|varchar(12)
|Strategy used for assigning reviews.
|-
!max_reviews_per_submission
|int(11)
|Maximum number of reviews allowed per submission.
|-
!review_topic_threshold
|int(11)
|Threshold for review topics.
|-
!copy_flag
|tinyint(1)
|Whether the assignment has a copy or not.
|-
!rounds_of_reviews
|int(11)
|Total number of rounds of reviews done for the assignment.
|-
!microtask
|tinyint(1)
|Indicating whether this is a microtask assignment.
|-
!require_quiz
|tinyint(1)
|Indicating whether the assignment requires a quiz or not.
|-
!num_quiz_questions
|int(11)
|Total number of questions present for the quiz.
|-
!is_coding_assignment
|tinyint(1)
|Indicating whether whether the given assignment is a coding assignment or not.
|-
!topics_assigned_by_bidding
|tinyint(1)
|Indicates whether topics are to be bid on (formerly is_intelligent).
|-
!calculate_penalty
|tinyint(1)
|Indicating whether penalty needs to be calculated for the given assignment.
|-
!late_policy_id
|int(11)
|ID in the late policy table.
|-
!is_penalty_calculated
|tinyint(1)
|Indicating whether the penalty for the assignment is calculated or not.
|-
!show_teammate_reviews
|tinyint(1)
|Indicating whether teammate reviews are shown or not.
|-
!available_to_students
|tinyint(1)
|Indicating whether the given assignment is available to students (formerly availability_flag).
|-
!can_bookmark_topics
|tinyint(1)
|Indicating whether students can bookmark topics (formerly use_bookmark).
|-
!can_review_same_topic
|tinyint(1)
|Indicating whether a reviewer can review the same topic again.
|-
!can_choose_topic_to_review
|tinyint(1)
|Indicating whether a reviewer can choose a topic to review.
|-
!is_calibrated
|tinyint(1)
|Indicating whether the assignment is calibrated or not.
|-
!is_selfreview_enabled
|tinyint(1)
|Indicating whether an author can review his/her work.
|-
!is_anonymous
|tinyint(1)
|Indicating whether whether the reviewer information is anonymous or not.
|-
!num_reviews_required
|int(11)
|Total number of reviews required for this assignment.
|-
!num_metareviews_required
|int(11)
|Total number of metareviews required for this assignment.
|-
!num_metareviews_allowed
|int(11)
|Total number of metareviews allowed for this assignment.
|-
!num_reviews_allowed
|int(11)
|Total number of reviews allowed for this assignment.
|-
!is_answer_tagging_allowed
|tinyint(1)
|Indicating if answer tagging is allowed.
|-
!allow_selecting_additional_reviews_after_1st_round
|tinyint(1)
|Allows students to take more reviews after the first round.
|-
!sample_assignment_id
|int(11)
|ID of a sample assignment used for calibration/example.
|-
!vary_by_topic
|tinyint(1)
|Indicates if rubrics/criteria vary by topic.
|-
!vary_by_round
|tinyint(1)
|Indicates if rubrics/criteria vary by round.
|-
!team_reviewing_enabled
|tinyint(1)
|Indicates if team reviewing is enabled.
|-
!bidding_for_reviews_enabled
|tinyint(1)
|Indicates if bidding for reviews is enabled.
|-
!auto_assign_mentor
|tinyint(1)
|Indicates if a mentor is automatically assigned.
|-
!team_members_have_duties
|tinyint(1)
|Indicates if team members have specific duties (formerly duty_based_assignment).
|-
!questionnaire_varies_by_duty
|tinyint(1)
|Indicates if the questionnaire changes based on the duty.
|-
!enable_pair_programming
|tinyint(1)
|Indicates if pair programming is enabled for this assignment.
|}

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

[[File:assignment_imported.png]]

== E/R diagram for Child Tables ==
Tables which refer the Assignment Table as Foreign Key Relationship.

[[File:assignment_exported.png]]

 
 
<hr />

= ARCHIVED: Previous Schema =
<div style="background-color: #f9f9f9; border: 1px solid #aaa; padding: 10px;">
'''Deprecated:''' The table structure below represents the schema prior to the recent updates. It is retained here for historical reference.
</div>

{| class="wikitable mw-collapsible mw-collapsed"
!Field Name !!Type !!Description
|-
!id
|int(11)
|This object's unique ID value. One per object.
|-
!created_at
|datetime
|The date/time stamp when this record was created
|-
!updated_at
|datetime
|The date/time stamp when this record was last modified
|-
!name
|varchar(255)
|The name given to this assignment by the instructor/administrator who created it
|-
!directory_path
|varchar(255)
|If this is an assignment to which files are being submitted, this is the first part of the directory path for the submissions. If this is a wiki assignment, it is the base URL for wiki pages submitted by the creators
|-
!submitter_count
|int(10)
|Number of creators who have submitted so far to this assignment
|-
!course_id
|int(11)
|ID in the [http://wiki.expertiza.ncsu.edu/index.php/Courses_table Courses] table of the course with which this assignment is associated
|-
!instructor_id
|int(11)
|ID of a instructor who created the assignment
|-
!private
|tinyint(1)
|whether assignment is visible to other instructors
|-
!num_reviews
|int(11)
|number of reviews done by a student for this assignment
|-
!num_review_of_reviews
|int(10)
|number of reviews of reviews done by a student for this assignment
|-
!num_review_of_reviewers
|int(11)
|number of reviewers who have reviewed the assignment.
|-
!reviews_visible_to_all
|tinyint(1)
|if false, other reviewers can't see this reviewer's review.
|-
!num_reviewers
|int(10)
|Number of reviewers.
|-
!spec_location
|text
|url of the assignment.
|-
!max_team_size
|int(11)
|Maximum number of participants allowed on the team.
|-
!staggered_deadline
|tinyint(1)
|Indicating whether deadlines are staggered or not *************
|-
!allow_suggestions
|tinyint(1)
|Indicating whether participants in an assignment with topics may suggest additional topics for the instructor to approve.
|-
!days_between_submissions
|int(11)
|Number of Days available between submissions *************
|-
!review_assignment_strategy
|varchar(12)
|
|-
!review_topic_threshold
|int(11)
|***********************************
|-
!copy_flag
|tinyint(1)
|Whether the assignment has a copy or not. *************
|-
!rounds_of_reviews
|int(11)
|Total number of rounds of reviews done for the assignment *************
|-
!microtask
|tinyint(1)
|Indicating whether this is a microtask assignment, i.e., if it has topics that are worth varying amounts of credit, and may be selected by students.
|-
!require_quiz
|tinyint(1)
|Indicating whether the assignment requires a quiz or not. *************
|-
!num_quiz_questions
|int(11)
|Total number of questions present for the quiz. *************
|-
!is_coding_assignment
|tinyint(1)
|Indicating whether whether the given assignment is a coding assignment or not *************
|-
!is_intelligent
|tinyint(1)
|Indicates whether topics are to be bid on, and then the "intelligent assignment" algorithm will assign teams to topics *************
|-
!calculate_penalty
|tinyint(1)
|Indicating whether penalty needs to be calculated for the given assignment. *************
|-
!late_policy_id
|int(11)
|ID in the ******late policy table***** *************. Indicating which late policy is applied here.
|-
!is_penalty_calculated
|tinyint(1)
|Indicating whether the penalty for the assignment is calculated or not. *************
|-
!max_bids
|int(11)
|Total amount of bids given for this assignment. *************
|-
!show_teammate_reviews
|tinyint(1)
|Indicating whether teammate reviews are shown or not. *************
|-
!availability_flag
|tinyint(1)
|Indicating whether the given assignment is available or not. *************
|-
!use_bookmark
|tinyint(1)
|Indicating whether bookmarks are used or not. *************
|-
!can_review_same_topic
|tinyint(1)
|Indicating whether a reviewer can review the same topic again. *************
|-
!can_choose_topic_to_review
|tinyint(1)
|Indicating whether a reviewer can choose a topic to review *************
|-
!is_calibrated
|tinyint(1)
|Indicating whether the assignment is calibrated or not. *************
|-
!is_selfreview_enabled
|tinyint(1)
|Indicating whether an author can review his/her work. *************
|-
!reputation_algorithm
|varchar(12)
|This field gives us the information of the reputation algorithm used for this assignment. *************
|-
!is_anonymous
|tinyint(1)
|Indicating whether whether the reviewer information is anonymous or not. *************
|-
!num_reviews_required
|int(11)
|Total number of reviews required for this assignment. *************
|-
!num_metareviews_required
|int(11)
|Total number of metareviews required for this assignment. *************
|-
!num_metareviews_allowed
|int(11)
|Total number of metareviews allowed for this assignment. *************
|-
!num_reviews_allowed
|int(11)
|Total number of reviews allowed for this assignment. *************
|-
!simicheck
|int(11)
|Similarity Check between assignments. *************
|-
!simicheck_threshold
|int(11)
|Similarity check threshold value for the given assignment. *************
|}

Back to the [[Documentation_on_Database_Tables|database documentation]]

Menu items

2025-12-02T07:25:13Z

Bvgowda:

Delayed jobs

2025-12-02T07:24:36Z

Bvgowda:

<div style="background-color: #ffcccc; border: 1px solid #cc0000; padding: 10px; margin-bottom: 20px; text-align: center;">
'''⚠ DEPRECATED: This table has been removed from the database in the latest release. This documentation is retained for historical reference only.'''
</div>

The Delayed Jobs table gives information regarding the users registered to Courses.
== Delayed Jobs Variable Documentation ==

{| class="wikitable"
!Field Name !!Type !!Description
|-
!id
|int(11)
|The unique record id
|-
!priority
|int(11)
|Priority given to the delayed Job.
|-
!attempts
|int(11)
|Number of attempts given to the Job.
|-
!handler
|text
|The handler for te associated Job.
|-
!last_error
|text
|The error decription of the Last Error.
|-
!run_at
|datetime
|Date time value when the job was run.
|-
!locked_at
|datetime
|Date time value when the job was locked.
|-
!failed_at
|datetime
|Date time value when the job was failed.
|-
!locked_by
|varchar(255)
|Details of the User who locked it.
|-
!created_at
|datetime
|Date time value when the record was created.
|-
!updated_at
|datetime
|Date time value when the record was updated.
|-
!queue
|varchar(255)
|Job Queue
|}

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

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

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

Calculated penalties

2025-12-02T07:24:20Z

Bvgowda:

Badges

2025-12-02T07:24:01Z

Bvgowda:

Awarded badges

2025-12-02T07:22:23Z

Bvgowda: