Understanding Compare Processing for Register (ITT)

Processing that's similar to the Student return is available for ITT trainee teachers (Register).

After the initial extract of data, if the compare parameter is selected, the extract entity and fields are compared with the corresponding submitted data record to determine which records are new, which have changed, and which are unchanged. The Entity Status and Field Status values of the extract records are updated to indicate where the record or field needs to be reported to Register.

The processing is only done if the Compare Extract with Submitted checkbox is selected on the Create Extract Data page.

The entity submitted data records are keyed on Institution, Return Type, Effective Date, Effective Sequence and then the unique keys for the particular entity record. The related submitted data fields records also include Field (SSR_HE_FIELD) in the key. The comparison is done against the most recent effective dated/sequenced record for the Institution and Return Type (namely, ITT) in the submitted data for the keys values for each entity.

Unlike DFSTDNT, there's no requirement to indicate parent entities with the Entity Status of Identify in cases where there's no change to the entity itself or its fields. It's required in DFSTDNT to include the parent entity in the XML file, but it isn't required when sending records via the Register API. New and updated Degree and Placement entities can be sent independently from the student/trainee.

The Register API allows deletion of Placement and Degree records. The compare processing will create extract records for Placements that have previously been reported for the current reporting period but are now not applicable to the trainee. The Entity Status will be set to Delete. Since only one Degree entity is reported, the existing record will be updated rather than a new record being added and the existing record deleted.

The unique Register identifiers for each entity are stored in the submitted data record. The comparison will populate the unique identifier in the extract record when it's matched to an existing record in submitted data. The unique identifiers will then be used for PUT and DELETE requests as part of the Export Trainees process.