Book with annotations doubling and showing annotations on wrong book

[Taubin]

This is a bit weird, I am currently reading Mort, and when I sync it to my server, I noticed it has made two copies of the book. One is tracking my progress, the other is showing 4% read and is holding my annotations.

The annotations are coming through on sync no problem, just to the second book which has very low reading percentage. This note I made today and came through fine

Just the the second ghost version (heh) of Mort, not the one I'm actually reading.

I wiped the database and re-synced and they both show up again. I checked my koreader and there's only one copy there. It's quite strange. Anything I can do the help troubleshoot this please just let me know.

[tku137]

This is indeed weird, but reminds me of #90. Maybe something similar happened to you?

If not, from the top of my head, there might be something wrong with matching the book IDs on KoInsight server, which is why it appears as two different books. There are currently bugs in annotations sync, which are fixed in #84, but I'd need to check if your issue could be an effect if said bugs.

Did you change the cover yourself? Wondering because the screenshot shows different covers.

[tku137]

@Taubin, if you don't mind, could you provide the following info to us?

In the KOReader statistics.sqlite3, what is the output of (assuming the title is something with "Mort" in it?):

SELECT id, title, md5 FROM book WHERE title LIKE '%Mort%';

And in the actual sidecar file, which is a directory with the epub filename + .sdr (maybe Mort.sdr?), inside is a lua file called metadata.epub.lua (or similar), which has

["partial_md5_checksum"] = "...",

I suspect these are different.

[tku137]

Also, just to make sure that duplicates are actually existing in koreaders statistics db already:

-- find titles with duplicates
SELECT title, COUNT(*) AS c
FROM book
GROUP BY title
HAVING c > 1;

-- inspect duplicate rows for a problematic title
SELECT id, title, md5, last_open
FROM book
WHERE title = 'Mort'
ORDER BY last_open DESC;

[tku137]

#84 should solve it. The old book matching logic was flawed and made duplicates possible.

[Taubin]

Sorry I wasn't able to get back to this until this morning.

You are correct the md5's are different

INSERT INTO "main"."book" ("md5") VALUES ('cc9d56e7e4c92e53b99b1ea022fa42f7');
INSERT INTO "main"."book" ("md5") VALUES ('0297fa3d24e0d0002856dec9d552b604');
INSERT INTO "main"."book" ("md5") VALUES ('bb7eae652ab0c507f169f5eddbbc2979');
INSERT INTO "main"."book" ("md5") VALUES ('92914a3dd2f8d6553e5cd0d10c662170');

Sorry I was so delayed in responding, and thank you so much for looking into this. I'll go ahead and close this since it is fixed in the pull. If you need anything from me or a copy of my db, please let me know.