Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kavita+ Basic Metadata Matching #2452

Open
majora2007 opened this issue Nov 22, 2023 · 2 comments
Open

Kavita+ Basic Metadata Matching #2452

majora2007 opened this issue Nov 22, 2023 · 2 comments
Labels
discussion In active discussion enhancement New feature or request Kavita+ This impacts or is completely Kavita+ related
Projects

Comments

@majora2007
Copy link
Member

majora2007 commented Nov 22, 2023

This is targeted towards people that don't use Komf.

The idea is to provide a manual button to download metadata from AniList and update Kavita via the API (this will not save the data to ComicInfo).

Note: Even if community votes yes for this, it is still subject to being removed after testing. This would likely put enormous strain on hosting and may not be sustainable.

Notes for self:

  • If we want this to ever be automatic, we can use a custom rate limit for each server IP tied against license to give X amount of metadata fetches per X hours. This allows servers to automatically scrape if applicable and prevent users from just using our api.
  • I need to investigate some advanced settings with the feature, like blocking certain keywords from being saved. Ie) Sexual Violence is not a genre in my opinion and shouldn't be written to target.
  • I may investigate a tag based system to help guide age ratings. Completely user customizable to have that written as there are no metadata sites with this present.
  • Need controls or checks that the user can set for when the match code should run. If a user uses komf, this shouldn't run. If the library is X, it shouldn't run, if the series already has X field, don't run.
@majora2007 majora2007 created this issue from a note in v0.7.5-v0.7.x (To do) Nov 22, 2023
@majora2007 majora2007 added enhancement New feature or request discussion In active discussion Kavita+ This impacts or is completely Kavita+ related labels Nov 22, 2023
@ghost
Copy link

ghost commented Jan 21, 2024

I have some thoughts about this i want to share.

  1. If i understand this right you want to proxy the Metadata request to your own Server and implement a rate limit ?
    I would suggest if you do this, use the Kavita Instance of the user and the API Key of the Admin that activated that Setting, dont send that over to your own Server.

  2. That sounds awful, cencorship bad. Thats why doing it over the Kavita Instance is better, then if a user would like to get metadata for a manga containing e.g. Sexual Violence it would only be on their server and never touch your network/server.

@majora2007 majora2007 removed this from To do in v0.7.5-v0.7.x Jan 24, 2024
@majora2007 majora2007 added this to To do in Backlog via automation Jan 24, 2024
@enchained
Copy link

  • I need to investigate some advanced settings with the feature, like blocking certain keywords from being saved. Ie) Sexual Violence is not a genre in my opinion and shouldn't be written to target.
  • I may investigate a tag based system to help guide age ratings. Completely user customizable to have that written as there are no metadata sites with this present.

It would be really nice to have tags split into categories like mangadex does - format, genre, theme, and content warnings (suggestive, erotica, gore, sexual violence). Also, since some Anilist tags contain spoilers, there should be a way to hide/reveal them, and a default setting.

(Thinking about spoilers, I had a thought about an option to blur/replace unread chapter covers, since it often starts with first frame and it might reveal some things that volume covers do not).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion In active discussion enhancement New feature or request Kavita+ This impacts or is completely Kavita+ related
Projects
Backlog
To do
Development

No branches or pull requests

2 participants