Background:
Several times a year Jana Arpy from ITS needs to upload new CSV data mapping student ID #s to emails (for Pepsico).
e.g. on the old deployment at : https://osl-events-app.firebaseapp.com/upload/
or maybe the newer https://vike-web.vercel.app/upload , except that the Google login seems to be broken on the vercel domain one.
-
Currently, it's uploading into the realtime DB within firebase at this tree location: /id-to-email-test
a) But it should be going directly into: /id-to-email
b) Also, it should be REPLACING the contents of that whole tree, rather than always adding more users!
c) (Furthermore, the performance of uploading each individual row is VERY bad -- instead, we should create a Javascript object that represents the whole subtree (containing all of the id:email pairs, and then use set() to replace the whole /id-to-email subtree in one single firebase operation!)
-
The original plan was to include a bunch of demographic data about students as well, so that OSL could use that to generate reports about how many first year students, women, international students, etc, were attending different events.
However, there are too many privacy concerns about that data, so we should just purge all of the demographic data from our database, and ALSO change the upload code to avoid inserting any demographic data (from the CSV file) into it in the first place! We only want to upload the id->email pairs.
Background:
Several times a year Jana Arpy from ITS needs to upload new CSV data mapping student ID #s to emails (for Pepsico).
e.g. on the old deployment at : https://osl-events-app.firebaseapp.com/upload/
or maybe the newer https://vike-web.vercel.app/upload , except that the Google login seems to be broken on the vercel domain one.
Currently, it's uploading into the realtime DB within firebase at this tree location:
/id-to-email-testa) But it should be going directly into:
/id-to-emailb) Also, it should be REPLACING the contents of that whole tree, rather than always adding more users!
c) (Furthermore, the performance of uploading each individual row is VERY bad -- instead, we should create a Javascript object that represents the whole subtree (containing all of the id:email pairs, and then use set() to replace the whole
/id-to-emailsubtree in one single firebase operation!)The original plan was to include a bunch of demographic data about students as well, so that OSL could use that to generate reports about how many first year students, women, international students, etc, were attending different events.
However, there are too many privacy concerns about that data, so we should just purge all of the demographic data from our database, and ALSO change the upload code to avoid inserting any demographic data (from the CSV file) into it in the first place! We only want to upload the id->email pairs.