Reporting system for SRRs

Issue #108 new
Former user created an issue

Mentioned this on IRC yesterday, but it might've gotten buried in netsplit spam: 04:11 < malvida> srrdb should have some kind of reporting system where registered users can report an srr for having trash files etc, too easy to miss stuff if just mentioned in irc IMO Current options for reporting this are lacking: 1) Too easy to miss/be forgotten on IRC 2) PM'ing someone on site lacks transparency

Suggested system: Report an SRR for having some kind of issue, mods can check and take appropriate action. Reports and actions should be stored in some kind of log that's open for anyone to view and possibly dispute, with a per-release log for each release. Open reports should be displayed on the details page. This could be extended to suggestion adds as well. Having this log would help in preventing repeated invalid reports as well. Depending on the desired complexity of the log system, it could be based on just simple messages (one end of the spectrum), or being able to select a list of affected files and a reason for the report (other end of the spectrum).

Practical examples Release A contains a trash NFO file. A registered user reports said SRR, indicating that the NFO file is trash and belongs to a different release. A moderator inspects the report and takes appropriate action and decides on the appropriate action. This is all displayed in the log.

Release B contains a seemingly unrelated file. A registered user reports said SRR. A moderator inspects the report, decides instead that the file is indeed part of the pre, and closes the report as invalid. Later, another user wants to report the SRR for the exact same reason, but sees the previous report in the log, together with the reason it was invalid.

A user mistakenly adds an incorrect file to an SRR as a suggestion add. Another user sees this suggestion adds, determines that it is invalid, and reports it. The suggestion add is denied after moderator review, and any subsequent attempted addition of this file is automatically denied.

Comments (0)

  1. Log in to comment