starred/audiobookshelf
1
0
Fork 0
mirror of https://github.com/advplyr/audiobookshelf.git synced 2026-05-30 23:40:40 +02:00
Code Issues 1.0k Packages Projects Releases 10 Wiki Activity

[Enhancement]: Add metadata type called "flag" #976

New Issue
Open
opened 2026-04-24 23:28:06 +02:00 by adam · 1 comment
adam commented 2026-04-24 23:28:06 +02:00
Owner
Copy Link
Copy Source

Originally created by @hobesman on GitHub (Feb 24, 2023).

Describe the feature/enhancement

This is intended to function essentially identical to tags, except that it would be something no outside source would modify.
The idea is that "tags" were created for the admin to be able to put a label on something, but that "tag" metadata item has been hijacked for better or for worse by audible tags. Those are good and I don't want to get rid of them, but I also want something I can add that won't be overwritten and won't be mixed up with data from other metadata sources.

So if I want to flag something as kid friendly, or not kid friendly, or sexually explicit, or gory, or whatever, I can do that without worrying that matching to audible will overwrite or bury those flags. If I'm granting or denying users access to things based on these, I don't want audible metadata getting mixed up in that.

Long story short, everything I can already do with tags, but separated from audible's tags.

While we're at it, these should also be written to the .abs file, and should also have the option to limit a user to (or deny a user access to) specific flags.

Originally created by @hobesman on GitHub (Feb 24, 2023). ### Describe the feature/enhancement This is intended to function essentially identical to tags, except that it would be something no outside source would modify. The idea is that "tags" were created for the admin to be able to put a label on something, but that "tag" metadata item has been hijacked for better or for worse by audible tags. Those are good and I don't want to get rid of them, but I also want something I can add that won't be overwritten and won't be mixed up with data from other metadata sources. So if I want to flag something as kid friendly, or _not_ kid friendly, or sexually explicit, or gory, or whatever, I can do that without worrying that matching to audible will overwrite or bury those flags. If I'm granting or denying users access to things based on these, I don't want audible metadata getting mixed up in that. Long story short, everything I can already do with tags, but separated from audible's tags. While we're at it, these should also be written to the .abs file, and should also have the option to limit a user to (or deny a user access to) specific flags.
adam added the enhancement label 2026-04-24 23:28:06 +02:00
adam commented 2026-04-24 23:28:07 +02:00
Author
Owner
Copy Link
Copy Source

@vincentscode commented on GitHub (Mar 16, 2023):

Do you think this should replace the explicit option?
If implemented this could also be used to implement https://github.com/advplyr/audiobookshelf/issues/1408.

Should this be entirely user-controlled or should there be pre-made flags?

@vincentscode commented on GitHub (Mar 16, 2023): Do you think this should replace the explicit option? If implemented this could also be used to implement https://github.com/advplyr/audiobookshelf/issues/1408. Should this be entirely user-controlled or should there be pre-made flags?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
authentication
backlog
bug
chapter editor
config-issue
ebooks
encoding/embedding
enhancement
help wanted
listening sessions & progress
planned
possible plugin
progress sync
pull-request
Mirrored from GitHub Pull Request
 sorting/filtering/searching
unable to reproduce
upload
users & permissions
waiting
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam (Adam Melkus)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf#976
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?