Skip to content

Add "course_id" to the database #8770

@bmcutler

Description

@bmcutler

What problem are you trying to solve with Submitty
Each course section has an ID number with the registrar. At RPI it is a 5 digit number that is unique for the semester and we call it a CRN. We would like to store this information in the database and have it available in Rainbow Grades.

Describe the way you'd like to solve this problem

Step 1: DONE

In the main Submitty database, let's add a column named 'course_id' to the courses_registration_sections table.
And in the course database, let's add a column named 'course_id' to the sections_registration table.

This is an optional piece of information, and different schools might have different types (numbers vs strings) or other requirements (uniqueness, etc.). So at this time, let's not attempt to put these requirements on the database. Let's set the type of this field as 'character varying' (string). It can have any length (# of characters) and is allowed to be empty string.

This field should be automatically synced between the Submitty database & each course database via database triggers.

Step 2: DONE

When student data is exported for Rainbow Grades, in addition to the field, e.g., "registration_section" : "5", let's add "course_id" : "12345".

Step 3: DONE

Let's display the section ID on the Manage Sections page for the course in the top section under "Manage Registration Sections", add a column to the "Current Registration Section" table.

Step 4: - this is incomplete

It would be nice to add a feature to set the course id for a section from the Manage Sections page. This information should update both the main database and the course database via triggers from step 1. I expect we at RPI will mostly be inputting the section data via sysadmin scripts with data from the registrar.

Edited to add -- NOTE: Once this information is exported than I'll update Rainbow Grades to use this information.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions