-
Notifications
You must be signed in to change notification settings - Fork 502
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
[Enhancement]: implement metadata provider for litres.ru #3834
Comments
Do you know if they do strict throttling of requests? We can try it out if you can do some testing on it to make sure it isn't going to result in a bunch of user bug reports |
I do not. But if you are not against another provider in general, I will write something up in the coming weeks and test it. Are there some specific minimal requirements like number of lookups per hour/minute/second, that must be satisfied? I must admid that I have not considered such a limitation at all. I usually add books as I buy them, one at a time. But ABS users might match their whole library which would fire a lot of API calls. |
There is no standard set for number of requests. Right now we are only throttling requests made when matching authors using the p-throttle library. Afaik we only had rate limit issues for users matching authors that had a lot of authors. |
I had a further look at the API and figured out how to get all the attributes without any parsing.
|
Type of Enhancement
Server Backend
Describe the Feature/Enhancement
I would like to implement a metadata provider that draws info from litres.ru. It's an online retailer with primarily Russian catalogue of books/audiobooks but also podcasts.
I had a look at the API and it seems promising, e.g. I could search for a book/audiobook with a call like:
An excerpt from the answer looks like:
It seems to me like most relevant fields are present:
title
,subtitle
,cover
, from thepersons
field one can retrieveauthor
(s),narrator
,publisher
andtranslator
(which at the moment is not used in ABS). What I am missing is the tags/genres, a description and a release date/year. It is not returned with the search results, but surely could be aquired since the book's page shows the information, though that might require extracting it from HTML.I use this site to aquire russian books. I am thinking about implementing a metadata provider for the site, so I don't have to copy paste it all the time. Their catalogue is quite large, and apart from exclusives of competing services they have most of the books I look up.
I am not sure about the podcast part, since I am not using that part of ABS at all - but it could work for that as well.
If I were to write a provider, would it be merged?
Why would this be helpful?
An additional provider for metadata for primarily russian books.
Future Implementation (Screenshot)
An additional entry in the provider drop-down field in the match book window and cover lookup window.
Audiobookshelf Server Version
v2.17.7
Current Implementation (Screenshot)
The text was updated successfully, but these errors were encountered: