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

Separate imported participants from manual changes #2138

Open
janno42 opened this issue Mar 11, 2024 · 0 comments
Open

Separate imported participants from manual changes #2138

janno42 opened this issue Mar 11, 2024 · 0 comments
Assignees
Labels
[C] Backend Focuses on backend implementation [P] Major Major priority
Milestone

Comments

@janno42
Copy link
Member

janno42 commented Mar 11, 2024

Once we use the import from #2131 on production, we need to separate imported participation data from manual changes. The import will update data regularly and should not overwrite manual changes made by editors or managers.

It should be possible to

  • manually override that specific accounts are participants in an evaluation regardless of what data is imported
  • manually override that specific accounts are not participants in an evaluation regardless of what data is imported
  • revoke these decisions (so that the imported data will be used)

... and all this without a complicated UI with many participation fields.

A possible solution would be to add three fields participants_imported, participants_manually_added and participants_manually_removed.
participants will then be the result of participants_imported + participants_manually_added - participants_manually_removed.
The frontend would always show the computed participants list and do all the necessary additions and deletions to the respective lists when saving changes.

@janno42 janno42 added [C] Backend Focuses on backend implementation [P] Major Major priority labels Mar 11, 2024
@janno42 janno42 added this to the Winter 2024 milestone Oct 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[C] Backend Focuses on backend implementation [P] Major Major priority
Development

No branches or pull requests

2 participants