Export does not handle multiple read / finish / drop events in books

[jrhbcn]

Hello,

Really thank you for this tool, I have been waiting for something to keep track of my read books. I started using a single text file, then an excel sheet and finally goodreads. However, I would like to keep my data personal and also to be able to export it completely to move on if needed (not like goodreads as I painfully realice now).

Anyways, I am testing the export functionality before I commit myself fully to Jelu and realised that events are not really exported. Multiple "reading" events are ignored (only the last one is exported). Also "drop" events are ignored. Multiple "finished" seem to be supported and exported as alist though.

Is it possible to export the full list of events? Best regards,

[bayang]

Hi, and thanks for your interest !

If I remember correctly Jelu only exports the last reading date in a goodreads like CSV file.

I'll try to find a suitable format to export all the events, maybe a compressed JSON file if it is not too big and let users choose between the actual CSV export and a full export.

Do remember, however, that all your data is forever yours as long as you keep your jelu SQLite database.
I recommend to regularly backup the SQLite file and your pictures folder.

[jrhbcn]

Hi @bayang

If I remember correctly Jelu only exports the last reading date in a goodreads like CSV file.

Yes, and that is the main reason I want to go away from goodreads and I have to go manually adding all my starting dates to all of my books :(

I'll try to find a suitable format to export all the events, maybe a compressed JSON file if it is not too big and let users choose between the actual CSV export and a full export.

JSON would be fine. However, i was thinking in a simpler thing. Just modifying the CSV export so the "reading date" column behaves as the "finished date" one, where all reading events are listed on a string separated by colons (maybe separate them with something different that the main csv separator. The same for the "drop" events.

Do remember, however, that all your data is forever yours as long as you keep your jelu SQLite database. I recommend to regularly backup the SQLite file and your pictures folder.

Yes! I am actually fully committed to Jelu because of this. :) I am exploring the API to be able to export everything with a python script. Now to manually import all my goodreads books...

[zblesk]

Seconded re the export thing! No reason to have it be broken in the same way as GR breaks it.

I'd appreciate a JSON export as well.

[bayang]

In the Jelu export I tried to be compatible with goodreads format because it is the most common format and I want people to be able to switch to another app if they get bothered with Jelu.

So in the Jelu export, columns from "Title" to "Bookshelves" are used for Goodreads reimport or usage in another app.
see https://help.goodreads.com/s/article/How-to-import-my-books-from-other-cataloging-services-1553870934585

The read_dates is a column I added arbitrarily to track several reading finished event.
I could add a dropped_dates column if you want.

About the currently reading state, in jelu you will only ever have only one currently reading event at the same time for a book.
Because when you set a book as finished or drop, it is actually the latest currently_reading event that is modified.

So if needed I can add a currently_reading column date if the book is in this state.
Do remember however, that those columns will probably not be used by other apps when you need to import your data elsewhere @jrhbcn and @zblesk .

[zblesk]

Thank you for the explanation. The absolute 1:1 compatibility is not a factor for me, but I understand if you don't want to add that. It's not that important to me.

[bayang]

Should be ok in 0.29.0