Kobo Collection Manager revisited

[JeanC]

Hi,

I started my kobo collection manager project anew. I've put it up for download. Disclaimer, it works for me, on my kobo libra 2, and there's no guarantee it will work for you too. But maybe it will be useful for someone else too.
It comes with a helpfile and a file called main.cpp with the source (latest c++ rad studio).

https://jcremers.com/Kobo.html
forum thread: https://forum.jcremers.com/index.php/board,15.0.html

[JSWolf]

Originally Posted by JeanC

Hi,

I started my kobo collection manager project anew. I've put it up for download. Disclaimer, it works for me, on my kobo libra 2, and there's no guarantee it will work for you too. But maybe it will be useful for someone else too.
It comes with a helpfile and a file called main.cpp with the source (latest c++ rad studio).

https://jcremers.com/Kobo.html
forum thread: https://forum.jcremers.com/index.php/board,15.0.html

How does this differ from what we can do with calibre?

[JeanC]

Originally Posted by JSWolf

How does this differ from what we can do with calibre?

It's far less hassle than with calibre, you don't have to build a library etc. This is for people like me who dislike the bloat in calibre. You just upload books right away into an existing or new collection. 3 clicks and you're done.

[JSWolf]

Originally Posted by JeanC

It's far less hassle than with calibre. You upload books right away into an existing or new collection. 3 clicks and you're done.

Would this not be better to be a calibre Plugin? The problem as I see it is you'd need to manage your books twice. Once in calibre and once in your collection manager.

[Sirtel]

Originally Posted by JSWolf

Would this not be better to be a calibre Plugin? The problem as I see it is you'd need to manage your books twice. Once in calibre and once in your collection manager.

Why would you need a second collection manager if you use calibre? Kobo driver does it well enough for those who manage their books in calibre.

[JSWolf]

Originally Posted by Sirtel

Why would you need a second collection manager if you use calibre? Kobo driver does it well enough for those who manage their books in calibre.

I wouldn't. But @JeanC either doesn't use calibre or finds his program easier to use.

[Sirtel]

Originally Posted by JSWolf

I wouldn't. But @JeanC either doesn't use calibre or finds his program easier to use.

If he doesn't use calibre, why should his program be a calibre plugin?

[JeanC]

Hey, it works for me, like it says in the disclaimer: I have uploaded books, managed / edited / deleted collections and books and i have no errors anymore and all seems to work. Maybe it's useful for someone else too, that's all i'm saying. I included the c++ source btw.

Connect the kobo, start the app, choose upload books (F8), in the first dialog you can select books, the second dialog lets you either choose an existing collection, or enter a name for a new one. The app uploads the books and creates the collection(s).

Then you disconnect the kobo so that it can rebuild it's database with regard to the uploaded books, and it will show those books in the collections you made / edited. Very straightforward.

[JSWolf]

Originally Posted by JeanC

Hey, it works for me, like it says in the disclaimer: I have uploaded books, managed / edited / deleted collections and books and i have no errors anymore and all seems to work. Maybe it's useful for someone else too, that's all i'm saying. I included the c++ source btw.

Connect the kobo, start the app, choose upload books (F8), in the first dialog you can select books, the second dialog lets you either choose an existing collection, or enter a name for a new one. The app uploads the books and creates the collection(s).

Then you disconnect the kobo so that it can rebuild it's database with regard to the uploaded books, and it will show those books in the collections you made / edited. Very straightforward.

How are you editing the database so you don't have to connect a 2nd time?

[JeanC]

Good question. Because the books all have a unique id that you can predict because it's composed of the filename, which is unique and mostly also contains a map named after the collection. This predicted unique id can be used to create the collection.

[JSWolf]

Originally Posted by JeanC

Good question. Because the books all have a unique id that you can predict because it's composed of the filename, which is unique and mostly also contains a map named after the collection. This predicted unique id can be used to create the collection.

The filename? What if I have two books with the same name?

[DNSB]

Originally Posted by JSWolf

The filename? What if I have two books with the same name?

What if the filename does not consist only of the book title? What if it includes the author name or other additional data such as series/index?

If you happen to have two books with the filename The_End_Of_All_Things_-_James_Harrison.epub, you have other issues to worry about.

[JeanC]

filename is unique on a kobo, or the same book in two different maps, just like any other filesystem, that's just the way things work on the kobo, a books id is derived from the filename. You don't have to believe me, investigate yourself or ask an expert.

Anyway, if it does not appeal to you, i'm sorry, you are free to stick with what you have.

[PeterT]

I thought at one poinbt that the KoboTouch driver did handle collections on the initial connection, but not series (or other metadata). My very limited testing in my bastardized environment though did not show that as working as I thought it did

It's times like this I wish we still had access to @davidfor


INTERESTING BUT WRONG. SEE MY NEXT POST

[JeanC]

well, my app works like it should, what can i say, i don't see a problem.