Right now, a next campaign is selected based on the amount of judgements a user has for this campaign for each game in the campaign.
The game in the campaign that has the least amount of judgements is then chosen as the next game.
This system is good in theory, but it requires each judgement in the judgements table to have a campaign_id and a game_id to be added to it, and if a user finishes a game that is in 2 campaigns, we want both campaigns to be updated.
This means that two judgements need to be made: one for campaign A and one for campaign B.
Two judgements are made, but only one judgement is really done: the user only makes one judgement for one image by clicking the submit button once.
This is ugly and should be done in a better way.
Maybe make a seperate table with user_id, judgement_id, game_id and campaign_id, and then having the same judgement_id appear twice in this table if it was for two different campaigns.
Right now, a next campaign is selected based on the amount of judgements a user has for this campaign for each game in the campaign.
The game in the campaign that has the least amount of judgements is then chosen as the next game.
This system is good in theory, but it requires each judgement in the judgements table to have a campaign_id and a game_id to be added to it, and if a user finishes a game that is in 2 campaigns, we want both campaigns to be updated.
This means that two judgements need to be made: one for campaign A and one for campaign B.
Two judgements are made, but only one judgement is really done: the user only makes one judgement for one image by clicking the submit button once.
This is ugly and should be done in a better way.
Maybe make a seperate table with user_id, judgement_id, game_id and campaign_id, and then having the same judgement_id appear twice in this table if it was for two different campaigns.