New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reading: Allow teams to enter benchmark reading data #2352

Merged
merged 18 commits into from Jan 16, 2019

Conversation

Projects
None yet
2 participants
@kevinrobinson
Copy link
Contributor

kevinrobinson commented Jan 16, 2019

Who is this PR for?

K5 reading teams: classroom teachers, reading specialists, special education teachers, ELL teachers, literacy coaches

What problem does this PR fix?

Data is entered in spreadsheets now, which requires reading specialists to set them up and maintain them as enrollment, IEP status, etc. shift over time (or they become stale). Across the district, this involves making ~100 separate spreadsheets each year.

The spreadsheet format works great for entry, and also enables educators to make other views of the data on their own. But this takes data manipulation for looking across time over grades (eg, at DORF WPM from 2nd > 3rd grade), and is hard to use directly for critical instruction decisions like planning reading groups.

What does this PR do?

Adds a prompt on the home page for entering reading benchmark data, linking to a page for entering data in the same kind of grid format everyone's already used to. This is intended for the first pilot, so doesn't handle the general case (which we'll still need to discover across grade levels and schools). Next work is for the pilot of using this data within an A&R planning meeting for grouping, and then we'll iterate on that or grow to the next team, and migrate and remove past prototypes around reading data.

Deploying has no impact - releasing requires changes to some ENV config and labels to make this visible and authorized for specific educators.

Screenshot (if adding a client-side feature)

home page prompt

screen shot 2019-01-16 at 9 36 59 am

entry

screen shot 2019-01-16 at 9 36 41 am

Checklists

Which features or pages does this PR touch?

  • Home page
  • Reading benchmark data entry page

Does this PR use tests to help verify we can deploy these changes quickly and confidently?

  • Included specs for changes
  • Manual testing made more sense here
@studentinsights-bot

This comment has been minimized.

Copy link

studentinsights-bot commented Jan 16, 2019

@kevinrobinson, this looks like it might be worth double-checking! @kevinrobinson might be able to help.

kevinrobinson added some commits Jan 16, 2019

@kevinrobinson

This comment has been minimized.

Copy link
Contributor Author

kevinrobinson commented Jan 16, 2019

selfie

@kevinrobinson kevinrobinson reopened this Jan 16, 2019

@kevinrobinson kevinrobinson merged commit 5731471 into master Jan 16, 2019

1 check was pending

continuous-integration/travis-ci/pr The Travis CI build is in progress
Details

@kevinrobinson kevinrobinson deleted the feature/reading-entry branch Jan 16, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment