Entry reports
Entry reports are a way of communicating edit-related mistakes. Two main reasons for reports are:
- Making a note that there’s an issue that should be fixed.
- Giving the previous editor a chance to correct their mistake and hopefully learn from it .
To allow the editor to learn from their mistake, Trusted Users should typically wait at least 24 hours before closing entry reports, besides those that the original editor cannot fix themselves or are on older edits.
The list of open entry reports is visible to all trusted users and above.
- Trusted users should ignore moderation-related reports such as artist verification and content removal requests.
Reporting an entry also sends a notification to the editor, but if the entry has been edited by more than one person, notifications are not sent.
To send a notification in this case, you can report a specific version. You can do this by using the “View Modifications” menu, going to the version where the error was first present, and clicking “Report an Error”. This should be preferred for entries by multiple editors, since it always sends a message to the relevant editor.
Entry reports should NOT be made for the following reasons:
- Requesting for a tag to be added (unless on an approved article)
- Requesting for lyrics to be added (use the “lyric transcript needed” tag instead)
- Asking questions, such as “Why was x changed?“. (The comments should be used for this purpose)
- Any other reasons not involving an error being present in the article.
Report an error
This is the main method of submitting entry reports. It appears on all page types.
Albums and artists have four report types, while songs have the additional “Broken PV” type.
Broken PV
Used for reporting deleted or privated PVs.
This report type communicates that a PV needs to be marked as Unavailable or deleted if the link type is “Reprint” or “Other”. If possible, prefer doing it yourself instead of creating an entry report.
Keep in mind that if the PV is region blocked, it should not be marked as unavailable.
Invalid or missing information
Used for reporting:
-
Invalid or incorrect information
- Always provide reasoning and proof unless already obvious.
Examples:
- Incorrect tag(s) applied to the entry
- Incorrect artists credited
- Romanizations/translations that do not follow the Romanization Guidelines
-
Missing information
Examples:
- A missing alias or circle.
- A missing artist credit.
If possible, it’s preferable to add missing information yourself instead of leaving a report, as it’s usually not necessarily an error.
Duplicate entry
Entry is a duplicate and should be merged. A link to the duplicate entry is required, along with proof.
Inappropriate content
For entries that do not belong in VocaDB.
Other (specify in notes)
- For errors not already covered within the existing report types.
This list shows suggestions that should be followed to prevent unclear situations and unnecessary work.
DON’T spam entry reports of the same type
If the same report applies to multiple entries, list those entries under one report, in a comment under one of the relevant entries, or message a moderator.
DO prefer reporting a specific version
Unless there’s only one editor for that entry, the editor won’t get a notification, and if they’re not a trusted user, they can’t see your report outside of the inital notification. For entries with multiple editors, it’s better to report a specific edit. This makes it more obvious what the problem is, and also the previous editor will get a direct notification.
DON’T report edits that are very old if you can take care of the issue yourself
If the mistake was made months, even years ago, there’s not much point in reporting it, assuming you can take care of it yourself. In many cases the previous editor isn’t even around anymore.
DO prefer taking care of your own reports if no one else responds
The expectation is that the previous editor who made the mistake would be the one to correct it, but assuming they don’t, the best thing you as the reporter can do is to correct the mistake yourself when you get the chance. Some people don’t check the site very often, or maybe they didn’t even get the notification.
DON’T let reports lie there for weeks (Trusted Users/Moderators)
When a report is over a week old, it should be taken care of somehow. If you can, please fix the problem.
DO provide explanations in your reports
Especially for newer editors, it might not be obvious what to fix when their entry is reported for something like “title needs to be cleaned”, “incorrect X”, etc. It is useful to be specific as to what is wrong in the entry and provide relevant wiki pages/quotes.