User Experience 2020-02-26 Meeting notes

Date

12 Feb 2020

Attendees

Agenda

1. Flesh out some of the details of the business rules to identify the correct set of students from which the results would be aggregated
   1. Student Count - count every student enrolled within the requested time period for the requested school or district.
   2. Default values – what would make sense for default start date
      1. Erin –
         1. beginning of the year to current date.
         2. Also mentioned how some schools/orgs might prefer semantically defined time-spans such as semesters, quarters, etc…
      2. Carolynn –
         1. beginning of school year to day prior to current date
      3. Happy –
         1. beginning of school year to day prior to current date
         2. different schools have different start date, e.g. quarters/trimester; need to be flexible
      4. Billy –
         1. One challenge with semantic labels can occur when aggregating the data to the district level when schools use different semantics;
         2. Asked if the same time period criterion should be applied to all content in the use case or just some of it and participants agreed that it would be best to apply to all.

Decision:

1. Recommend reopening ticket to add a behavior severity data field to the API/ODS
2. Use defined time spans to identify the student set.
   1. Start date defaults to the start date for the academic year
   2. End date defaults to yesterday (e.g., today – 1)

Action –

• Billy said he would bring the questions about semantic time spans to the RVWG co-chairs/Ed-Fi Alliance to assess the feasibility/possibility of using durations defined by labels (e.g., 1^st semester, semester 2, etc…).