Details
-
Improvement
-
Resolution: Done
-
Major
-
None
-
None
Description
Summary of outcomes for Data Standard 3.3.0-a
- Problem Addressed: Some SIS tie student Behavior descriptor values to individual Discipline Actions. The current model ties Behavior to Discipline Incidents but can only be referenced as a collection to Discipline Action via DisciplineAction DisciplineIncidentReference.
- High-level Reasoning: This is a common use case not currently handled in the data model. The workaround is clumsy as it requires a separate DisciplineIncident record (or StudentDisciplineIncidentAssociation record) for each Behavior.
- Changes to be Made: Split out Behavior as a particular association, StudentDisciplineIncidentBehaviorAssociation. Non-offender associations would then go to a new StudentDisciplineIncidentNonOffenderAssociation. And finally a new reference on DisciplineAction can be added for the SDIBA . Behavior as a collection can still be added to a DisciplineIncident record. Ideally, this would include all behaviors associated with the incident. Then the SDIBA could be used to assign the proper subset of those behaviors to individual students. And finally the reference on DisciplineAction would tie specific behaviors to the subsequent actions. Additional documentation on how to assign values to these different instances of Behavior will be included in techdocs. StudentDisicplineIncidentAssociation, will be deprecated.
Original Description:
Currently, the data standard has the Behavior collected in either the DisciplineIncident or the StudentDisciplineIncidentAssociation. Nebraska chooses to use the Behavior in the SDIA. We also allow more than one Behavior to be reported per student/incident. However, when the discipline action is then reported in the DisciplineAction resource, there is no way to tie each Action to the specific Behavior in the SDIA. This means that we end up with duplicated actions when we link the two tables.
We would like to see an association between the specific behavior and the discipline action.
Attachments
Issue Links
- relates to
-
DATASTD-1569 Update UML for StudentDisciplineIncidentNonOffenderAssociation
- Closed
-
DATASTD-1430 Duplication of Behavior in Discipline Domain
- Closed
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...