Define new Program Evaluation Model

This ticket addresses similar requests for model extensions for evaluations of students associated with a program:

• DATASTD-1890 Early Childhood Outcomes – to capture the child outcomes indicator SPPI-7 for early childhood evaluations
• EDFI-1990 AZ-Collecting 21st CCLC survey data – a simple form filled out by a teacher for a student

Both of these reflect Evaluations done regarding a Student for a Program. There are likely many other examples across the various programs.

On EPDM, a model was developed for evaluating Teachers and Teacher Candidates, explained in the following:
Performance Evaluation Domain - Educator Preparation Programs (EPPs) - Ed-Fi Tech Docs

The EPDM evaluation model reflects the same type of metadata–results pattern used in assessment and in survey. My direction is to adapt this as follows:

• The EPDM model supports rubric-based evaluations, quantitative measures, and survey results – for Program Evaluations it seems only a rubric evaluation is required
• The EPDM model is heavily based upon a numeric averaging of the various rubric score that may or may no be used for Program Evaluations.
• The EPDM model supports goals, which do not immediately seem to apply – though this may not be the case of IEP data were to be represented
• The EPDM model is a 4-level model which supports bringing together different evaluations into a single rating of performance – my sense is that Program Evaluations do not need this highest level and could use a simpler model
• The EPDM model includes an Evaluation Objective level that allows multiple rubric entries to be grouped. The 21st CCLC questions are a simple set of three questions that would not require this level. The SPPI-7 is similarly pretty simple, though it could be expanded as per three-child-outcomes-breadth.pdf (ectacenter.org). The recommendation is to keep the Objective level and go with the 3-level model. Perhaps we could structure the linkages to support both a 2- or 3-level model as is done for assessments.
• The associations would change: required (key) links to Student & Program (GeneralStudentProgramAssociation?), optional link to the Staff doing the evaluation
• Reevaluate the various attributes for this use case. For example, likely needs an optional descriptor for Entry or Exit evaluations.