1.0 | Sending a staff member with multiple LEA associations and different email addresses | A staff member works across multiple LEAs and needs to be associated with each LEA they are working with, along with their contact information. Prerequisites: The following records need to be posted to the WISEdata API before posting the /staffEducationOrganizationContactAssociations resource: Either the /staffEducationOrganizationAssignmentAssociation record (this endpoint is populated from WISEid), Or the /staff and /staffEducationOrganizationEmploymentAssociations
SIS vendors/LEAs should provide the Contact Title as configured in the SIS. | LEA 1 POST on /staffEducationOrganizationAssignmentAssociations: contactTitle: e.g School educationOrganizationReference: educationOrganizationId: 7525 staffReference: staffUniqueId: 1001001001 electronicMailAddress: "staff@LEA1.com" LEA 2 POST on /staffEducationOrganizationAssignmentAssociations: LEA 1 POST on /staffEducationOrganizationAssignmentAssociations: contactTitle: e.g School educationOrganizationReference: educationOrganizationId: 1234 staffReference: staffUniqueId: 1001001001 electronicMailAddress: "staff@LEA2.com" |
---|
2.0 | Update the staffEducationOrganizationAssignmentAssociations | If the updated data property is a primary key, then vendors will need to insert a new record, then delete the old staffEducationOrganizationAssignmentAssociation record. If the updated data property is NOT a primary key, then vendors would simply update the data property for an existing staffEducationOrganizationAssignmentAssociation record. | PUT on /staffEducationOrganizationAssignmentAssociations |
---|
3.0 | Delete the staffEducationOrganizationAssignmentAssociations | The staffEducationOrganizationAssignmentAssociation record can be deleted without requiring the deletion of any associated child records first. | DELETE on /staffEducationOrganizationAssignmentAssociations |
---|