Manually adding book to database

[geek1011]

I am working on a standalone, command-line tool to update series metadata on a Kobo eReader (you can see my progress so far here). I would like to be able to update the metadata, even if the user has not actually imported the book yet.

Is it possible to manually import a book to the Kobo, and if so, is just adding the it to the content table sufficient?

[davidfor]

Originally Posted by geek1011

Is it possible to manually import a book to the Kobo, and if so, is just adding the it to the content table sufficient?

Yes, it is possible, and I have done it in the dim distant past. There are enough issues with it, that I just didn't find it worthwhile or want to maintain it as the database changed. But, if you do it, you also need to add rows to the table volume_shortcovers.

[geek1011]

Originally Posted by davidfor

Yes, it is possible, and I have done it in the dim distant past. There are enough issues with it, that I just didn't find it worthwhile or want to maintain it as the database changed. But, if you do it, you also need to add rows to the table volume_shortcovers.

Ok, that seems straightforward enough.

What were the issues with it? I do not seem to see any obvious ones.

[davidfor]

Originally Posted by geek1011

Ok, that seems straightforward enough.

What were the issues with it? I do not seem to see any obvious ones.

You've worked out exactly what goes into each column of the contents table? For each book format? And exactly what to do about the table of comments? And how to handle the changes that have happened with different firmware versions?

From my experience, it wasn't reliable. I could do it, but frequently the book would get imported anyway. The creator of the KoboTouchExtended driver tried as well. We both decided it wasn't worth the hassle. I probably know more about it now then when I first tried, but, again, I just don't think there is enough gain to make it worth the effort.

[geek1011]

Originally Posted by davidfor

You've worked out exactly what goes into each column of the contents table? For each book format? And exactly what to do about the table of comments? And how to handle the changes that have happened with different firmware versions?

From my experience, it wasn't reliable. I could do it, but frequently the book would get imported anyway. The creator of the KoboTouchExtended driver tried as well. We both decided it wasn't worth the hassle. I probably know more about it now then when I first tried, but, again, I just don't think there is enough gain to make it worth the effort.

I think I have figured out most of the columns but I am still testing. I am only planning to use ePub and kepub files. I am only planning to support the latest firmware version, and whichever one I use.

The other alternative for my use case is to inject a helper script as a update which would perform the database changes after the content is imported. Do you think this would be an easier option?

[davidfor]

Originally Posted by geek1011

I think I have figured out most of the columns but I am still testing. I am only planning to use ePub and kepub files. I am only planning to support the latest firmware version, and whichever one I use.

That will cut down on the work needed.

The other alternative for my use case is to inject a helper script as a update which would perform the database changes after the content is imported. Do you think this would be an easier option?

If you can get it run at the right time, it should work. I've never really looked at it.