User Experience 2019-12-11 Meeting notes

Date

11 Dec 2019

Attendees

Goals

Review Metric Priority and Refine Use Case
Metric Priority Survey Comments
Open Items
Data Element Review

Discussion items

Metric Description/Link:		votes to include	priority
Number/Percentage of incidents by type/code and demographic - for district or school	top 30%	6	2
Incidents, location, date, action taken by student (with accompanying demographics)	top 30%	6	1
Students with multiple incidents (by severity: major and minor)	top 30%	6	3
Number/Percentage of offenses by geo location and type/code, demographic	2nd 30%	6	4
Number/Percentage of incidents by time of day and incident code, demographic	2nd 30%	6	6
Number/Percentage of actions taken by type/code and demographic - for district or school	2nd 30%	5	5
Number of major/minor incidents by school	lowest 40%	5	7
Number/Percentage of Incidents reported by reporter type and incident code, demographic	lowest 40%	4	8
Number/Percentage of actions taken by reporter staff and type/code, demographic	lowest 40%	2	9
Percentage of students who are repeat offenders	lowest 40%		10

Item	Who	Notes
Metric Priority	rrozzelle	Discuss top three metrics Number/Percentage of incidents by type/code and demographic - for district or school Incidents, location, date, action taken by student (with accompanying demographics) Students with multiple incidents (by severity: major and minor)
Survey Comments	rrozzelle	Where data is disaggregated by demographics, please make sure that there not only is a column for the total count but there's also a column for total percentage. The problem that I had with the ranking is that it depends on the user. A district-level Director of Student Services would probably start by scanning the level of incidences at each site and then dig deeper into the types of incidences and if there are patterns with location or time of day because that can affect support to the schools. A school-based counselor or administrator may be more interested in seeing which students have multiple incidents and digging deeper into factors that may be affecting that individual student's behavior. In a system, both the high level summary data and the individual data is valuable; the priority may vary by type of user though. Argues for metric 1 and 7 and 8 – this should cover it We should have a way to report actions/disciplinary responses conditional on the type of infraction across demographic groups; this is a typical thing that the Office of Civil Rights requests in consent decrees and is also useful to illustrate equity in punishment. It would also be important to show the duration of things like in/out of school suspensions since they result in missed instructional time. If there is a way to drill down in the dashboard it may be more effective to use multiple dashboard elements for each of the distinct demographic groups which then allow users to drill down to individual student-level data for detailed information. Also, it may be useful to consider that not all organizations define major/minor events; so what would the contingency be for those instances so a single piece of content could be used to satisfy both cases? Maybe using a multiple select filter/slicer would make things a bit more flexible across more use cases? Add this as a row under each suspension type in the actions taken metric?? This is addressed under incidents by students Itzel: discussed at general session: data is there but visualization might be different; ideal to map what kind of action apply to what incident and to whom for one of the top three metrics Itzel: dashboard drill down - how much to put into one report to allow drill down Just a note, I think that the "Number/Percentage of incidents reported by reporter type..." is mislabeled, compared to the example in the spreadsheet I think this should say "reporter staff". Severity is not in the data model - will need a filter ReportName is the data field in Ed-Fi
Open Items	rrozzelle	Showing the percentage of attendance from the time a student is enrolled rather than just reporting the absence. Itzel: Tech team to discuss this afternoon, consensus is to address this as an option How to flag chronic absenteeism (10% or more of total days enrolled) Rick: Flag chronic absences in red on the student report? Do we want to also see excused and unexcused absences? Rick: reported under chronic absenteeism Itzel: too much information in one report? Metric Roll up - which metrics roll up and how the rollup amounts are reported. Itzel: Tech team: how to roll it up; need to define top level to drill down; flash out visualization Rick: top level = district, next = school, last = classroom Incident Severity Levels: How do we identify major/minor?
Data Elements	rrozzelle

Data Element Name - Ed-Fi	Description
Name	Full legal name of the person.
StudentUniqueId	A unique alphanumeric code assigned to a student.
SchoolId	The identifier assigned to a school.
School	School enrolling the Student.
EntryDate ExitWithdrawDate	The month, day, and year on which an individual enters and begins to receive instructional services in a school. The month, day, and year of the first day after the date of an individual's last attendance at a school (if known), the day on which an individual graduated, or the date on which it becomes known officially that an individual left school.
ResponsibilitySchool	School responsible for student's discipline.
AttendanceEventCategory EventDate	A code describing the attendance event, for example: Present Unexcused absence Excused absence Tardy. Date for this attendance event.
	Student Race/Ethnicity, ELL, SPED (and disability code)
	Student Gender
	Student socio-economic status
	Date of Birth
	Grade level
IncidentIdentifier	A locally assigned unique identifier (within the school or school district) to identify each specific DisciplineIncident or occurrence. The same identifier should be used to document the entire DisciplineIncident even if it included multiple offenses and multiple offenders.
Behavior	Describes behavior by category and provides a detailed description.
School	Relates the DisciplineIncident to the school where the incident occurred.
IncidentDate	The month, day, and year on which the DisciplineIncident occurred.
IncidentTime	An indication of the time of day the incident took place.
IncidentLocation	Identifies where the DisciplineIncident occurred and whether or not it occurred on school, for example: On school Administrative offices area Cafeteria area Classroom Hallway or stairs ...
no Ed-Fi element for this	Severity of offense - major/minor
Discipline	Type of action, such as removal from the classroom, used to discipline the student involved as a perpetrator in a discipline incident.
DisciplineActionIdentifier	Identifier assigned by the education organization to the DisciplineAction
DisciplineDate	The date of the DisciplineAction.
DisciplineActionLength	The length of time in school days for the DisciplineAction (e.g. removal, detention), if applicable.
StudentDisciplineIncidentAssociation	Reference to the DisciplineIncident associated with the DisciplineAction.
ReporterName Staff	Identifies the reporter of the DisciplineIncident by name. Identifies the staff reporter of the DisciplineIncident by use of a pre-existing school or district unique identifier.

Action items

Itzel Torres (Deactivated) Conduct Working session with Teach Team this afternoon on how to present the data; narrow down what they want to use as architecture, proof of concept to test out some of the theories
Itzel Torres (Deactivated) Put top three metrics into use cases; have this group collaborate with Tech Team beginning of next year