-
Couldn't load subscription status.
- Fork 6
Feat: privacy-conscious appointment stats #1210
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
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh... I think we tried to partially solve the same thing 🙈.
Last week, I added #1206 trying to avoid the zoom meeting report because of the issues you described
- Not being able to identify users accurately
- Not having any infos on non-zoom meetings
| export async function populateAppointmentStats() { | ||
| logger.info('Populating appointment stats'); | ||
| const zoomMeetingReports = await prisma.lecture.findMany({ | ||
| where: { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't we also exclude here those that already have the stats populated? 👀
|
@JeangelLF I see, thanks for the notice. So all that remains for closing https://github.com/corona-school/project-user/issues/1422 is the meeting duration, afaict. This I can derive from the meeting reports without any hacks. I'm gonna remove the appointment_stats data structure then and just add the |
…ve appointmentStatsId from evaluate.spec.ts
Only save select Zoom data to our database.
This required some very hacky workaround because I wasn't sure how to identify pupils/students in the meeting report other than separating them by having an ID and not having an ID. Is there a better way to do it?
Closes https://github.com/corona-school/project-user/issues/1422