Performance measure and Staff Evaluation domain analysis

The staff evaluation domain was originally part of the TNTP set of model extensions for Ed-Fi ODS/API 2.x. These extensions were focused around the talent management pipeline and it's where the base designs for Applicants, Applications, Prospects, Surveys, and Staff Evaluation in TPDM came from.

The Staff Evaluation domain has up and to this point not realy been used. Late last year in working with a vendor partner (TeachBoost) we determined that their data fit some of performance measure fields and some data fit Staff Evaluation fields, but neither domain fit their data appropriately. TeachBoost suggested that their data would fit better if the two domains were combined.

Recently the Alliance was doing an internal review of the domains within TPDM in preparation for the upcoming TPDM RFC. After some discussion we came to the conclusion that the domains should probably be combined as they are effectively the same thing , a way to evaluate a person (Staff, Teacher Candidate, Applicant) 

We would like to see a domain that combines the two concepts, Staff Evaluation and Performance Measures  into one. 

Things that may need to be considered:

• TPDMX-109 (Goals entity) - This was submitted by TeachBoost as needed for their integration and we've had an ask from the talent pipeline people for a goals entity. This will replace the existing TalentManagementGoals entity that exists in TPDM currently 
• TPDMX-111 - Performance Measures - Lori @ UPD has submitted a new design for Performance Measures that would create a instrument/measurement type of domain similar to how surveys and assessments work (i.e. performance measure and performance measure response entities)