...
EdOrgId instead of SchoolId in DisciplineIncident Entity:
Request: There was a request to replace SchoolId with EdOrgId in the DisciplineIncident Entity.
Opinions:
Some participants saw the potential usefulness of this change.
Others opposed the change, stating it would break their reporting and that granularity at the school level is needed for state reporting.
It was suggested to hear specific use cases to understand the impact better, but knowing that the ticket was created by a Ed-Fi Alliance team member and no reference to a use case was provided the community member present at the meeting had the consensus of rejecting the proposed change due to the more complications it will introduce compared to the its benefits.
There were questions about how incidents are created at the LEA level and whether each parent school would have its own incident.
Making StudentDisciplineIncidentBehaviorAssociation a required collection in the DisciplineAction entity:
General Consensus: There was strong support for making this collection mandatory to ensure proper association of actions and behaviors.
Vendor Enforcement: It was emphasized the importance of enforcing vendors to send this data upstream.
Behavioral Associations: There was a discussion on handling multiple behavioral associations, with some participants suggesting that once the old resource is gone, the new one should be required.
Responsibility School: There was a community member asked for having the ResponsibilitySchool required, but it is already required in the current model.
...