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

CAPP flag set in Banner). The functionality was then turned off until the
necessary Banner cleanup can be done. The team has the information for
turning it back on when they are ready to move forward with this functionality.
Transit
Training 1
We completed a review of the navigation and functionality as it relates to the ADMIN
tasks (daprestart, ucx12job, webrestart). We also reviewed running the DAP 16 process
and SCR02 through SCR10 reports so that the team can utilize these functions as
needed during their scribing and testing.
Training 2
We reviewed the remaining Transit functionality with the exception of the DAP54 report
which will be reviewed during Training 3.
Training 3
Reviewed DAP54 as it relates to applying templates to students in bulk.
Block and Web Review
Training 2
The implementation team reviewed the recommended strategies for both block and web
review. We completed examples of both and staff did a good job of identifying both
scribe and audit issues and the methodologies for determining where the issue was and
how it needed to be corrected. They identified several scribe issues that we were able
to correct during the session.
We covered the following concepts during our discussion:
Best Fit Algorithm – the Audit Engine will always attempt to place the student’s
courses into the audit in such a way as to achieve the highest possible level of
requirement completion. Consequently, it is possible for a course to be used to meet
one requirement on one audit and have that class move to complete a different
requirement on a subsequent audit if that is now the “best fit” for that student.
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/extracted are not considered nor are items changed in DW (notes, petitions,
exceptions) during the current session processed 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.
Review of Diagnostic Tools – It was noted that those with Registrar level access
(equivalent to a superuser in Banner) have access to several other tools within DW
to assist with diagnosing any questions/discrepancies/issues that may arise. The
Kern Community College District Confidential and Proprietary Page 8 of 20
DegreeWorks Services Engagement Report