Reflection: Patterns within notes #2683
Merged
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 |
This was referenced Oct 30, 2019
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?
SHS educators in a workshop, to start
What does this PR do?
Adds a reflection tool for looking at patterns in how students are written about within Student Insights. This is still early, but the idea is to center how individual students are talked about (rather than how individual educators write), and to focus on students that are written about the most within Student Insights. The intention is to help focus ask questions about reflecting whole-child and strengths-based perspectives. Notes are scoped to student-level authorization, and to the current school year only (anything restricted is excluded, even if the educator would have access in other contexts).
This page is behind a label, and not exposed in the UI right now. It'll be prototyped in a workshop first before any wider training or release.
Screenshot (if adding a client-side feature)
(word cloud omitted)
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?