Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upMTSS: Add minimal semi-automated importer for MTSS referral form #2361
Conversation
kevinrobinson
added some commits
Jan 17, 2019
This comment has been minimized.
This comment has been minimized.
studentinsights-bot
commented
Jan 18, 2019
|
@kevinrobinson, this looks like it might be worth double-checking! @kevinrobinson might be able to help. |
This comment has been minimized.
This comment has been minimized.
|
selfie |
kevinrobinson
merged commit c850894
into
master
Jan 18, 2019
1 check passed
continuous-integration/travis-ci/pr
The Travis CI build passed
Details
kevinrobinson
deleted the
feature/mtss-import
branch
Jan 18, 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.
kevinrobinson commentedJan 18, 2019
•
edited
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?