A Universal Requirement is a standalone program that will attach to students automatically. This is not something that is created by the SIS, and can be created by any Stellic superadmin. Therefore, the scope works differently than programs generated from SIS data since we need to define which students need the Universal Requirement being created by the user.
In order to create a universal requirement, a user has to choose an initial scope that can be further refined with secondary scope options. Initial scopes for universal requirements can be as follows:
- university-wide: all students at an institution. This scope can be narrowed further by using the additional optional scope options below.
- school: all students with a program declared within the specified school. If a student has no programs, we then use the student's school to determine the universal requirement's scope.
- You can only specify one school for a universal requirement's scope. This scope can only be used if your institution is using a school designation within your data, and students are affiliated with schools.
- department: all students with a program declared within the specified department. You can only specify one department for a universal requirement's scope. This scope can only be used if your institution is using a departmental designation within your data, and students are affiliated with departments.
- program: students within a particular program(s) in Stellic. You can specify more than one program if needed.
- student: you can specify individual students for a universal requirement.
Additional optional scope options include:
- Degree should only be specified if this audit is specific to students that have a declared program with a particular degree(s).
- Campus should only be specified if this audit is specific to students that have a declared program within a particular campus, and there can be variance between campuses for the program. We recommend you leave this value as "all campuses" unless your student population within the program spans multiple departments.
- Student tag should only be specified if this audit is specific to students with a particular characteristic being marked by a tag by your institution. Students without the tag will not have this audit applied. If there are two audits with otherwise identical criteria, specifying a tag will cause the students with the tag to have that particular audit version applied.
- Audit entry year looks for students with an audit a particular audit entry year. In other words, the important application criteria for this option is the audit that is applied to the student, not the student's data. This field may instead look for catalog year if you are using this at your institution. This field cannot be a range. If you have a universal requirement that applies to students with an audit year of 2019, 2020, and 2021, and you have 3 separate audits for those years (not just one audit that spans all three), you will need three separate universal requirements for these audits to all receive the requirement.
- Student entry term looks for students with a particular entry term. This field can be a range. This field looks for student data and will apply to students that have an entry term that is specified by the scope.
Using catalog terms to apply Universal Requirements
Currently, Stellic supports having one catalog term for all of a student's universal requirements. This is typically specified in a data feed as a students ge_catalog_term. In order to assign universal requirements via catalog term, choose the student entry term scope for the universal requirement. If Stellic receives a ge_catalog_term for the student, we will use this value to assign the universal requirement while reading from the student entry term field of the scope.