Submission Workspace Matching
Sibling Verification
School and district staff can now use the Submission Workspace Matching to Verify Siblings using Sibling Verification Feature. Up to four matches can be performed against each record (1 for a Primary Student and 3 for Siblings). Matching for each student can be supported via both the default matching logic and Enhanced Match Criteria.
Performing Match on Primary Student and Siblings
Sibling Verification is supported via Automatic Matching and Manual Matching using a Match Window.
Match Conditions
The match status of each will be updated in the respective property (Primary Student: SWMMatchStatus; Sibling 1: SWMMatchStatusSibling1; Sibling 2: SWMMatchStatusSibling2; Sibling 3: SWMMatchStatusSibling3):
Matched- if matchedPotentialMatches- if no match but at least one potential match foundNoMatch- if no potential matches foundUnMatched- if matching has not yet occurredempty if there is no data in the submission record to be matched against
The
SWMAllStudentsMatchedproperty will be updated:1- if all students/siblings are eitherMatched,NoMatch, or empty0- if at least one student/sibling isPotentialMatchesorUnMatched
A match orb will be shown horizontally for each student that was attempted to be matched, and its color will reflect its match status.
The match orbs will contain tooltips in the format of $Student: $First $Last ($DoB)
For example,
Student: John Doe (01/01/2000)For example,
Sibling 1: Jane Doe (01/02/2001)
The matched student record in PS SIS is imported into the submission record, including data from:
Core Students table
1-1 extensions off of the Students table
OTM extensions off of the Students table
Match Errors
When the match process results in an error, click the error icon to navigate to the data delivery review page.
Reset Match
School and District Staff can also perform a Reset match against a Student or Sibling within a record. When the user resets the match status for a submission record, the match status of each property (Primary Student: SWMMatchStatus; Sibling 1: SWMMatchStatusSibling1; Sibling 2: SWMMatchStatusSibling2; Sibling 3: SWMMatchStatusSibling3) will be updated:
Matched- if matchedPotentialMatches- if no match but at least one potential match foundNoMatch- if no potential matches foundUnMatched- if matching has not yet occurredempty if there is no data in the submission record to be matched against
The
SWMAllStudentsMatchedproperty will be updated:1if all students/siblings are eitherMatched,NoMatch, or empty0if at least one student/sibling isPotentialMatchesorUnMatched
Any of the Match Found or No Match Found tags defined in the SWM configuration will be removed from the submission record.
Match Siblings using Student Number and Birth Date
This feature supports matching siblings (the non-primary students within a submission record) using the Student Number and Date of Birth. When this option is enabled, a sibling will be matched if there is exactly one active or pre-registered student in PowerSchool SIS with an exact match on Student Number (Students.Student_Number) and an exact match on Date of Birth (Students.DOB). This enhancement is used in conjunction with the Sibling Verification feature.
No match will be performed if there are no active or pre-registered student records with an exact match on Students.Student_Number and an exact match on Students.DOB.
When a Match is performed for Sibling (Secondary Student) using a Match window, the records will be displayed as potential matches within the Match Window, when there is at least one active or pre-registered student with an exact match on Students.Student_Number and an exact match on Students.DOB.
The Students.Student_Number and Students.DOB is mandatory and if it is empty, upon clicking the match action on the individual record in the Pending Match view, School or District users will see the error icon. You can see the error message mentioned when hovered on the error icon. Click the error icon to navigate to the data delivery review page.
Enhanced Match Criteria
Enhanced Match Criteria is available for the Submission Workspace Matching feature. School or District users can use Enhanced Match Criteria for delivery schemas having Submission Workspace Matching record type. Enhanced Match Criteria requires First Name, Last Name, and Date of Birth to perform Matching. If these values are not available, on performing an individual match, the record will not be matched; Users will get an error when performing a match task on a batch and records will be skipped. Use of Enhanced Match Criteria within Submission Workspace Matching is applicable for batch load and match window.
When the Enhanced Match Criteria is disabled on the delivery target associated with the SWM pending match view, the student match for SWM will continue to leverage its own custom match criteria as follows.
The Auto-Match to Student when One Exact Match Found option from the same page (delivery target associated with the SWM pending match view) is necessary to match the record automatically when One Exact Match is Found.