Quote:
Originally Posted by davidfor
The Kobo is opening the book to get the title and author. As the rest of the metadata is either in the OPF or comes from the file system, it isn't going to add much time to it.
|
Surely it requires time to write to the database, and makes the database bigger, etc. -- even if there isn't any additional penalty for extracting the OPF?
Quote:
|
Word count, or even page count, would be better as I sometimes choose a book based on size (due to mood, opportunity to read etc). But, I have a fair idea of the book length based on the file size using my experience with the books and the known sources.
|
I have found filesize to be wildly erratic. Not only does filesize not have any good reason to be a good indicator of book length, it conforms to my expectations by not being a good indicator.
Quote:
|
A format of epub/kepub, PDF, CBR/CBZ, text etc does tell me something - fiction, text book or other info, comic book and "why do I have plain text on the device?"
|
I can get all that from the title and cover image.
Quote:
|
As the sideloaded books are not directly linked to a shop somewhere, using that method is useless. Plus about half of my read is done somewhere without connectivity, so it wouldn't help. And if I want to look at the jacket, that means I have to open the book which marks it on the Kobo as open. I can unmark it, but, that's extra work. And from what I can see, the reason that calibre metadata jackets exist is because so few of the ereaders support displaying this information separately. There is no way I would buy one that didn't.
|
Very true. Amazon wants you to buy books from their store.
I don't really look at summaries, but if I did I would be disappointed on most devices, as you pointed out.
Quote:
|
I'll beg to disagree. Embedding the series info in the title is a hack done because the device can't display it separately.
|
Perhaps that is why I agreed with you...
Quote:
The Kobo's generate the cover images as needed. It does waste some space by having different sizes for different places, but it works fine. Or calibre can generate them during the send.
The simple thing here is that the point of the metadata being in the book is that applications can use it. And hopefully in a way that is useful to the user. I am interested in seeing most of the metadata above. I do look at it when choosing a book. So, the time taken in building this is useful to me. If Kobo speed it up, then great. If they add a bit more info, just as good (I'd love to see tags and filter based on them).
|
And I still cannot understand why half that metadata needs exist outside of an archival database.
Quote:
Originally Posted by Terisa de morgan
@eschwartz, sorry, yes, that's the info I was talking about. Not interesting for you, the main reason I won't have a Kindle unless they change library management or I have no other option. Different people, different choices, but it keeps on being more metadata extraction in Kobo than Kindle.
|
I guess I understand where you are coming from... partly. I still think it seems to be extracting more metadata than is actually needed.