MTSS: Add minimal semi-automated importer for MTSS referral form#2361
Merged
kevinrobinson merged 3 commits intomasterfrom Jan 18, 2019
Merged
MTSS: Add minimal semi-automated importer for MTSS referral form#2361kevinrobinson merged 3 commits intomasterfrom
kevinrobinson merged 3 commits intomasterfrom
Conversation
|
@kevinrobinson, this looks like it might be worth double-checking! @kevinrobinson might be able to help. |
Contributor
Author
|
selfie |
This file contains hidden or 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
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?
K8 MTSS teams
What problem does this PR fix?
An experiment with supporting a variant on the MTSS protocol where an educator meets with a student before the MTSS meeting, and then reviewing the student's perspective is how the MTSS meeting starts.
What does this PR do?
Adds an importer to read data from the MTSS referral form and map it to flat
EventNoteattributes, intended for semi-automated use on the console for now.Screenshot (if adding a client-side feature)
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?