Quote:
|
- Not quite sure how we should build UUID, when from scratch... might be dependent from other fields ?
|
Why not keep it? It's a random ID string, that tries to provide an unique ID. Since you copy the annotations, might as well keep them. For syncing it can be useful, though outside PB Cloud I can't think of any using it yet.
Quote:
Originally Posted by Frapi
Then copy back books.db on reader's /mnt/ext1/system/config/
(with a rooted reader it might be more convenient)
reboot
|
This can also be `/system/profiles/default/`, especially for recent devices.
Quote:
|
- books you want to add notes for MUST have been opened at least once on the reader (they are not listed in books table otherwise)
|
Good, don't get stuck re-creating the metadata. On firmware changes this might break.
I'd suggest letting the user selects a book title first. Then get its book OID. In `Items` there are rows that link the book OID with the actual annotation data in `Tags`. These `Item` rows need to be moved.
Next copy the related `Tags` rows over. No need to be specific about the TagID rows for each note, just copy them all.
One assumption is the source/target files are the same, otherwise annotation locations will mismatch.
It's a nice learning project. I could implement it for AVATeR with some GUI window, might even do so later.