Question: Could this be the beginnings of mapping to dashboards?
We need to document fields used to integrate student (West Windsor specific) and assessment information (NWEA for all future NWEA clients) from secondary sources to our MTSS Platform.
West Windsor has NWEA for reading and math grades K-12, Attendance, Behavior and uses Genesis for everything.
RethinkEdStudents_Export.csv
Field Name: School Year
Data Areas: All
Locations in MTSS Dashboard: All
Description: Contains school year,
Value: shown as YYYY-YY. Example: 2023-24
UI
Acceptance Criteria
Used in all areas to contain data sets to a specific school year within the year drop down.
Field Name: Enrollment Status
Data Areas: All
Locations in MTSS Dashboard: All
Description: confirms student is enrolled,
Values: Active
UI
No UI.
Acceptance Criteria
Used in all areas to denote if student is Enrolled.
Used in conjunction with other fields to tie to student to correct information.
Question: Is this field used to eliminate a student from counts in graphs so that proper counts of students are included with no duplicates
Field Names: First Name, Last name
Data Areas: All
Locations in MTSS Dashboard: Classroom, Student
Description: Student’s first name, Student’s last name
Values: Text varies
UI
Acceptance Criteria
Used in conjunction with other fields to identify student and tie to student to correct information.
Field Name: Grade Level
Data Areas: All
Location in MTSS Dashboard: All
Field Description: Student’s grade level
Values: Integer
No UI
Acceptance Criteria
Used in conjunction with other areas to place student within the correct grade level and correct school year.
Field Name: State IDNumber
Data Areas: All
Location in MTSS Dashboard: All
Field Description: Unique Student Identifier for the state in which the student lives
Values: Integer
No UI
Acceptance Criteria
Used in conjunction with other fields identify the correct student and tie student to correct information
Field Name: Spec Ed, Gender, Ethnicity Primary, Date of Birth
Data Areas: All
Location in MTSS Dashboard: All
Field Description: Demographic information
Values:
Spec Ed = No, Yes
Gender: Male, Female, Non-binary, Not specified
Ethnicity Primary: American Indian or Alaska Native, Asian, Black or African American, Hispanic or Latino, Native Hawaiian or Other Pacific Islander, Two or More Races, White
Date of Birth: MM/DD/YYYY
Shows up within Student Profile and in filters
Acceptance Criteria
Used in conjunction with other fields identify the correct student and tie student to correct information
Values used to fill filters in all areas of the dashboard.
ReThinkEdStudent_school_enrollment.csv
Field Name: School Year
Data Areas: All
Location in MTSS Dashboard: All
Field Description: Names the school year
Values: shown as YYYY-YY, Example 2023-24
UI
Acceptance Criteria
Used in all areas to contain data sets to a specific school year within the year drop down. (Not sure which we follow as school year is shown in multiple data sets)
Field Name: Enrollment Status
Data Areas: All
Location in MTSS Dashboard: All
Field Description: Tells if student is Active
Values: shown as Active
UI
No UI
Acceptance Criteria
Used in all areas to denote if student is Enrolled.
Used in conjunction with other fields to tie to student to correct information. (Not sure which we follow for Enrollment Status since it is shown in multiple data sets)
Field Name: Student ID
Data Areas: All
Location in MTSS Dashboard: All
Field Description: Unique student identifier
Values: Integer
UI
Student ID is shown in Student Dashboard
Acceptance Criteria
The unique student identifier must be the same across the different types of data so that RethinkEd can link all data types back to the same student in our platform
Used in conjunction with other fields to tie to student to correct information. (Not sure which we follow for Student ID since it is shown in multiple data sets)
Field Name: Current Entry in District
Data Areas: All
Location in MTSS Dashboard: All
Field Description: Tells the date student entered the district
Values: Date, shown as MM/DD/YYYY
UI
No UI
Acceptance Criteria
This field could be used to keep graphs up to date.
Field Name: Current Withdrawal Date
Data Areas: All
Location in MTSS Dashboard: All
Field Description: Tells the date student left the district
Values: unknown; no entries are in the data set
UI
No UI
Acceptance Criteria
This field could be used to keep graphs up to date, it could also help to ensure that students are not counted multiple times.
ReThinkEdBehavior_Export.csv---Genesis Data?
Field Name: School Year
Data Areas: Behavior
Location in MTSS Dashboard: Behavior
Field Description: Tells the school year the behavior occurred
Values: shown as YYYY-YY, Example 2023-24
UI
Acceptance Criteria
Used in Behavior Section to contain data within a specific year.
(Not sure which we follow as school year is shown in multiple data sets)
Field Name: Student ID
Data Areas: Behavior
Location in MTSS Dashboard: Behavior
Field Description: Unique student identifier
Values: Integer
UI
No UI
Acceptance Criteria
Used in Behavior Section to match student to Infraction Date
The unique student identifier must be the same across the different types of data so that RethinkEd can link all data types back to the same student in our platform
Field Name: Infraction Date
Data Areas: Behavior
Location in MTSS Dashboard: All Graphs at all levels (District, Classroom, Student)
Field Description: Date the infraction
Values: shown as MM/DD/YYYY
UI
Acceptance Criteria
This shows without the use of our Behavior Incidents
Student View (Behavior Tab)
Show the infraction date in the chart
Used in conjunction with Student Id to match student with infraction
Used to calculate the number of infractions for determining Tiers
Used to calculate the number of infractions for determining when to send Tier Notices when no intervention plan exists.
Used to calculate the number of infractions for determining At Risk indicators.
Used to calculate the span of time between infractions as determined in Setting for when a student is returned to Tier 1.
Student View (Overview Tab)
Used to determine a count of students within the grade level for each of the tiers within the graph
Classroom Dashboard (Overview Tab)
Used to determine the counts for each tier level shown in the graph for the selected classroom
Classroom Dashboard (Behavior Tab)
Used in conjunction with Define School year to determine placement in the appropriate graph for the classroom
District View (Overview Tab)
Used to determine the counts for each tier level shown in the graph for the entire district
District View (Behavior Tab Selected)
Used in conjunction with Define School year to determine placement in the appropriate graph for the entire district
ReThinkEdAttendance_Export.csv---Genesis Data?
Field Name: School Year
Data Areas: Attendance
Location in MTSS Dashboard: Attendance Graphs in overview and Tabs in all areas: District, Classroom, Student
Field Description: Tells the school year of the Attendance records
Values: shown as YYYY-YY, Example 2023-24
UI
Acceptance Criteria
Used in all areas to contain data sets to a specific school year within the year drop down. (Not sure which we follow as school year is shown in multiple data sets)
Field Name: Student ID
Data Areas: Attendance
Location in MTSS Dashboard: Attendance Graphs in overview and Tabs in all areas: District, Classroom, Student
Field Description: Unique student identifier
Values: Integer
UI
No UI
Acceptance Criteria
Used in Attendance Section to match student to the date an Absence or Tardy occurred
The unique student identifier must be the same across the different types of data so that RethinkEd can link all data types back to the same student in our platform
Field Name: Date
Data Areas: Attendance
Location in MTSS Dashboard: Attendance Graphs in overview and Tabs in all areas: District, Classroom, Student
Field Description: Date the Absence or Tardy occurred
Values: show as MM/DD/YYYY
UI
Acceptance Criteria
Used in Attendance Section to match student to the date an Absence or Tardy occurred
Used in conjunction with the Attendance Code to determine if an Absence or a Tardy is to be recorded for that date.
Field Name: Attendance Code
Data Areas: Attendance
Location in MTSS Dashboard: Attendance Graphs in overview and Tabs in all areas: District, Classroom, Student
Field Description: Code to determine if the date shown is an absence or a tardy
Values: show as MM/DD/YYYY
UI
Acceptance Criteria
Used in Attendance Section to match student to the date an Absence or Tardy occurred
1 or A or ABU = absence, U or T = tardy, exclude SRE and 6 and other values not listed here from attendance metrics
Assessment Fields (NWEA-Map specific)
Need to add: maybe Year, School, Enrollment, Last Name, First Name, Demographics? or site theses as “checks” for other integrated fields?
Rethink Ed Field Name: CompletedDateLocal
NWEA Field Name: TBD; Use the date it came it
Data Area: Academic Assessments
Field Description: date (and time if available) stamp for when the assessment was completed
UI
Acceptance Criteria:
Essential field (fields marked as essential or optional for academic assessment data only; assume fields for all other data types are essential).
Rethink Ed Field Name: ScaledScore
NWEA Field Name: OverallRITScore
Data Area: Academic Assessments
Field Description: scale or raw score for the assessment
UI
Acceptance Criteria:
Essential field
Rethink Ed Field Name: GradeEquivalent
NWEA Field Name: Assessment Grade
Data Area: Academic Assessments
Field Description: grade level equivalent based on assessment performance
UI
Acceptance Criteria:
Optional field
note: iReady has a slightly different field than Renaissance
Rethink Ed Field Name: PercentileRank
NWEA Field Name: Test Percentile
Data Area: Academic Assessments
Field Description: percentile rank
UI
Acceptance Criteria:
Essential field
Rethink Ed Field Name: BenchmarkCategoryName
NWEA Field Name: use High, High Average, Average, Low Average, Low associated with Tier selection in Settings
Data Area: Academic Assessments
Field Description: benchmark category label for student (eg, “Proficient”, “Partially meeting expectations”)
UI
Acceptance Criteria:
Essential field
Rethink Ed Field Name: ScreeningPeriodWindowName
NWEA Field Name: TBD: Month
Data Area: Academic Assessments
Field Description: name of screening period (e.g. “Fall 2023”, “Q1 2024”)
UI
Acceptance Criteria:
Optional field
Rethink Ed Field Name: ExtraTime
NWEA Field Name: TBD; nothing so eliminate it.
Data Area: Academic Assessments
Field Description: whether student was given extra time to complete the assessment
UI
Acceptance Criteria:
Optional field
Note: Renaissance and iReady have a different field. We are looking for some measure of time the student used to take a test; Duration or just noting that the test time was longer or shorted than anticipated.
Rethink Ed Field Name: ScreeningWindowStartDate
NWEA Field Name: TBD; nothing so eliminate it
Data Area: Academic Assessments
Field Description: start date for the given ScreeningPeriodWindowName
UI
Acceptance Criteria:
Optional field
Rethink Ed Field Name: ScreeningWindowEndDate
NWEA Field Name: TBD; nothing so eliminate it
Data Area: Academic Assessments
Field Description: end date for the given ScreeningPeriodWindowName
UI
Acceptance Criteria:
Optional field
Rethink Ed Field Name: SubjectArea
NWEA Field Name: TBD; Exam or Test
Data Area: Academic Assessments
Field Description: subject area for assessments (e.g. “ELA”, “Math”) if not evident from data file name
UI
Acceptance Criteria:
Essential field if not evident from data file name (e.g. “ELA assessment results”)
Rethink Ed Field Name: StateIdentifier
NWEA Field Name: TBD: State ID
Data Area: Academic Assessments
Field Description: child/student state identifier
UI
Acceptance Criteria:
Important note: Either this sate identifier or the Student ID for this file must be the same across the different types of data so that RethinkEd can link all data types back to the same student in our platform.
Rethink Ed Field Name: StudentNumber
NWEA Field Name: TBD: ?
Data Area: Academic Assessments
Field Description: child/student identifier
UI
Acceptance Criteria:
Important note: Either this student identifer or the StateIDNumber for this file must be the same across the different types of data so that RethinkEd can link all data types back to the same student in our platform.