Skip to content
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

feat: Exclude existing pupils from requiring a screening #961

Merged
merged 1 commit into from
Jan 22, 2024

Conversation

Jonasdoubleyou
Copy link
Member

We use matches / course participation to exlude existing active pupils from needing a screening

We use matches / course participation to exlude existing active pupils from needing a screening
@realmayus realmayus temporarily deployed to backend-feat-exclude-ex-xfml7b January 22, 2024 12:36 Inactive
Copy link
Contributor

@realmayus realmayus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Out of interest: Why don't we just create successful screenings for these pupils?

@Jonasdoubleyou
Copy link
Member Author

@realmayus that was my initial plan, but it also comes with the downside that then we have thousands of "fake screenings", i.e. it would mess up our screening statistics for example, and screeners would be confused by "previous successful screenings". Additionally there might be edge cases where this might actually be desired, i.e. Plus Pupils that are manually matched are then also allowed to access the user app without having been screened

@Jonasdoubleyou Jonasdoubleyou merged commit 69cbbc9 into master Jan 22, 2024
2 checks passed
@Jonasdoubleyou Jonasdoubleyou deleted the feat/exclude-existing-users-from-screening branch January 22, 2024 12:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants