Skip to content
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

Import: GoogleSheetsFetcher for importing batches of sheets and folders #2515

Merged
merged 33 commits into from Jul 2, 2019

Conversation

@kevinrobinson
Copy link
Contributor

kevinrobinson commented Jul 2, 2019

This adds minimal commits on top of #2442, after testing for the production setup. @edavidsonsawyer did all the real work here :)

Who is this PR for?

developers, automating sync process for sheets and form responses

What problem does this PR fix?

Sometimes it's simpler for educators to collect and manage data in ways that are very specific to their context (eg, one sheet or tab for each teacher is common). When doing this across many teachers, grades or schools, there's no great way to automate importing these.

For batch uploads, we could push this work to educators and have them reformat into a standard format. But for data that we want to sync while collection is ongoing, or recurring data collection rhythms, this doesn't work as well.

For specific uses, we can add app scripts that respond to events and push data to Student Insights as it's entered or updated. This requires owning the document and another permissions step for educators.

What does this PR do?

Adds a class that uses a Google service account to allow automating this import, and setting the synchronization on the pull side. This lets educators share folders or sheets like normal, and then everything else can be automated on our end.

The first use cases are historical reading data in Somerville and transition data in Bedford. This may also be useful in the fall for self-serve imports as well (eg, service caseloads, ad hoc student voice surveys).

Checklists

Which features or pages does this PR touch?
(none)

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

  • Manual testing made more sense here
edavidsonsawyer and others added 30 commits Apr 23, 2019
@kevinrobinson kevinrobinson merged commit ccc47e1 into master Jul 2, 2019
1 check passed
1 check passed
continuous-integration/travis-ci/pr The Travis CI build passed
Details
@kevinrobinson kevinrobinson deleted the sheets_test branch Jul 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.