Model Enrollments

Model Enrollments

Student enrollments in academic or other program offerings are modeled with the Program Enrollment and Affiliation objects.

Contacts' Program Enrollments

As we previously explored, BS Biology is an example of a degree-granting Academic Program. Consider now a student, Shay West, who decides to major in Biology and officially enrolls in the Academic Program. A Program Enrollment record represents the enrollment. It relates Shay's Contact record to the BS Biology Academic Program record.

Looking at the full list of Program Enrollments on Shay's Contact record, we can see how his interests are shaping his educational journey at Connected University.

Similarly, the Program Enrollment records on the Contact record for a third-grader at Delano Elementary School could look something like this example.

Program Enrollment ID	Related Academic Program	Represents Student's
PE-0106	Third Grade	Enrollment in third grade Tip If you're using K-12 Architecture Kit, the Grade Enrollment object lets you model grade enrollments specifically.
PE-0158	General Ed Transportation	School bus rider registration
PE-0352	Extended Day Support Program	After-school program registration

See Model Program Offerings.

Program Enrollments In Parallel with Affiliations

The Program Enrollment object relates a Contact to an Academic Program (Account). Specifically, it tracks a student Contact's enrollment data, such as enrollment dates and enrollment status. Program Enrollment serves a more specialized purpose than the Affiliation object, which similarly relates any kind of Contact—not just students—to any kind of Account—not just Academic Program Accounts. In EDA, Program Enrollments and Affiliations are used in parallel and come preconfigured with automation to keep their data in sync.

For example, remember Connected University student, Shay West, who's majoring in Biology? Shay's Contact record is related to the BS Biology Academic Program (Account) record by a Program Enrollment record, PE-2281. When that Program Enrollment record was created, Affiliation record AF-005967 was created automatically at the same time.

Even though the Affiliation connects the same two records connected by the Program Enrollment, it tracks more general-purpose data. It's one of a Contact's many affiliated Accounts, and tracks students', faculty members', and other people's involvement with campus and community organizations. Program Enrollment details don't apply to all types of Affiliations. Nor do they apply to all types of Contacts, which is why Program Enrollment data is tracked in a separate but related object.

Students' Program Enrollments can be changeable, as they explore their interests and complete various prerequisites before committing to an academic plan. And of course, plans sometimes change. If Shay changes majors, departments, or even colleges, someone makes sure that his Program Enrollment details are either updated, deleted, or created anew, and EDA automation keeps his corresponding Affiliation details updated, too.

Connect the Dots Between Enrollments and Program Offerings

Now that you've seen how to model the entities that administer Academic Programs, the programs themselves, and the students who enroll in those programs, we can connect the dots to create a bigger picture of these object relationships.

In this diagram, trace the connections that tell this part of the academic story for Biology major Shay West—from his Contact record to his affiliated Accounts, to his Program Enrollment in the major, to the Program Plan he's been assigned, and requirements for this academic plan.

Enrollments in Programs Versus Courses

Program Enrollments are for tracking students enrolling in degree programs, other types of academic programs, or other types of programs in general.

To track students enrolling in individual classes, use the Course Connection object, which relates a Contact to a Course Offering. See Model Courses and Curricula.