Problem
When it comes to processing user responses on deferred tickets, my current process is to accumulate ticket response emails and then try to work through as many as possible. I often dread starting to work on them as I have no way of sorting/grouping them by user (the most important factor for reducing stress caused by repeated context switching).
This leads to long waiting time for users even if they did great corrections or added perfect clarifications.
Some users might delete their uploads during moderation. I'm speculating this might be out of frustration with response time. For example:
https://freesound.org/tickets/7e70b76e5ec34056aa56e63ce5bb19fd/
https://freesound.org/tickets/db9d3165b92c49e4b630857e5cf65f5c/
A clear overview over users with tickets to which they actively respond to should be of help.
Solution
A new sortable view of all assigned deferred tickets. It could sort all tickets by the date of
- the last message by the uploader
- the last message by a moderator
However more importantly, it needs to allow group-sorting by uploader. First, group all (deferred) tickets by uploader (assigned to current moderator), then sort the groups by either:
- which uploader most recently replied to a ticket while the ticket is in deferred state (when-deferred) or
- which uploader most recently replied to a ticket that currently is in deferred state (current-deferred)
The distinction: if an uploader replies in one of 100 tickets and that reply resolves any concern of the other 99, then, if the moderator approves that ticket with the reply, then gets distracted, then returns back to moderation the next day, the current-deferred method will lead to the user group not having a recent reply, thus not being at the front.
On the other hand, if one reply on one ticket fails to resolve the other tickets, current-deferred might be better.
And of course a mix of both is possible. If possible, both methods of sorting groups might be good to have.
Within the groups, apply the sorting as listed above.
It might be necessary to keep track of a user variable, which is the most recent date the user wrote a message on a ticket that at that moment was deferred.
Example
(Time is in 'minutes ago' for simplicity)
| sound link |
ticket link |
user |
last uploader reply |
last moderator reply |
when-deferred |
current-deferred |
| Man Saying Hello |
11114358 |
VocalStudiosos |
3 |
3 |
3 |
3 |
| Woman Laughing |
43958934 |
VocalStudiosos |
10 |
10 |
3 |
3 |
| Bird Flapping |
94358340 |
StoneStone123 |
6 |
6 |
6 |
6 |
If I approve Man Saying Hello, when-deferred/current-deferred lead to different sorting of the rest.
when-deferred:
| sound link |
ticket link |
user |
last uploader reply |
last moderator reply |
when-deferred |
current-deferred |
| Woman Laughing |
43958934 |
VocalStudiosos |
10 |
10 |
3 |
10 |
| Bird Flapping |
94358340 |
StoneStone123 |
6 |
6 |
6 |
6 |
current-deferred:
| sound link |
ticket link |
user |
last uploader reply |
last moderator reply |
when-deferred |
current-deferred |
| Bird Flapping |
94358340 |
StoneStone123 |
6 |
6 |
6 |
6 |
| Woman Laughing |
43958934 |
VocalStudiosos |
10 |
10 |
3 |
10 |
Notes
- I'm not sure whether "[uploader] updated one or more fields of the sound description" should be considered a reply by the user or not
- For the future, it might be useful to be able to prioritize (sort by) users that respond quickly relative to the previous mod message.
Related tickets
Problem
When it comes to processing user responses on deferred tickets, my current process is to accumulate ticket response emails and then try to work through as many as possible. I often dread starting to work on them as I have no way of sorting/grouping them by user (the most important factor for reducing stress caused by repeated context switching).
This leads to long waiting time for users even if they did great corrections or added perfect clarifications.
Some users might delete their uploads during moderation. I'm speculating this might be out of frustration with response time. For example:
https://freesound.org/tickets/7e70b76e5ec34056aa56e63ce5bb19fd/
https://freesound.org/tickets/db9d3165b92c49e4b630857e5cf65f5c/
A clear overview over users with tickets to which they actively respond to should be of help.
Solution
A new sortable view of all assigned deferred tickets. It could sort all tickets by the date of
However more importantly, it needs to allow group-sorting by uploader. First, group all (deferred) tickets by uploader (assigned to current moderator), then sort the groups by either:
The distinction: if an uploader replies in one of 100 tickets and that reply resolves any concern of the other 99, then, if the moderator approves that ticket with the reply, then gets distracted, then returns back to moderation the next day, the current-deferred method will lead to the user group not having a recent reply, thus not being at the front.
On the other hand, if one reply on one ticket fails to resolve the other tickets, current-deferred might be better.
And of course a mix of both is possible. If possible, both methods of sorting groups might be good to have.
Within the groups, apply the sorting as listed above.
It might be necessary to keep track of a user variable, which is the most recent date the user wrote a message on a ticket that at that moment was deferred.
Example
(Time is in 'minutes ago' for simplicity)
If I approve Man Saying Hello, when-deferred/current-deferred lead to different sorting of the rest.
when-deferred:
current-deferred:
Notes
Related tickets