Thread: K5 Collections Manager
View Single Post
Old 08-09-2012, 03:29 PM   #75
ixtab
(offline)
ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.
 
ixtab's Avatar
 
Posts: 2,903
Karma: 6677559
Join Date: Dec 2011
Device: K3, K4, K5, KPW, KPW2
Quote:
Originally Posted by NiLuJe View Post
I finally had time to start playing with the Calibre import/export! It's pretty cool

A quick question about the import: Does it reset the visibility/parent(s) of *existing* collections?
Nope. This is now made explicit in the description. Note that versions <= 1.2.0 would actually remove child collections from a collection whose "other" content was modified; this is fixed with v1.2.1.

Quote:
Originally Posted by NiLuJe View Post
* When the cdeKey begins with *, it means that there's no ASIN (or fake UUID as ASIN) in the headers of the book, and the key was derived from the sha1sum of the absolute path of the file. That changes the format used in the legacy json file. It's just 'cdeKey', instead of '#cdeKey^cdeType'. (Right now it's exporting stuff as '#*sha1sum^EBOK' instead of just '*sha1sum').

* The lastAccess field is faked in the exports, but that's not a huge deal .
Both of these should be fixed in 1.2.1. Since I don't have books which match the first case, please report back on whether it works as it should now. (but it should )

Quote:
Originally Posted by NiLuJe View Post
* In the same 'no ASIN' vein, in the case of Kindlets, the cdeKey is NULL for custom stuff. They don't get exported. I don't think there's anything we can do on that front (well, except making Kindlet authors put a fake UUID in the Amazon-ASIN field of their Kindlet Manifest), just mentioning it . (They used the same *sha1sum trick as for books on previous firmwares, so custom Kindlets could be managed via Calibre).
That's right. Anything which doesn't have a cdeKey (or doesn't pass a few other sanity checks) is vigorously ignored

Thanks for the reports and the testing!

Last edited by ixtab; 08-09-2012 at 06:31 PM.
ixtab is offline   Reply With Quote