...
Meeting Notes
Discussion related to Ed-Fi Validation Results API specificationDesign
- Discussed a comment in the document from Audrey Shay highlighting the fact that the current WI validation engine retains the same ID for for a validation result when data that was in error remains in error. Requiring a new ID each time would break some their existing functionality. After discussion Jon Hickam (Unlicensed)indicated that we would probably update the design to account for this.
- Audrey indicated that the WI team had also noted that there is no rule entity in the current design - which is needed to provide information about the validation rule that the result refers to. There was discussion and general agreement that this should be added to the design.
- There was discussion of how you would determine which source system was the cause of a validation error/info message. Discussion clarified that this is not in scope for the design, nor is feasible, as a L2 validation message may be the result of an interaction between multiple source systems over data that is written to the ODS. Therefore, source systems that query the Validation API for results would need account for this and direct the message appropriately.
- There was discussion related to the fact that multiple resources may be involved in a validation rule, so should the representation be 1:many. (Jon Hickam (Unlicensed)- can you clarify where we landed on this?)
...