The Dual Credit Synchronization process has two parts to it:

• Update Partner PSI information
• Load CDA pathway data

Updating PSI information cannot be done independently of loading CDA pathway data as both are part of the same background process now. This process runs once a day upon startup and, like some other background processes, can be run at different times for QA. If the testing flag is set, it will run every 15 minutes from 09:00 to 18:00.

As soon as PASI core is restated the dual credit process will start and acquire any new changes from CDA using the CDA proxy service, passing in our most recent version of the data.

Updated pathways from CDA are compared against the pathways in PASI to determine if something has changed that can potentially impact pathway completion and/or evaluated mark statuses. For example, if the start and/or ending school years on a pathway are changed, this change will result in triggering. There is an edge case where a change to the ending school year will not result in triggering; an example would be if the ending school is not provided but then it is updated to be 2050. If a course is added, updated, or removed from a course mapping, the related pathway that course mapping is for would be considered changed.

Not all changes result in triggering. For example, if the name of a pathway is changed, the pathway will be saved in PASI but nothing will be triggered as the pathway has not changed in a way that would impact pathway completion or evaluated mark statuses. Another example of a non-triggering update would be if a pathway is deleted in CDA and PASI, and is updated in CDA but still deleted, PASI would save the updated pathway but nothing would be triggered. The same is true for other entities on the pathway such as a pathway requirement for example. The five entities on a pathway are surveyed for changes:

• External Credentialed Pathway
• Pathway
• Pathway Requirement Set
• Pathway Requirement
• Pathway Requirement Course Mapping

Changes to an external credential or an awarding organization do not result in any triggering. However, if an external credential is deleted, CDA will also delete the related external credentialed pathways which would cause an update to the pathway and would result in triggering.

What is triggered is based on what pathways have changed that can potentially impact pathway completion and/or evaluated mark statuses.

Evaluated marks that are not deleted with an EXCRED evaluation method tied to students who have an external credential that is tied to a pathway that has changed are triggered. The pathway has to be tied to the external credential and the student has to have a record of that external credential (regardless of status.) At the time of this writing, out of 2.3 million evaluated marks on production, only 25 have an EXCRED evaluation method.

Transcripts for students that have a certain minimum number of official mark records (regardless of status) based on the number of courses to complete for ANY pathway requirement on any pathway that has changed are triggered. For example, consider an updated pathway that has a requirement stating that the number of courses to complete the requirement is three. Any students that have at least three official marks (regardless of status) for any of the courses of the requirement would have their transcripts triggered. This approach does result in slightly more triggering than needed but the vast majority of pathways only have one requirement and this approach was chosen for simplicity. A pathway that does not have an impacting change (as described in the previous section) is not considered for triggering.

A T-sql script is used to populate the PartnerPsi table. Once a year Curriculum will validate the list of partner PSIs. Any changes to the effective and end school years will trigger the course enrolment status processor for course enrolments that are associated to the affected Prtner PSI.

This script is stored in Team Foundation Server at the following location:

• PASI.Database\Core\Scripts\Pre-Deployment\Initial Data Load

Script name: Populate_PartnerPsi

On a daily basis, the Dual Credit process will run and use the AE.dll to look-up all Partner PSIs. If the Partner PSI name has changed, the name is updated.

These tables are distinctly related to course data, but are maintained by PASI and CDA.

Dual credit definition data within PASI is made up of definitions for External Credentials, Awarding Organizations, and Pathways which includes the requirement set, requirements, and course mappings.

This information can be updated in PASI, and as a result may impact evaluated mark statuses for evaluated marks awarded students where the evaluation method is EXCRED (External Credential).
Given this potential impact, when tables housing the dual credit definition data have records inserted or modified, the evaluated mark status processors may be triggered (Evaluated Mark Status Processor Trigger).

• Note: To minimize the volume of triggers created and not impact overall PASI performance, the records triggered are limited to “active” Students.
• Note: Dual credit definitions are stored within the CDA data space, and are not part of the integration with the CIA (Course Information Application).