Addendum with evidence (8.2 MB) - Accreditation - Bakersfield ...

Registrar’s Report, Diagnostics Report, and Student Data Report audit views were
reviewed with the Implementation Team with an emphasis on navigation of the
forms, the contents of each and what to look for on each form. We primarily focused
on when it is appropriate to utilize each form in the process of researching issues
that may be discovered during their testing. Example: Scribe in question – start with
the Registrar Report; Audit Engine decision in question – start with the Diagnostics
Report; Student data in question – start with the Student Data Report.
Web Data Review
Training 2
We covered the following concepts during our discussion (the first four bullets were
refresher discussions):
Always regenerates the audit from data in DegreeWorks – Only data already in DW
when the audit is run is considered. Changes in Banner that have not yet been
bridged are not considered nor are items changed in DW (notes, petitions,
exceptions) during the current session shown unless the “Process New” function is
utilized to regenerate the audit.
Role of Catalog Year in matching students to blocks – the catalog year as it appears
on the SGASTDN Curriculum and Field of Study records are applied as appropriate
to determine which requirement block will appear for a student. Example: If a
student has a entrance catalog year of 2007 and a major catalog year of 2009, the
major would look at a scribe block that had a start year of 2009 (or prior) with an end
date of 2009 or beyond, while the degree and general education blocks would look at
a scribe block that had a start year of 2007 (or prior) with an end year of 2007 or
beyond.
The Registrar’s Report, Diagnostics Report, and Student Data Report audit views
were reviewed with the Implementation Team with an emphasis on navigation of the
forms, the contents of each and what to look for on each form. We primarily focused
on when it is appropriate to utilize each form in the process of researching issues
that may be discovered during their testing. Example: Scribe in question – start with
the Registrar Report; Audit Engine decision in question – start with the Diagnostics
Report; Student data in question – start with the Student Data Report.
Notes – Depending on security level granted, advisors will have the capability of
adding either pre-defined and/or free-form notes that are then added to the student
audit and become part of their record. Reminder: the notes will only appear on the
audit after the note is saved and the Process New button has been utilized.
Petitions – The petition process was reviewed but will likely not be utilized.
Exceptions – We reviewed the functionality for applying exceptions to student
records. This included discussion of each of the exception options available, when
more than one exception may be required to complete the exception, how to identify
enforced and unenforced exceptions and why an exception would become
unenforced. We also discussed how several different methods can be used to
complete the same exception. We reviewed the Exception Management Report as a
tool for managing exceptions and the AUD001 report in Transit for monitoring
unhooked and unenforced exceptions. Below is a recap of the various exception
types and specifics about how and when they are best used.
o Force Complete – allows you to complete a course rule, subset rule, and/or
block or rule qualifier without applying additional classes.
Kern Community College District Confidential and Proprietary Page 9 of 20
DegreeWorks Services Engagement Report