Join periodic export using the data scheme provided by evalytics - Githubissues

vusaverse / evalytics

Data pipeline for evalytics data.

MIT License

0 stars 0 forks source link

Join periodic export using the data scheme provided by evalytics #1

Open Tomeriko96 opened 4 weeks ago

Tomeriko96 commented 4 weeks ago

https://187350916-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MUKhoh5rgfVskIr1bwi%2Fuploads%2FVssIOQb6tnLbMCj5E898%2Fdata-export.svg?alt=media&token=cfbd13aa-0af7-4b93-8354-136c671c342b

Tomeriko96 commented 3 weeks ago

Step 1: Simple joins

[x] evaluationToLabel --> evaluationLabel
[x] questionToLabel --> questionLabel
[x] subjectToLabel --> subjectLabel
[x] subjectGrade --> subjectGradePeriod
[x] subjectTopicType --> subjectTopicTypeTeacher
[x] questionScale --> questionScaleValue

See note: https://github.com/vusaverse/evalytics/issues/1#issuecomment-2167381277

[ ] genericTopicLabel --> genericTopicToLabel

Step 2: Multiple joins

[x] question --> questionToLabel
[x] question --> questionScale

[ ] topicType, https://github.com/vusaverse/evalytics/issues/2
[ ] organisation, https://github.com/vusaverse/evalytics/issues/3

Tomeriko96 commented 3 weeks ago

Note:

In our exports we found that genericTopicLabel and genericTopicToLabel were empty.

Tomeriko96 commented 3 weeks ago

Note regarding joining the question dataset with the questionScale and questionLabel data.

As questionScale has all the values of the scales, this will cause the dataframe to be longer, as we match each question hash to each scale