Maybe this should also be a post in the Suggestions/Improvements forum. eg.
Note: The below implies that for any item uploaded for review, at least a unique record is kept in the database for that item - whether the actual content (datafile) is kept for that item is irrelevant.
Summary: When a mod rejects a picture, they select a reason (not sure if that currently occurs as I am not a mod) and that reason is subsequently made available to view by the uploading user.
Enhancement:
1.0 Picture/Video Approval
When a mod reviews pictures and selects Reject, they also select from a dynamic rejection category list, the mod also selects the Reason for rejection from a list.
1.1 This Rejection Category list should be dynamic so that additions, modifications can be made as necessary.
1.2 Keep the Rejection Category list relatively simple and high-level. The mods have no onus to deal with an excessive list of categories to provide detailed descriptions to users. Too many makes it less beneficial and less efficient.
1.3 Nice to Have: Have an Other category that spawns a free text field in case the category is not adequately defined. This Other category can periodically be reviewed by Mods/Admin to determine if new Categories should be added, or existing Categories should be merged or used instead of Other:<FreeTextReason>.
1.4 Content Management: Based on the Rejection Category, the thumbnail of the data file may be maintained for a period of time to aid review by User/Mod. If the Category is for Inappropriate content the Thumbnail should be removed immediately from the host.
1.4.1 Thumbnails of rejected content should be removed from the host by a housekeeping process after a defined period for User Review of their uploads.
2.0 User Upload Visibility (it's been ages since I've uploaded anything for review so don't remember the screens/process so amend as necessary)
Under the User Upload section for a User Profile, a new section Rejected Uploads is created underwhich a user may view a reference for the file and the rejection reason given.
2.1 This Rejected Uploads section is accessible only to the owning User and to any Admin/Mod access as defined by site access level governance.
2.2 This Rejected Uploads section shall contain reference to the file (Unique WBW ID, perhaps local upload file path or original file name if that is stored, date of upload, date of review, rejection reason). I expect, for issues of space, that the original file content is deleted upon rejection.
2.2.1 It may be possible to keep the thumbnail, for a defined period of time, to provide the user with an immediate visual reference. However, for issues of decency if the content is inappropriate and was rejected for that reason then the thumbnail should also be removed originally.
2.2.2 When viewing by Mod/Admin, the rejecting mod should be visible. When viewing by User, this might cause too much overhead for the mods with Users questioning rejections all the time.
Add to it as necessary
Note: The below implies that for any item uploaded for review, at least a unique record is kept in the database for that item - whether the actual content (datafile) is kept for that item is irrelevant.
Summary: When a mod rejects a picture, they select a reason (not sure if that currently occurs as I am not a mod) and that reason is subsequently made available to view by the uploading user.
Enhancement:
1.0 Picture/Video Approval
When a mod reviews pictures and selects Reject, they also select from a dynamic rejection category list, the mod also selects the Reason for rejection from a list.
1.1 This Rejection Category list should be dynamic so that additions, modifications can be made as necessary.
1.2 Keep the Rejection Category list relatively simple and high-level. The mods have no onus to deal with an excessive list of categories to provide detailed descriptions to users. Too many makes it less beneficial and less efficient.
1.3 Nice to Have: Have an Other category that spawns a free text field in case the category is not adequately defined. This Other category can periodically be reviewed by Mods/Admin to determine if new Categories should be added, or existing Categories should be merged or used instead of Other:<FreeTextReason>.
1.4 Content Management: Based on the Rejection Category, the thumbnail of the data file may be maintained for a period of time to aid review by User/Mod. If the Category is for Inappropriate content the Thumbnail should be removed immediately from the host.
1.4.1 Thumbnails of rejected content should be removed from the host by a housekeeping process after a defined period for User Review of their uploads.
2.0 User Upload Visibility (it's been ages since I've uploaded anything for review so don't remember the screens/process so amend as necessary)
Under the User Upload section for a User Profile, a new section Rejected Uploads is created underwhich a user may view a reference for the file and the rejection reason given.
2.1 This Rejected Uploads section is accessible only to the owning User and to any Admin/Mod access as defined by site access level governance.
2.2 This Rejected Uploads section shall contain reference to the file (Unique WBW ID, perhaps local upload file path or original file name if that is stored, date of upload, date of review, rejection reason). I expect, for issues of space, that the original file content is deleted upon rejection.
2.2.1 It may be possible to keep the thumbnail, for a defined period of time, to provide the user with an immediate visual reference. However, for issues of decency if the content is inappropriate and was rejected for that reason then the thumbnail should also be removed originally.
2.2.2 When viewing by Mod/Admin, the rejecting mod should be visible. When viewing by User, this might cause too much overhead for the mods with Users questioning rejections all the time.
Add to it as necessary
mikeyeven finds this awesome.
