The Advising module allows user-defined aim labels to be assigned to students in order to identify their goals. Labels such as MAJOR, MINOR, or CORE are examples of aim labels that might be used in your institution. Aim labels are also categorized by aim types.
The contents of each aim label varies according to the student's individual requirements as illustrated below with the Aim Label of MAJOR:
Major when assigned to Don Smith: |
|
Major when assigned to Judy Anderson: |
|||
Becomes the student aim of MAJOR for Don Smith |
|
Becomes the student aim of MAJOR for Judy Anderson. |
|||
English MAJOR (ENGMAJ) |
|
Art MAJOR (ARTMAJ) |
|||
Completion of a minimum of 51 credits which must include the following: |
|
Completion of a minimum of 60 credits which must include the following: |
|||
English Comp |
9 credits |
|
Art History |
9 credits |
|
Communication |
6 credits |
|
Studio Art |
42 credits |
|
Grammar |
6 credits |
|
Fine Art Electives |
9 credits |
|
Literature |
30 credits |
|
|
|
|
Total: |
51 credits |
|
Total: |
60 credits |
The examples above show that the aim label of MAJOR would vary greatly depending on the student to which it is assigned. The MAJOR aim label for Don has an Advising Requirement Code of ENGMAJ that serves as the root requirement and will be used as the source for evaluating his requirements. The same holds true for Judy and the ARTMAJ student aim, which is her root requirement.
|
It is possible for a student to have an aim label with no associated Advising Requirement Code. Such a case might exist when the student has not yet selected a specific major. |
If desired, you may use the same name to identify both the requirement type and the aim label.
|
All requirements designated as the root of a degree major tree have both a requirement type and aim label called MAJOR. Therefore, when selecting advising requirement codes to satisfy an aim of MAJOR, all requirements with a type of MAJOR would be obvious. However, this is a matter of choice and may or may not be used in your institution. |
As soon as an aim is assigned to a student, it becomes a student aim and ready to be configured for the individual student. After the student aim has been identified, it will serve as a starting point for building the student's requirements tree and evaluating the progress towards meeting the requirements that have been specified in that tree.
|
When a student's progress is evaluated, the summary information is stored in the Student Aims row that was selected for the evaluation. This provides a means of viewing a summary of a student's progress from the previous evaluation without having to perform a recalculation. |