Enrollment Rosters

This information is primarily for instructors of courses in the CS Department.

Each weekday morning during the semester, we fetch enrollment data from the Registrar for the COS courses and the related ISC courses. This data is used by the department to grant enrolled student access to systems such as TigerFile, to determine eligibility for accounts on the CS systems, and other automated workflows.

In addition, this enrollment information is provided to instructors and, in some cases, students as described below.

IMPORTANT NOTES:

  • Enrollment data is PRIVATE and subject to privacy regulations. It must not be publicly posted or otherwise shared with others.
  • Enrollment data in CS systems is delayed (not real-time) and unofficial. Data directly from Registrar-maintained systems is the only official source of enrollment data at the University. Any updates to the data must be made through normal Registrar systems which will then be reflected on the next fetch.
  • If a student adds a course and then immediately (i.e., before the next data fetch) has an assignment due that uses TigerFile, an instructor can send an email to CS Staff and we can manually add them to TigerFile. They won't show up on the automated email or rosters described below (as that data is always a snapshot of the data from the Registrar), but they will be able to submit assignments through TigerFile.

Enrollment Email

After each fetch of data, enrollment rosters are compared on a course-by-course basis with the previous version of the data. If there are any differences in the roster for a course, an email is sent to the course instructors. The email contains the new roster as well as a summary of differences (adds, changes, deletes). While the email uses the term "Drop" for the case where a student was on the previous day's roster but is not on the current day's roster, this may or may not be due to a student initiating a "drop" -- it simply indicates a difference between the current roster and the next.

If course personnel changes and the distribution for a course enrollment email needs to change, please contact CS Staff. Note that the distribution for the enrollment email is independent of the list of instructors who can see enrollment pages (next section) (if enabled) and is independent of the instructors in the TigerFile system.

Enrollment Pages - Password Protected

To make it easier for students to self-organize into pairs or groups for team assignments or projects, course instructors can request to CS Staff that their course rosters be made available to students behind a password protected web site.

CS Staff has verified with the Office of General Counsel that sharing enrollment data in this manner is consistent with University policy.

For those courses that request it, the enrollment data appears on a password-protected, SSL encrypted webpage. Visitors to the page must authenticate using CAS and their OIT NetID credentials. After authenticating, the system will only show enrollment data for which the user is authorized to view. In the case of students, it will only allow them to view enrollment for the courses (i.e., COS courses that have requested this service) that they themselves are enrolled in. Instructors will only be able to see rosters for the courses they teach or support.

The enrollment rosters are available here: https://www.cs.princeton.edu/courses/enrollment/

Course instructors can put course-specific links on their pages like this:

https://www.cs.princeton.edu/courses/enrollment/?course=COS126_F2011

or this:

https://www.cs.princeton.edu/courses/enrollment/?course=COS126_F2011&precept=P01

If course personnel changes and the list of instructors who need to see enrollment pages for a course changes, please update the list using the course setup page on the ADM site. Note that the distribution for the enrollment email (above) is independent of the list of instructors who can see enrollment pages (if enabled) and is independent of the instructors in the TigerFile system.

Tags: