Thread: How to write a Metadata plugin
View Single Post
Old 11-24-2018, 10:33 PM   #3
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,906
Karma: 47303748
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
That's the simplest thing to do. There are plenty of examples you can look at. I don't know which is the best to look at as they all do things a little differently. You should also look in the calibre source at src/calibre/ebooks/metadata/sources/base.py. You can see the API and what needs to be overridden.

And having a quick look at the two sites mentioned, onebookshelf.com seems to be parent site for a group of others. And they look like they probably use the same source code for all the sites. And it is likely they have an API. If so, the results from that are usually easier to handle than parsing a web page.
davidfor is offline   Reply With Quote