View Single Post
Old 01-18-2021, 06:23 AM   #2102
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,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by ownedbycats View Post
My filename template is {#kobopath}/{author_sort}/{title} - {authors}.

#kobopath is a fixed-value column with a few options (Fiction, Nonfiction, and Fanfiction essentially) just as a kludge to avoid cluttering up the root of the drive with a million author folders. It never changes once it's set.

I forgot to mention that the duplicate book appears in Calibre device view. Usually I notice it when SmartEject tells me there's duplicate books. I've never actually checked to see if it appears on the device itself because I just delete the old version.

I also have KoboTouchExtended set to treat it as a new book. I was thinking that if the book uploaded first, and then Kobo Utilities grabs the bookmark from the old version, Calibre sees it as two separate database entries. (It would also explain why it only happens sometimes - it depends on whether the bookmark or reading list sync happens first.) But that's kind of grasping at things.
That's weird. Does the library show there are two copies on the device? That's how I usually realise I have the extended driver active.

Getting the reading status should be OK. It gets the status for all copies of the book that are in the database. And it should be using the most recent one (latest reading timestamp). If a new copy is sent as a different file name, it will not be in the database, so it won't be found. If it is breaking something, I need a debug log to look at.
davidfor is offline