[Enhancement]: Allow users to report/flag books for review #2515

New issue

Open

opened 2026-02-20 02:18:39 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-20 02:18:39 -05:00

Owner

Originally created by @WeAreBorgPony on GitHub (Oct 30, 2024).

Type of Enhancement

Web Interface/Frontend

Describe the Feature/Enhancement

In the 3 dots menu, add option to flag a book for review by an admin. User could select from a canned reason for doing so as explained below. For the admin, these could show up in the issues menu. A setting could automatically hide reported books from normal users until reviewed.

Why would this be helpful?

In large libraries mistakes can be made. Users could report a book for having the wrong Metadata, such as being the wrong book entirely, wrong version, or being a compilation when its labeled as a full book, as well as audio issue, or not marked as explicit when it should be. It would allow admins to fix books without users needing to remember what book had the issue and then remember to tell an admin.

Future Implementation (Screenshot)

Audiobookshelf Server Version

v2.15.1

Current Implementation (Screenshot)

No response

Originally created by @WeAreBorgPony on GitHub (Oct 30, 2024). ### Type of Enhancement Web Interface/Frontend ### Describe the Feature/Enhancement In the 3 dots menu, add option to flag a book for review by an admin. User could select from a canned reason for doing so as explained below. For the admin, these could show up in the issues menu. A setting could automatically hide reported books from normal users until reviewed. ### Why would this be helpful? In large libraries mistakes can be made. Users could report a book for having the wrong Metadata, such as being the wrong book entirely, wrong version, or being a compilation when its labeled as a full book, as well as audio issue, or not marked as explicit when it should be. It would allow admins to fix books without users needing to remember what book had the issue and then remember to tell an admin. ### Future Implementation (Screenshot) ![Screenshot_20241030_211327_Edge](https://github.com/user-attachments/assets/81636613-d2ad-4cc3-86ee-71ae34c10b8b) ![Screenshot_20241030_211937_Edge](https://github.com/user-attachments/assets/873b5535-29aa-48fd-bb20-4dde086b0ef1) ### Audiobookshelf Server Version v2.15.1 ### Current Implementation (Screenshot) _No response_

deekerman added the

enhancement

possible plugin

labels

2026-02-20 02:18:39 -05:00

deekerman commented

2026-02-20 02:18:40 -05:00

Author

Owner

@ZLoth commented on GitHub (Nov 1, 2024):

How would the interface look like from the administrative level?

@ZLoth commented on GitHub (Nov 1, 2024): How would the interface look like from the administrative level?

deekerman commented

2026-02-20 02:18:40 -05:00

Author

Owner

@sydlexius commented on GitHub (Nov 2, 2024):

Though it might get binned under metadata, a specific call-out for chapter issues might be in order as well.

@sydlexius commented on GitHub (Nov 2, 2024): Though it might get binned under metadata, a specific call-out for chapter issues might be in order as well.

deekerman commented

2026-02-20 02:18:40 -05:00

Author

Owner

@WeAreBorgPony commented on GitHub (Nov 3, 2024):

How would the interface look like from the administrative level?

@WeAreBorgPony commented on GitHub (Nov 3, 2024): > How would the interface look like from the administrative level? ![zasdtgwe54tgqe](https://github.com/user-attachments/assets/a458309b-0303-4f3d-b60a-763ba77eccec) ![h0789h9puihnj-0](https://github.com/user-attachments/assets/bc2c33a3-7a2e-49ec-9dd2-caf031522a56)