Database Guidelines 15. Remove Release

15.1.1 This function is found on the release history page, on the right hand side of the gray section:


After clicking the 'Remove Release' link, you will see:


This function allows voters and owners of the release to vote on its removal. A release needs over 81% 'Yes' votes to be removed. All users with the release in their collection are able to vote on the removal. Removed releases go back to the original submitters draft folder.

15.1.2. Releases should only be removed from the database if they are invalid. For example; they don't exist or they don't contain enough information to identify them as a valid unique release. For all duplicate releases, please use the Merge Release function. Please see the General Guidelines for more information. Releases that have been entered in an extremely inappropriate manner (for example, releases with adult themes, artwork etc listed in the Children's genre) can be removed from the database.

15.1.3. Releases should not be removed because they were entered without the submitter having the release (websubmission). If the release exists and the data is enough to represent the release, it must stay in the database. However, you can report the user who did the websubmission to the Database Manager - users doing websubmissions may be warned, restricted, blocked, or banned from the database by the Database Manager.

Related Topics: