Closed gedankenstuecke closed 6 years ago
Memo for me: The processing code used so far can be found in https://github.com/OpenHumans/open-humans-data-processing/blob/master/sources/twenty_three_and_me
I got the current processing code updated to py3
to be used in the stand-alone deployment. It still needs to be refactored and there are no tests so far (which is the same for the old integrated version)
BASE_URL
can now be changed to more easily test against stagingohapi
AWS S3 methodmanagement task
to re-queue all files that haven't been processed so farhttps://oh23andmesource.herokuapp.com
and tested itIMPORTANT NOTE: If you're an existing 23andMe integration user you don't have to upload your data again, we will merge this into a single application in the next steps!
Plan for wrapping up:
Add management command to make CSV dump of all project member IDs + refresh tokens.
The oh-23andme-source
now has a simple import function that takes project_member_id
s and refresh_token
s from a CSV to import the existing users in the standalone project.
@madprime Do you agree that all things here are taken care of as checked off above and we can successfully close the first step in moving over our legacy projects? 🙏
And done! 👍
oh-23andme-source
repo to import users from old legacy activityWe want to move away from having some data sources integrated right on the main site as it's a PITA to maintain and leads to all sorts of problems. We've roadmapped out the general workflow and file-based uploads should be a good start to test it out.