Quote:
Originally Posted by Mister L
Are they automatically exported? How do you do that? I thought I had somehow managed to configure something for that because I have 2 annotations .txt files in the kobo memory that I do not remember manually exporting, but only 2, when I have annotated many many more books than 2. I vaguely remember activating an option in the conf file (I think?) to allow exporting annotations but as far as I can tell it must be done manually from inside the book and if you open a book to export the annotations the datestamp is reset which ruins my sort order so it's not ideal. Plus I have to remember to do it.
|
None of the annotation export options are automatic. You have to run them either on the device or when the device is connected to a PC. The export annotations on the device can be run from any of the book lists. Long-press on the book and it should be on the menu.
Quote:
I think / hope I have noted current % read for open books, using the plugin. I also have saved "date" but I think that only concerns the date the book was opened, not the date it was sent to the device, unfortunately. I open books sometimes to move them to the top of the list, and I also deliberately don't finish a book to the last page sometimes if there is something in it I want to remember to check. Plus the books I am actually currently reading. So I don't want to lose that information if I can avoid it.
|
If you have all the columns configured in the book status fetch, then you can restore the status and the reading position. Which includes the last read date. That is the case for both read and unread books. But, if you are opening the book and then marking it as unread to get it to the top of the "Recent" sort, then that is not stored.
Quote:
It might be user error. I am attempting to learn how to manage databases as I go along here so I am just blindly trying things and hoping they work. But certainly some / a lot of things are not working as I would expect. Almost nothing is working in fact. :/
That makes sense. I tried running the statement you gave me but the result said "no data to display" (see screencap attached). I don't know why. There very clearly should be data to display.
I accidentally ran it once halfway through (only the first 2 lines) and that did give one result, so I deleted that book and all associated files with the same filename (some images, and annotations file...), but this did not fix the problem.
|
After I posted the SQL statement, it occurred to me that it might not give the desired result because the index was corrupt. The query is probably optimised to use the index, which would give the wrong result.
Quote:
I set the plugin to save everything there was an option for (4 columns) so if reading status is one of those it is saved. I know Collections are saved. Is it possible to restore the datestamp as well, for sorting by "Recent"? I have the Annotations plugin, it saves the annotations to a custom column, but I would prefer to have them on the device as well ideally. How complicated is it to manually copy a table?
|
There are no tools that I know of that export the annotations in a way that can be imported again. You can be done by exporting the table and importing it into a new database.
For the "Recent" sort, if I populate the device again, I use the "Update metadata in the device library" to set the "Date Added" to one of the dates in the calibre library. If you are opening and then marking books as unread, it won't help.
Quote:
Today the problem is worse:
Database check
I don't know why, and although I copied the database from yesterday with only the one error back to the device the new errors reappear each time after I eject / reconnect.
At this point I am not sure it is possible for me given my lack of database skills to correct this problem. I have not managed to do any of the things suggested, the problem is getting worse, and I am getting pretty frustrated. I think it's probably best if I try to salvage as much as I can and just start fresh with a new database, much as it annoys me.
This is my first experience with a device that uses a database, my previous devices (Sony and Cybook) did not work that way as far as I know, and although I have been mostly happy with the Kobo so far this is really putting a damper on my enthusiasm, I never had any problem even remotely like this with the others.
|
At this point, I'm not sure if it can be fixed. If I had a copy of the database, I could try. It would involve dropping the indexes, finding the duplicates as above followed by some cleanup and then recreating the indexes. That should work, but, there is a lot to do.