How do we untangle our Edly data

[chicgeek]

For the Applied Certificate Course pilot on Edly here teachers and students can login via their email OR RPF account.

Some questions some of the content team have asked are:

• Where do we record teacher data? Not scalable to store in a form.
• How do we prevent the split of the user data over two places?
• What is the best way to link student data with teacher / school data?

Thoughts:

• Data is currently in one place (Edly) - we can view and export this data on a data dashboard here. Currently:
• Every row has:
  • username
  • email
• Most rows have:
  • SSO ID
• On spot checks those rows that don't have SSO ID some have an associated RPF account (so potential for some later aggregation there too)
• Data exports (csv) can be manually requested and sent via automated email - these could in theory be imported into BigQuery much like the EdX data
• Other data inc school information is captured in external forms (see google doc)

Notes:

Potentially useful fields either in the course view or emails are:

• USER_ID & USER_EMAIL - available in both the course and emails
• USER_FULLNAME - from what I can tell only available in emails

Potentially useful course settings:

• External Login Domain

Other ideas:

• iframe a signup/login flow into the course using some of the available parameters
• dropdown for the teacher/student to select the school (due to the pilot these are all known) and fire off to some data collection mechanism (POST to lambda? - email is the only consistent field but SSO ID if available)
• send an email as we're then able to pass email and name through to enable us to forward users onto another link/service for further data collection

Questions:

• Can we block progress on the course as a result of a parameter? i.e. toggle a boolean once a login/dropdown has been selected?