View Single Post
Old 02-18-2021, 10:39 PM   #10
Bradles
Zealot
Bradles turned on, tuned in, and dropped out.Bradles turned on, tuned in, and dropped out.Bradles turned on, tuned in, and dropped out.Bradles turned on, tuned in, and dropped out.Bradles turned on, tuned in, and dropped out.Bradles turned on, tuned in, and dropped out.Bradles turned on, tuned in, and dropped out.Bradles turned on, tuned in, and dropped out.Bradles turned on, tuned in, and dropped out.Bradles turned on, tuned in, and dropped out.Bradles turned on, tuned in, and dropped out.
 
Bradles's Avatar
 
Posts: 112
Karma: 35586
Join Date: Nov 2020
Location: Perth, Western Australia
Device: Apple Books & Kobo Libra H20
Hi David,

Thanks for your question. The two possible answers are:

1. I was more interested in the simple existence of the book in each source, not so much in syncing the metadata. More a personal preference in how I use LT and calibre.

2. Complexity. This is my first "real" plugin, my first attempt at python programming, and my first experience with web-related development. I wanted to keep it simple.

I have looked at a couple of your metadata source plugins, and I can foresee it wouldn't be TOO difficult to adapt one for LT. I do like the idea of clicking on the identifier to go to the book in LT. I will give this some thought if the current plugin gets any traction.

To touch on your other comments, I do use a "LibraryThing ID" column in calibre to keep track of the matched books. The LT API is one-way, so no facility to update books there.
Bradles is offline