Change Details

Given the decisions in T328032#8936008: As a Developer, I want to create a job to: - Aggregate a participant's answers 90 days after they answered for the first time - Aggregate all remaining answers when the event ends - Delete the answers after they've been aggregated - The actual aggregation logic shouldn't be directly inside the script, but rather in a separate object (e.g., QuestionAggregationStore) that the script would use. The script should be documented in the [[https://www.mediawiki.org/wiki/Extension:CampaignEvents | extension's manual]].

See the decisions in T328032#8936008. ===Acceptance criteria=== - An individual participant's answer must be aggregated after 90 days from first answer - All remaining unaggregated answers must be aggregated when the event ends - All answers must be deleted after aggregation - The logic should be implemented in a dedicated service, like QuestionAggregationStore. - A maintenance script should be written that uses that service to aggregate/delete answers. - The script should be documented in the [[https://www.mediawiki.org/wiki/Extension:CampaignEvents | extension's manual]]. **TBD** Open question: how exactly should the aggregation be triggered when the event ends? Is it OK to wait until the next periodic run of the script (and maybe show a message in the interface), or should it happen on the fly (when? what about performance?)?

GivenSee the decisions in T328032#8936008:. As a Developer, I want to create a job to:===Acceptance criteria=== - Aggregate a- An individual participant's answers 90 days after they answered for the must be aggregated after 90 days from first timeanswer - A- All remaining unaggregate all remaining answersd answers must be aggregated when the event ends - Delete the- All answers after they've beenmust be deleted after aggregatedion - The logic should be implemented in a dedicated service, - The actual aggregation logic shouldn't be directly inside the script, but rather in a separate object (e.g., QuestionAggregationStore) that the script would uselike QuestionAggregationStore. - A maintenance script should be written that uses that service to aggregate/delete answers. - The script should be documented in the [[https://www.mediawiki.org/wiki/Extension:CampaignEvents | extension's manual]]. The script should be documented in the [[https://www.mediawiki.org/wiki/Extension:CampaignEvents | extension's manual]].**TBD** Open question: how exactly should the aggregation be triggered when the event ends? Is it OK to wait until the next periodic run of the script (and maybe show a message in the interface), or should it happen on the fly (when? what about performance?)?