Clients on version 8.0 and higher will need to generate updated degree audits for import and processing based on a schedule to be arranged with your consultant.
How many times will batch audits need to be generated annually?
Consultants will work with you to determine the exact frequency. At a minimum, the audits will need to be generated at least once for each major term. If your institution is interested in additional analysis results following key milestones on the academic calendar, then the batch audit process could be completed more frequently (but usually no more than 2-3 times per term).
What is the student population for the batch degree audit process?
Platinum Analytics results are generated for an analysis term (e.g. Fall). When generating degree audits, students enrolled in the analysis term and the prior term (e.g. Spring) should be included. In other words, the continuing student population, as well as any new students who have already registered, should be included in the batch audit.
Are there specific settings for the audits that should be used?
The Platinum Analytics import must know the audit type and the batch date in order to ensure the correct audit is selected for processing. In addition, in-progress courses and pre-registered courses should be included in the batch audit process. Depending on business practices, audits may need to be frozen for a short period of time while they are imported.
What is the required retention for the audits?
In general, audits should be saved for one week to ensure import processing. If this is not feasible, then an alternate retention schedule can be discussed.
How does Ad Astra access the audit information?
Ad Astra accesses the audit result information from the following PeopleSoft tables (query access must be granted for the appropriate security profile):
When are the first degree audits needed?
Consultants will work with you on the exact timing.