Expertiza_Wiki - User contributions [en]

Documentation on Database Tables

2025-12-09T04:05:40Z

Rtantry2: Undo revision 167476 by Rtantry2 (talk)

'''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]]
# '''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.

Documentation on Database Tables

2025-12-09T04:03:32Z

Rtantry2: Undo revision 167476 by Rtantry2 (talk)

'''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]]
# '''Hierarchy'''
#: [[institutions]]
#: [[languages]]
#: [[sessions]]
#: [[sections]]
#: [[versions]]
# '''Display'''
#: [[nodes]]
#: [[notifications]]
#: [[tree_folders]]
#: [[track_notifications]]
# '''Questionnaires/Rubrics'''
#: [[question_advice]]
#: [[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:01:08Z

Rtantry2:

'''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'''
#: [[topic_bids]]
#: [[invitations]]
#: [[join_team_requests]]
#: [[signed_up_teams]]
#: [[teams]]
#: [[teams_participants]]
# '''Courses'''
#: [[courses_table|courses]]
# '''Hierarchy'''
#: [[institutions]]
#: [[languages]]
#: [[sessions]]
#: [[sections]]
#: [[versions]]
# '''Display'''
#: [[nodes]]
#: [[notifications]]
#: [[tree_folders]]
#: [[track_notifications]]
# '''Questionnaires/Rubrics'''
#: [[question_advice]]
#: [[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.

Bids

2025-12-09T03:59:15Z

Rtantry2: /* Bids Variable Documentation */

The Bids table gives information regarding the bids for the topics given by a particular user.
== Topic Bids Variable Documentation (Reimplementation) ==

'''Note:''' This table has been renamed from ''bids'' to ''topic_bids''.

{| class="wikitable"
!Field Name !!Type !!Description
|-
!id
|int(11)
|Unique ID for each bids record.
|-
!topic_id
|int(11)
|Name of the Topic.
|-
!user_id
|int(11)
|User ID who bid for the Topic.
|-
!created_at
|datetime
|Date time value when the record was created.
|-
!updated_at
|datetime
|Date time value when the record was updated.
|-
!priority
|int(11)
|Priority Level for that Bid.
|}

== Bids Variable Documentation (2023 version) ==

{| class="wikitable"
!Field Name !!Type !!Description
|-
!id
|int(11)
|Unique ID for each bids record.
|-
!topic_id
|int(11)
|Name of the Topic.
|-
!user_id
|int(11)
|User ID who bid for the Topic.
|-
!created_at
|datetime
|Date time value when the record was created.
|-
!updated_at
|datetime
|Date time value when the record was updated.
|-
!priority
|int(11)
|Priority Level for that Bid.
|}

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

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

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

Question advices

2025-12-09T03:58:16Z

Rtantry2:

== Question Advice Variable Documentation (Reimplementation) ==

'''Note:''' This table has been renamed from ''question_advices'' to ''question_advice''.

{| class="wikitable"
!Field Name !!Type !!Description
|-
!id
|int(11)
|id of the advice
|-
!question_id
|int(11)
|id of the question
|-
!score
|int(11)
|scores related to each question. It could be just 0/1 meaning false/true or integers
|-
!advice
|text

|description of what a particular score means
|}

== Question Advices Variable Documentation (2023 version) ==

{| class="wikitable"
!Field Name !!Type !!Description
|-
!id
|int(11)
|id of the advice
|-
!question_id
|int(11)
|id of the question
|-
!score
|int(11)
|scores related to each question. It could be just 0/1 meaning false/true or integers
|-
!advice
|text

|description of what a particular score means
|}

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

[[File:question_advises.jpg]]

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

[[File:question_advises_child.jpg]]

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

Teams users

2025-12-09T03:56:45Z

Rtantry2:

== Teams Participants Variable Documentation (Reimplementation) ==

'''Note:''' This table has been renamed from ''teams_users'' to ''teams_participants''.

The Teams Participants table maps users to teams; in rare cases, a single individual is on > 1 team for an assignment.

{| class="wikitable"
!Field Name !!Type !!Description
|-
!id
|int(11)
|
|-
!team_id
|int(11)
|id of the team to which the user belongs to
|-
!user_id
|int(11)

|user id of student who belongs to the team
|
|-
!duty_id
|int(11)
|indicates what role the user plays (what duty they have) for this assignment: manager, programmer, tester, etc.
|-
!pair_programming_status
|varchar(1)
|a team can declare that it is pair programming, so that members won't be penalized for not doing commits.
|
|-
!participant_id
|int(11)
|id of the participant object for this user in this assignment. (This field is not yet in use.)
|}

== Teams Users Variable Documentation (2023 version) ==

The Teams table maps users to teams; in rare cases, a single individual is on > 1 team for an assignment.

{| class="wikitable"
!Field Name !!Type !!Description
|-
!id
|int(11)
|
|-
!team_id
|int(11)
|id of the team to which the user belongs to
|-
!user_id
|int(11)

|user id of student who belongs to the team
|
|-
!duty_id
|int(11)
|indicates what role the user plays (what duty they have) for this assignment: manager, programmer, tester, etc.
|-
!pair_programming_status
|varchar(1)
|a team can declare that it is pair programming, so that members won't be penalized for not doing commits.
|
|-
!participant_id
|int(11)
|id of the participant object for this user in this assignment. (This field is not yet in use.)
|}

== E/R diagram of tables referencing teams_users table ==
This table is not referenced by any other tables

== E/R diagram of tables teams_users table is referencing to ==

The following image shows the tables referencing teams_users table is referencing to
[[File:teams_users_export.png]]

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

Teams

2025-12-09T03:42:57Z

Rtantry2:

== Teams Variable Documentation (Reimplementation) ==

{| class="wikitable"
!Field Name !!Type !!Description
|-
!id
|int(11)
|
|-
!name
|varchar(255)
|Name of the team
|-
!parent_id
|int(11)
|ID of assignment or course that this team is participating in
|-
!type
|varchar(255)

|Type of the team, either AssignmentTeam or CourseTeam
|-
!submitted_hyperlinks
|text
|List of submitted hyperlinks
|-
!directory_num
|int(11)
|directory number where files submitted by this team are stored
|-
!grade_for_submission
|int(11)
|Stores the grade assigned by the instructor, if any
|-
!comment_for_submission
|text
|Stores feedback from the instructor for the team
|}

== Teams Variable Documentation (2023 version) ==

{| class="wikitable"
!Field Name !!Type !!Description
|-
!id
|int(11)
|
|-
!name
|varchar(255)
|Name of the team
|-
!parent_id
|int(11)
|ID of assignment or course that this team is participating in
|-
!type
|varchar(255)

|Type of the team, either AssignmentTeam or CourseTeam
|-
!comments_for_advertisement
|text
|text for comments
|-
!advertise_for_partner
|tinyint(1)
|Boolean that tells whether the team is advertising for a partner
|-
!submitted_hyperlinks
|text
|List of submitted hyperlinks
|-
!directory_num
|int(11)
|directory number where files submitted by this team are stored
|-
!grade_for_submission
|int(11)
|Stores the grade assigned by the instructor, if any
|-
!comment_for_submission
|text
|Stores feedback from the instructor for the team
|}

== E/R diagram of tables referencing users table ==
The following image shows the tables referencing teams table
[[File:teams_export.png]]

== E/R diagram of tables users table is referencing to ==
The teams table is not referenced by any other tables

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

Signed up teams

2025-12-09T03:41:16Z

Rtantry2: /* Signed Up Teams Variable Documentation */

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

{| 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.
|-
!comments_for_advertisement
|TEXT
|Comments provided by the team regarding the advertisement for partners.
|-
!advertising_for_partner
|BOOLEAN
|Indicates whether the team is currently advertising for a partner.
|}

== Signed Up Teams Variable Documentation (2023 version) ==

{| 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.

Submission records

2025-12-09T03:37:31Z

Rtantry2: /* Submission Records Variable Documentation */

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

{| class="wikitable"
!Name !!Datatype !!Description
|-
!id
|int(11)
|Primary key of the entry in table, auto increments by default
|-
!record_type
|text
|Type of submission record; this field may actually be unused (formerly type)
|-
!content
|varchar(255)
|Either the filename or URL identifying what was submitted
|-
!operation
|varchar(255)
|Which operation was done, either submit/remove hyperlink, or submit/remove file
|-
!team_id
|int(11)
|id of the student's team who submitted this hyperlink or file
|-
!submitted_by
|varchar(255)
|User who actually did the submission for their team (formerly user)
|}

== Submission Records Variable Documentation (2023 version) ==

{| class="wikitable"
!Name !!Datatype !!Description
|-
!id
|int(11)
|Primary key of the entry in table, auto increments by default
|-
!type
|text
|Type of submission record; this field may actually be unused
|-
!content
|varchar(255)
|Either the filename or URL identifying what was submitted
|-
!operation
|varchar(255)
|Which operation was done, either submit/remove hyperlink, or submit/remove file
|-
!team_id
|int(11)
|id of the student's team who submitted this hyperlink or file
|-
!user
|vharchar(255)
|User who actually did the submission for their team
|-
!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.

Participants

2025-12-09T03:35:27Z

Rtantry2: /* Participants variable documentation */

Users associated with either a [http://wiki.expertiza.ncsu.edu/index.php/Courses_table course] or an [http://wiki.expertiza.ncsu.edu/index.php/Assignments assignment]

==Participants variable documentation (Reimplementation)==

{| class="wikitable"
!Field Name !!Type !!Description
|-
!user_id
|INT(10)
|unique id referring to the user
|-
!id
|INT(10)
|unique identifier for the person participating
|-
!can_submit
|BIT
|bit to identify whether the person can submit or not
|-
!can_review
|BIT
|bit to identify whether the person can review or not
|-
!parent_id
|INT(10)
|unique id referring to parent assignment or course
|-
!OK_to_show
|BIT
|this bit tells whether the instructor can use the work that the student has submitted later on (formerly permission_granted).
|-
!grade
|FLOAT
|Grade allotted for the submission after evaluation
|-
!type
|VARCHAR(255)
|either CourseParticipant or AssignmentParticipant
|-
!handle
|VARCHAR(255)
|the handle that the user wants to be known by in this assignment
|-
!can_take_quiz
|BIT
|this bit signifies whether the participant can take a quiz on the work they are reviewing
|-
!can_mentor
|BIT
|Indicates whether the participant can act as a mentor.
|}

==Participants variable documentation (2023 version)==

{| class="wikitable"
!Field Name !!Type !!Description
|-
!id
|INT(10)
|unique identifier for the person participating
|-
!can_submit
|BIT
|bit to identify whether the person can submit or not
|-
!can_review
|BIT
|bit to identify whether the person can review or not
|-
!user_id
|INT(10)
|unique id referring to the user
|-
!parent_id
|INT(10)
|unique id referring to parent assignment or course
|-
!submitted_at
|DATETIME
|Date and Time of the submission made
|-
!permission_granted
|BIT
|this bit tells whether the instructor can use the work that the student has submitted later on.
|-
!penalty_accumulated
|INT UNSIGNED
|
|-
!grade
|FLOAT
|Grade allotted for the submission after evaluation
|-
!type
|VARCHAR(255)
|either CourseParticipant or AssignmentParticipant
|-
!handle
|VARCHAR(255)
|the handle that the user wants to be known by in this assignment
|-
!time_stamp
|DATETIME
|
|-
!digital_signature
|TEXT
|to record what was the evaluation
|-
!duty
|VARCHAR(255)
|the "role" of this person on their team, e.g., tester. Used only when roles are assigned to team members.
|-
!can_take_quiz
|BIT
|this bit signifies whether the participant can take a quiz on the work they are reviewing
|-
!Hamer
|FLOAT
|the reputation of this participant using the Hamer algorithm
|-
!Lauw
|FLOAT
|the reputation of this participant using the Lauw algorithm
|}

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

[[File:participants_eer.jpg]]

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

Users

2025-12-09T03:33:33Z

Rtantry2:

== Users Variable Documentation (Reimplementation) ==

{| class="wikitable"
!Name !!Datatype !!Description
|-
!id
|int(11)
|Primary key of the entry in table, auto increments by default
|-
!username
|varchar(255)
|User name of the respective user (formerly name)
|-
!crypted_password
|varchar(40)
|Password of the respective user
|-
!role_id
|int(11)
|Role which this user corresponds to FK into ROLES table. Examples are super_admin, admin, instructor, etc.
|-
!password_salt
|varchar(255)
|
|-
!name
|varchar(255)
|Registered full name of the user, e.g., Lastname, firstname (formerly fullname)
|-
!email
|varchar(255)
|Registered email of the respective user.
|-
!parent_id
|int(11)
|Parent of the respective user; corresponding to the user who created this user. The value of this field is the primary key in the users table for the parent user, e.g., 2 if the parent is the super-admin (username admin).
|-
!private_by_default
|tinyint(1)
|If the user is private by default; essentially Boolean. It seems that this is not used in the system, don't know what it was intended to mean. Could be removed.
|-
!email_on_submission
|tiny_int(1)
|If user is to be e-mailed when something they reviewed is resubmitted.
|-
!is_new_user
|tiny_int(1)
|Determines whether the user has logged in before; if not, upon login the user should be presented with the new-user agreement.
|-
!handle
|varchar(255)
|A handle is an alternate name by which the user would want to be known, e.g., on the wiki, if this assignment involves writing on a wiki. This allows the user to appear anonymous. In the code, this is sometimes known as the "default handle", because users can also create assignment-specific handles.
|-
!time_zone_pref
|varchar(255)
|Timezone that times should be displayed in when the user logs in.
|-
!public_key
|mediumtext
|Public key used for data-encryption by user. This is used and should stay in the table, though whether the use is meaningful is not clear.
|-
!copy_of_emails
|tinyint(1)
|Whether this user wants to receive copies of e-mails sent for all assignments they are participating in. This is only implemented for instructors. Instructors would enable it so they start getting copies of all emails being sent related to their assignments. It is a way that the instructor can be reassured that emails are in fact being sent.
|-
!institution_id
|int(11)
|id of the institution that the user is associated with
|}

== Users Variable Documentation (2023 version) ==

{| class="wikitable"
!Name !!Datatype !!Description
|-
!id
|int(11)
|Primary key of the entry in table, auto increments by default
|-
!name
|varchar(255)
|User name of the respective user
|-
!crypted_password
|varchar(40)
|Password of the respective user
|-
!role_id
|int(11)
|Role which this user corresponds to FK into ROLES table. Examples are super_admin, admin, instructor, etc.
|-
!password_salt
|varchar(255)
|
|-
!fullname
|varchar(255)
|Registered full name of the user, e.g., Lastname, firstname
|-
!email
|varchar(255)
|Registered email of the respective user.
|-
!parent_id
|int(11)
|Parent of the respective user; corresponding to the user who created this user. The value of this field is the primary key in the users table for the parent user, e.g., 2 if the parent is the super-admin (username admin).
|-
!private_by_default
|tinyint(1)
|If the user is private by default; essentially Boolean. It seems that this is not used in the system, don't know what it was intended to mean. Could be removed.
|-
!mru_directory_path
|varchar(128)
|To allow the user to log back in to the same directory that (s)he logged out from before.
|-
!email_on_review
|tiny_int(1)
|Whether the user should be e-mailed when a new review is received for their work.
|-
!email_on_submission
|tiny_int(1)
|If user is to be e-mailed when something they reviewed is resubmitted.
|-
!email_on_review_of_review
|tiny_int(1)
|Whether the user should be e-mailed when one of their reviews is meta-reviewed by another reviewer.
|-
!is_new_user
|tiny_int(1)
|Determines whether the user has logged in before; if not, upon login the user should be presented with the new-user agreement.
|-
!master_permssion_granted
|tiny_int(4)
|If the user has the master user permission is granted. What?! What does master permission mean?! Well, doesn't matter, because this field is set but not read in existing code.
|-
!handle
|varchar(255)
|A handle is an alternate name by which the user would want to be known, e.g., on the wiki, if this assignment involves writing on a wiki. This allows the user to appear anonymous. In the code, this is sometimes known as the "default handle", because users can also create assignment-specific handles.
|-
!digital_certificate
|mediumtext
|Digital certificate generated for the user to protect his password. This is never read and could be removed.
|-
!timezonepref
|varchar(255)
|Timezone that times should be displayed in when the user logs in.
|-
!public_key
|mediumtext
|Public key used for data-encryption by user. This is used and should stay in the table, though whether the use is meaningful is not clear.
|-
!copy_of_emails
|tinyint(1)
|Whether this user wants to receive copies of e-mails sent for all assignments they are participating in. This is only implemented for instructors. Instructors would enable it so they start getting copies of all emails being sent related to their assignments. It is a way that the instructor can be reassured that emails are in fact being sent.
|-
!institution_id
|int(11)
|id of the institution that the user is associated with
|}

== E/R diagram of tables referencing users table ==
The following image shows the tables referencing users table
[[File:Users_export.png]]

== E/R diagram of tables users table is referencing to ==
The users table is not referenced by any other tables

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

Suggestions

2025-12-09T03:29:41Z

Rtantry2:

== Suggestions Variable Documentation (Reimplementation) ==

{| class="wikitable"
!Name !!Datatype !!Description
|-
!id
|int(11)
|Primary key of the entry in table, auto increments by default
|-
!assignment_id
|int(11)
|ID of the assignment for which suggestions are published
|-
!title
|varchar(255)
|Stores the title of the suggestion
|-
!description
|text
|Stores the description of the suggestion
|-
!status
|varchar(255)
|Stores the status of the suggestion(Initiated/Approved/Rejected)
|-
!username
|varchar(255)
|Stores the username of the user who provides suggestion (formerly unityID)
|-
!signup_preference
|varchar(255)
|Stores the signup_preference(Y/N) of the user who provides suggestion
|}

== Suggestions Variable Documentation (2023 version) ==

{| class="wikitable"
!Name !!Datatype !!Description
|-
!id
|int(11)
|Primary key of the entry in table, auto increments by default
|-
!assignment_id
|int(11)
|ID of the assignment for which suggestions are published
|-
!title
|varchar(255)
|Stores the title of the suggestion
|-
!description
|text
|Stores the description of the suggestion
|-
!status
|varchar(255)
|Stores the status of the suggestion(Initiated/Approved/Rejected)
|-
!unityID
|varchar(255)
|Stores the unityID of the user who provides suggestion
|-
!signup_preference
|varchar(255)
|Stores the signup_preference(Y/N) of the user who provides suggestion
|}

== E/R diagram of tables referencing suggestions table ==
The following table doesn't reference to other tables in the database

== E/R diagram of tables suggestions table is referencing to ==
The tag_prompts table is not referenced by any other tables

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

Responses

2025-12-09T03:27:53Z

Rtantry2: /* Response variable documentation */

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 (Reimplementation)==

{| class="wikitable"
!Field Name !!Type !!Description
|-
!id
|int(11)
|The unique record id
|-
!response_map_id
|int(11)
|The ID of the [[response_maps|response map]] defining the relationship that this response applies to (formerly map_id)
|-
!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.
|}

==Response variable documentation (2023 version)==

{| 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.

Response maps

2025-12-09T03:26:41Z

Rtantry2: /* Response maps variable documentation */

Maps a connection between the [[participants]] as reviewers and [[participants]] or [[teams]] as reviewees

==Response maps variable documentation (Reimplementation)==

{| class="wikitable"
!Field Name !!Type !!Description
|-
!id
|int(11)
|The unique record id
|-
!reviewed_object_id
|int(11)
|The object being reviewed in the [[responses|response]]. Possible objects include other ResponseMaps or [[assignments]]
|-
!reviewer_id
|int(11)
|The [[participants|participant]] (actually AssignmentParticipant) providing the response
|-
!reviewee_id
|int(11)
|Dependent on which subclass of ResponseMap this object is. For a ReviewResponseMap, the [[teams|team]] (AssignmentTeam) receiving the response. For a TeammateReviewResponseMap, the AssignmentParticipant who is being reviewed.
|-
!type
|varchar(255)
|Used for subclassing the response map. Available subclasses are ReviewResponseMap, MetareviewResponseMap, FeedbackResponseMap, TeammateReviewResponseMap
|-
!created_at
|DATETIME
|Date and Time for when the record was created
|-
!updated_at
|DATETIME
|Date and Time when the last update was made
|-
!for_calibration
|int(11)
|Tells whether the record will be used for calibration or not.
|}

==Response maps variable documentation (2023 version)==

{| class="wikitable"
!Field Name !!Type !!Description
|-
!id
|int(11)
|The unique record id
|-
!reviewed_object_id
|int(11)
|The object being reviewed in the [[responses|response]]. Possible objects include other ResponseMaps or [[assignments]]
|-
!reviewer_id
|int(11)
|The [[participants|participant]] (actually AssignmentParticipant) providing the response
|-
!reviewee_id
|int(11)
|Dependent on which subclass of ResponseMap this object is. For a ReviewResponseMap, the [[teams|team]] (AssignmentTeam) receiving the response. For a TeammateReviewResponseMap, the AssignmentParticipant who is being reviewed.
|-
!type
|varchar(255)
|Used for subclassing the response map. Available subclasses are ReviewResponseMap, MetareviewResponseMap, FeedbackResponseMap, TeammateReviewResponseMap
|-
!created_at
|DATETIME
|Date and Time for when the record was created
|-
!updated_at
|DATETIME
|Date and Time when the last update was made
|-
!calibrate_to
|tinyint(1)
|Tells whether the record will be used for calibration or not.
|}

Back to the [[Documentation_on_Database_Tables|database documentation]]

Quiz question choices

2025-12-09T03:24:37Z

Rtantry2:

== Quiz Question Choices Variable Documentation (Reimplementation) ==

{| class="wikitable"
!Name !!Datatype !!Description !
|-
!id
|INT(11)
|unique identifier for the record
|-
!question_id
|INT(11)
|the unique identifier for the question
|-
!txt
|TXT
|The description for the question
|-
!is_correct
|TINYINT(1)
|to check whether it is correct or not
|}

== Quiz Question Choices Variable Documentation (2023 version) ==

{| class="wikitable"
!Name !!Datatype !!Description !
|-
!id
|INT(11)
|unique identifier for the record
|-
!question_id
|INT(11)
|the unique identifier for the question
|-
!txt
|TXT
|The description for the question
|-
!iscorrect
|BIT
|to check whether it is correct or not
|}

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

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

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

Due dates

2025-12-09T03:19:08Z

Rtantry2: /* Due Dates Variable Documentation */

The Due Dates table gives information regarding the due dates associated to each of the assignment.
== Due Dates Variable Documentation (Reimplementation) ==

{| class="wikitable"
!Field Name !!Type !!Description
|-
!id
|int(11)
|Unique ID for each Due Date record
|-
!due_at
|datetime
|Deadline for submission
|-
!deadline_type_id
|int(11)
|whether a submission deadline, a review deadline, etc.
|-
!assignment_id
|int(11)
|the assignment that the deadline is related to (formerly parent_id)
|-
!submission_allowed_id
|int(11)
|this is "OK", "Late" or "No", depending on whether submission is allowed before this due date
|-
!review_allowed_id
|int(11)
|this is "No", "Late" or "OK", depending on whether reviewing is allowed before this due date
|-
!review_of_review_allowed_id
|int(11)
|this is "OK", "Late" or "No", depending on whether meta-reviewing is allowed before this due date
|-
!round
|int(11)
|Number of the review round to which this due date pertains
|-
!flag
|tinyint(1)
|Not clear what this is. It is zero in all due dates except some between 2010/11/15 and 2011/05/25.
|-
!threshold
|int(11)
|How many hours before the due date a reminder is sent to participants
|-
!delayed_job_id
|int(11)
|ID of the delayed job, presumably the job that sends reminders of this due date.
|-
!deadline_name
|varchar(255)
|Name of the deadline. This is either NULL or the empty string in all deadlines.
|-
!description_url
|varchar(255)
|URL of the description
|-
!quiz_allowed_id
|int(11)
|ID of the quiz associated to the Due Date. No! This does not make any sense. efg has no idea of what this field is for.
|-
!teammate_review_allowed_id
|int(11)
|this is "OK", "Late" or "No", depending on whether teammate review is allowed before this due date
|-
!type
|int(11)
|Type of the Due Date.
|}

== Due Dates Variable Documentation (2023 version) ==

{| class="wikitable"
!Field Name !!Type !!Description
|-
!id
|int(11)
|Unique ID for each Due Date record
|-
!due_at
|datetime
|Deadline for submission
|-
!deadline_type_id
|int(11)
|whether a submission deadline, a review deadline, etc.
|-
!parent_id
|int(11)
|the assignment that the deadline is related to
|-
!submission_allowed_id
|int(11)
|this is "OK", "Late" or "No", depending on whether submission is allowed before this due date
|-
!review_allowed_id
|int(11)
|this is "No", "Late" or "OK", depending on whether reviewing is allowed before this due date
|-
!review_of_review_allowed_id
|int(11)
|this is "OK", "Late" or "No", depending on whether meta-reviewing is allowed before this due date
|-
!round
|int(11)
|Number of the review round to which this due date pertains
|-
!flag
|tinyint(1)
|Not clear what this is. It is zero in all due dates except some between 2010/11/15 and 2011/05/25.
|-
!threshold
|int(11)
|How many hours before the due date a reminder is sent to participants
|-
!delayed_job_id
|int(11)
|ID of the delayed job, presumably the job that sends reminders of this due date.
|-
!deadline_name
|varchar(255)
|Name of the deadline. This is either NULL or the empty string in all deadlines.
|-
!description_url
|varchar(255)
|URL of the description
|-
!quiz_allowed_id
|int(11)
|ID of the quiz associated to the Due Date. No! This does not make any sense. efg has no idea of what this field is for.
|-
!teammate_review_allowed_id
|int(11)
|this is "OK", "Late" or "No", depending on whether teammate review is allowed before this due date
|-
!type
|int(11)
|Type of the Due Date.
|}

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

[[File:due_dates_imported.png]]

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

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

Courses table

2025-12-09T03:16:19Z

Rtantry2: /* Courses Variable Documentation */

The Courses table gives information regarding the Courses.
== Courses Variable Documentation (Reimplementation) ==

{| class="wikitable"
!Field Name !!Type !!Description
|-
!id
|int(11)
|The unique record id
|-
!name
|varchar(255)
|The name of the course
|-
!instructor_id
|int(11)
|The [[users|user]] who created this course
|-
!directory_path
|varchar(255)
|The directory to be used for work submitted to this course (assuming that files will be submitted, rather than wiki pages, etc.). Concatenated with the instructor's name to create a unique location within the directory hierarchy. We expect that submission directories for particular assignments in the course will be subdirectories of this directory.
|-
!info
|text
|A description of the course
|-
!created_at
|datetime
|The timestamp at which this course was created
|-
!updated_at
|datetime
|The timestamp at which this course was last updated
|-
!is_private
|tinyint(1)
|Whether or not the course is available to other administrators and instructors
|-
!institution_id
|int(11)
|The institution this course belongs to.
|-
!language
|varchar(255)
|The language/locale setting for the course.
|}

== Courses Variable Documentation (2023 version) ==

{| class="wikitable"
!Field Name !!Type !!Description
|-
!id
|int(11)
|The unique record id
|-
!name
|varchar(255)
|The name of the course
|-
!instructor_id
|int(11)
|The [[users|user]] who created this course
|-
!directory_path
|varchar(255)
|The directory to be used for work submitted to this course (assuming that files will be submitted, rather than wiki pages, etc.). Concatenated with the instructor's name to create a unique location within the directory hierarchy. We expect that submission directories for particular assignments in the course will be subdirectories of this directory.
|-
!info
|text
|A description of the course
|-
!created_at
|datetime
|The timestamp at which this course was created
|-
!updated_at
|datetime
|The timestamp at which this course was last updated
|-
!private
|tinyint(1)
|Whether or not the course is available to other administrators and instructors
|-
!institutions_id
|int(11)
|Whether or not the course is available to other administrators and instructors
|-
!locale
|varchar(255)
|The language/locale setting for the course.
|}

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

[[File:courses_imported.png]]

== E/R diagram for Child Tables ==
Tables referred by the Courses Table as Foreign Key Relationship.
'''NOTE: courses_users table does not exist in the database.'''

[[File:courses_exported.png]]

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

Bookmark ratings

2025-12-09T03:13:49Z

Rtantry2: /* Bookmark Ratings Variable Documentation */

The Bookmark Ratings table gives information regarding the ratings provided to each of these bookmarks.
== Bookmark Ratings Variable Documentation (Reimplementation) ==

{| class="wikitable"
!Field Name !!Type !!Description
|-
!id
|int(11)
|Unique ID for each bookmark_ratings record.
|-
!artifact_id
|int(11)
|ID of the Bookmark.
|-
!rater_id
|int(11)
|User ID who rated the particular Bookmark.
|-
!ratings
|int(11)
|Rating provided to that bookmark.
|-
!created_at
|datetime
|Date time value when the record was created.
|-
!updated_at
|datetime
|Date time value when the record was updated.
|}

== Bookmark Ratings Variable Documentation (2023 version) ==

{| class="wikitable"
!Field Name !!Type !!Description
|-
!id
|int(11)
|Unique ID for each bookmark_ratings record.
|-
!bookmark_id
|int(11)
|ID of the Bookmark.
|-
!user_id
|int(11)
|User ID who rated the particular Bookmark.
|-
!rating
|int(11)
|Rating provided to that bookmark.
|-
!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 ==
No Tables were referred by the Bookmark_ratings Table as Foreign Key Relationship.

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

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

Assignments

2025-12-09T03:10:23Z

Rtantry2: /* Current Assignment Variable Documentation */

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

== Current Assignment Variable Documentation (Reimplementation) ==
<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.
|}

== Current Assignment Variable Documentation (2023 version) ==

{| 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.
|-
!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.
|-
!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.
|-
!is_intelligent
|tinyint(1)
|Indicates whether topics are to be bid on.
|-
!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.
|-
!availability_flag
|tinyint(1)
|Indicating whether the given assignment is available to students.
|-
!use_bookmark
|tinyint(1)
|Indicating whether students can bookmark topics.
|-
!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.
|-
!duty_based_assignment
|tinyint(1)
|Indicates if team members have specific duties.
|-
!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]]

Assignment questionnaires

2025-12-09T03:03:19Z

Rtantry2: /* Assignment Questionnaires variable documentation */

The assignment_questionnaires table defines the joins between a [[questionnaires|questionnaire]] and an [[assignments|assignment]]. It is also used to associate default limits for the notifications an instructor receives.
==Assignment Questionnaires variable documentation (Reimplementation)==

{| class="wikitable"
!Field Name !!Type !!Description
|-
!id
|int(11)
|The unique record id
|-
!assignment_id
|int(11)
|The ID of the [[assignments|assignment]] in this relationship. A null value is used to define the default limits
|-
!questionnaire_id
|int(11)
|The ID of the [[questionnaires|questionnaire]] in this relationship. A null value is used to define the default limits
|-
!user_id
|int(11)
|The ID of the [[users|instructor]] who created the relationship
|-
!notification_threshold
|int(11)
|A percent difference between an awarded score and the current average score as an integer. This defines at which point the instructor receives a notification that a response falls outside the acceptable range
|-
!questionnaire_weight
|int(11)
|A percentage that the [[questionnaires|questionnaire]] contributes to the overall score. When both assignment_id and questionnaire_id are null, this relationship defines the defaults set by the instructor.
|-
!used_in_round
|int(11)
|Questionnaire used in which particular round.
|-
!dropdown_in_use
|tinyint(1)
|Indicating whether a dropdown is present or not.
|}

==Assignment Questionnaires variable documentation (2023 version)==

{| class="wikitable"
!Field Name !!Type !!Description
|-
!id
|int(11)
|The unique record id
|-
!assignment_id
|int(11)
|The ID of the [[assignments|assignment]] in this relationship. A null value is used to define the default limits
|-
!questionnaire_id
|int(11)
|The ID of the [[questionnaires|questionnaire]] in this relationship. A null value is used to define the default limits
|-
!user_id
|int(11)
|The ID of the [[users|instructor]] who created the relationship
|-
!notification_limit
|int(11)
|A percent difference between an awarded score and the current average score as an integer. This defines at which point the instructor receives a notification that a response falls outside the acceptable range
|-
!questionnaire_weight
|int(11)
|A percentage that the [[questionnaires|questionnaire]] contributes to the overall score. When both assignment_id and questionnaire_id are null, this relationship defines the defaults set by the instructor.
|-
!used_in_round
|int(11)
|Questionnaire used in which particular round.
|-
!dropdown
|tinyint(1)
|Indicating whether a dropdown is present or not.
|}

== E/R diagram for Parent Tables ==
The table Assignment_questionnaire has not referred to any other table.

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

[[File:assignment_questionnaire_imported.png]]

Back to the [[Documentation_on_Database_Tables|database documentation]]