User Experience 2020-02-12 Meeting notes

Owned by Ann Su
Last updated: Mar 03, 2020 by Chris Moffatt (Deactivated)
1 min read

Date

Attendees

First Name

Last Name

Organization

Fred

Edora

AEM Education Services

Carolynn

Fallon

Volusia County Schools

Rick

Rozzelle

CELT

Jeremy

Thigpen

ESP Solutions Group, Inc.

Billy

Buchanan

Fayette County Public Schools

Glynn

Ligon

ESP Solutions Group, Inc.


Agenda

Student Discipline Use Case

  1. Severity code
    1. Question: In the Ed-fi data elements identified for visual, the “severity of offense” element is missing. Severity usually identified as major/minor and is attached to the incident/actions item.  Question is if data model should be modified to include this element.
    2. District experience
      1. Billy (Fayette) – district does not use severity indicator
      2. Generally, criteria for classifying major/minor is a subjective decision; code is entered based on business rules and not a calculated value.
      3. Per Happy’s (New Mexico) previous feedback – report out of ODS should include data field for severity code that’s accommodated in API
      4. Per Chris at previous meeting – mentioned there was a ticket; need to open back up for consideration

Decision:

  1. Recommend creating RFC for adding severity data field to API/ODS
    1. Roll up counts – earlier Ed-Fi dashboard provided counts
    2. Billy - Changes in enrollment affect count; underlining business logic is to create additional views of incident counts. Report shows 2 separate sets of data: 1. Enrollment count, 2. Behavioral incident counts

Action – flesh out some of the details of the business rules to identify the correct set of students from which the results would be aggregated.