Use Case to support promoting Staff.Credential to Domain Entity StaffCredential

Summary of outcomes for Data Standard 2.1

• Problem Addressed: For a staff with multiple credentials and multiple assignments or job positions, there is not currently a way to associate a credential with a particular assignment or job position.
• High-level Reasoning: Credential is currently a common type included on Staff. However, a staff member may have multiple job positions or assignments, each requiring a different credential. By promoting Credential to be a domain entity and referencing Credential on Staff, StaffEducationOrganizationAssignmentAssociation, and StaffEducationOrganizationEmploymentAssociation, the assignment/position to which the credential applies may be specified.
• Changes Made: Promoted Credential from common type to domain entity; Added reference to Credential on Staff as optional collection; Added optional reference to Credential on StaffEducationOrganizationAssignmentAssociation and StaffEducationOrganizationEmploymentAssociation; Added Credential to StaffAssociation interchange

Original ticket description follows:

MI state reporting requires identifying the Staff credential required by the assignment. To implement we just needed to add a Staff.Credential reference to the StaffEducationOrganizationAssignmentAssociation. However, since the Credential complex type is a common type, we were unable to implement the ReferenceType for the Staff.Credential

We resolved the issue by:
1. creating a StaffCredential domain entity - contained a StaffReference AND the Credential fields - plus a few additional that MI required.
2. creating a StaffCredentialReferenceType
3. then extending the StaffEducationOrganizationAssociation with a StaffCredentialReferenceType.

The downside to this solution is that we had to leave the existing Staff.Credential in place since the build process cannot handle restrictions.