KOReader and "Kobo/Kindle" Books Integration

[Jadehawk]

Hello everyone and thank you for any answers you can give me.
I am new to KOReader and have been enjoying it on my Kobo Libra Colour and fresh jailbroken PaperWhite Gen 11.

Question is as follow, I have been watching plenty of YT videos on how to install and use features on the KOReader application, but one of the YT creators that is very knowledgeable in KOReader, advice into maintaining a separate book library between my "Kobo Nickel UI" and the "KOReader"

This will have me using more space on my device by having 2 copies of each book.

He says this and I quote when I asked why and where does the advice come from:

Because they uses their own meta data storage and there is a potential risk to destroy the meta data for one or the other. And mobile read forums is where I’ve learned that.

So I have spent a while doing searches in MobileReads for anything related to Metadata corruption in KOBO/KOREADER accessing from 1 single library and have come out with nothing.

Is this still a Factor?
Should I be concern and Split the Libraries?
Was this something that was a Factor in early Versions of KOReader?

Thanx again for any info.

[pazos]

There's no problem having a single set of documents shared across Kobo/Kindle stock system and KOReader (and never has being a problem, AFAIK)

But you might consider the following scenario:

KOReader implements a bunch of "features" to fetch documents, such as:

- cloud storage
- save epubs from wikipedia
- rss/atom news
- download from opds
- ...

KOReader is folder based so these documents steal no processing time from the system. But both Kobo and Kindle use an indexer to figure out which files are documents and extract metadata from them.

Kindles run the indexer as a background service while Kobos run it after each USB session running from its UI.

At some point in time Kobos were very bad "importing documents", so the recomendation to prevent those issues while returning to stock were to put them on a unix hidden directory (a dir starting with a dot). That would prevent them from being indexed by stock.

Nowadays things seem better on kobos so keeping a single version of documents is safe. But remember that all kind of **supported** documents will end up on your home library, no matter if they're wallabag articles or "real" ebooks.

Some people might prefeer to keep their epubs and other ebook formats on a directory available to both systems and hide feeds/read-it-later and related documents away from stock.

It is a matter of choice, of course.

[Jadehawk]

Originally Posted by pazos

There's no problem having a single set of documents shared across Kobo/Kindle stock system and KOReader (and never has being a problem, AFAIK)

But you might consider the following scenario:

KOReader implements a bunch of "features" to fetch documents, such as:

- cloud storage
- save epubs from wikipedia
- rss/atom news
- download from opds
- ...

KOReader is folder based so these documents steal no processing time from the system. But both Kobo and Kindle use an indexer to figure out which files are documents and extract metadata from them.

Kindles run the indexer as a background service while Kobos run it after each USB session running from its UI.

At some point in time Kobos were very bad "importing documents", so the recomendation to prevent those issues while returning to stock were to put them on a unix hidden directory (a dir starting with a dot). That would prevent them from being indexed by stock.

Nowadays things seem better on kobos so keeping a single version of documents is safe. But remember that all kind of **supported** documents will end up on your home library, no matter if they're wallabag articles or "real" ebooks.

Some people might prefeer to keep their epubs and other ebook formats on a directory available to both systems and hide feeds/read-it-later and related documents away from stock.

It is a matter of choice, of course.

Perfect, this makes more sense and thank you for the history lesson.