A new deepdive command would allow us to generate many transcription checks for a given user in bulk.
This would be useful to systematically approve the first 100/24 of a user or check transcriptions in detail if major issues were uncovered in another transcription.
The Slack command could look like this: @Blossom deepdive <username> <post_number> <percentage>
<username> Is the name of the user to generate the checks for.
<post_number> Is the number of recent posts to consider for the checks. E.g. 100 would consider the last 100 transcriptions the user made (for a 100/24).
<percentage> Is used to calculate the number of checks that should be generated. E.g. 80% would mean that out of the 100 posts to consider, 80% should be checked. So 80 transcription checks will be generated in total.
It might be useful to also determine the time frame to generate the checks for, but this might make the command overly complicated.
It needs to be considered that this command will generate a HUGE amount of messages. Therefore we have to think about making multiple adjustments:
Adding a piece of text to the check message to indicate that they have been generated by this command
Posting the checks in a different channel to avoid cluttering the main channel
Adding a confirmation dialog to avoid accidentally generating an enormous number of checks
Limiting the number of checks to a maximum (e.g. 100) to prevent accidents and overloading the mods with too much work
This would be implemented after #291.
A new
deepdive
command would allow us to generate many transcription checks for a given user in bulk. This would be useful to systematically approve the first 100/24 of a user or check transcriptions in detail if major issues were uncovered in another transcription.The Slack command could look like this:
@Blossom deepdive <username> <post_number> <percentage>
<username>
Is the name of the user to generate the checks for.<post_number>
Is the number of recent posts to consider for the checks. E.g.100
would consider the last 100 transcriptions the user made (for a 100/24).<percentage>
Is used to calculate the number of checks that should be generated. E.g.80%
would mean that out of the 100 posts to consider, 80% should be checked. So 80 transcription checks will be generated in total.It might be useful to also determine the time frame to generate the checks for, but this might make the command overly complicated.
It needs to be considered that this command will generate a HUGE amount of messages. Therefore we have to think about making multiple adjustments: