Transition notes: Support limited transition from 5th > 6th in Somerville #2495
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
selfie |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Who is this PR for?
Students and families in 5th grade at once school, transitioning schools
What problem does this PR fix?
Help support counselors and admin in transitions across years and buildings.
What does this PR do?
Extends the 8th > 9th grade transition to be used in a similar way for counselors and admin in one school for students transitioning schools at 6th grade. This maps mostly directly to the 8th > 9th grade transition, in particular with how restricted information is handled.
Separately, other schools with program shifts where students switch buildings will do this also, but in different ways (eg, Somerville Argenziano program, Bedford elementary schools), and those import processes can be tackled separately in the summer so they're all ready for the fall. They may re-use parts of the model or UI here but for now this PR punts on that to the minimal change needed during the time before the end of the school year.
As a caveat, for folks working K5 with districtwide access, the "Jump to next student" isn't smart enough to know they are only doing this for a smaller subset of students, but they can workaround using the "School transitions page."
Checklists
Which features or pages does this PR touch?
Does this PR use tests to help verify we can deploy these changes quickly and confidently?