Originally Posted by SneeziePacker
I'm new to the forum, have been using Calibre for a couple of months now. I use the Moon Reader + app on my android tablet and have just added in Calibre Companion. I love them all, thanks to those of you that created these tools!
My question - and maybe I am missing something in one of these tools - is how to keep track of what you have finished reading. I have a custom field in Calibre (yes/no) where I record what I've finished reading. I use that tag to keep anything already read from appearing in my content server.
The piece that I'm missing is how to keep track of what I finish on my tablet and remember to update my Calibre data later when back at my PC. I know I can send myself an email or something similar to that. I have used Moon Reader to "Add to Home Screen" as an easy reminder.
Are there any better ways out there?
Welcome to MobileRead.
There are two parts to my answer: what you can do today and what we (CC's developers) are thinking about for the near and more distant future. Comments welcome.
Today: Assuming you use CC as your organizer then there is one aide available now. CC keeps track of the date you pressed "Read" to open the book in your reader app (Moon+ in your case). You can sort on this date, showing the latest at the top of the screen. The idea: you use this sorted list on your tablet as a memory aide/hint to check and update manually the yes/no column in calibre. I agree that this is not the best solution, but it can help and is easier than sending email.
Later: I am looking at how to transfer the date read column into calibre's library. The idea: the user would give CC (in CC's settings) the lookup name of a calibre date-type custom column. If CC has this name, then it would attempt to transfer the date read value into that custom column column on every connect (as a wireless device). The user could then sort or search on the date column in calibre and manually update other columns as desired. My problem: although the feature isn't particularly hard to implement, I am not completely convinced that it is useful enough to justify the time and complexity to build it.
Even later: We are looking at adding the ability to edit certain metadata items in CC, transferring the changes to calibre when you connect as a wireless device (not via the content server). The fields we are considering are tags and ratings; and text, ratings, and yes/no custom columns. There are several issues for us to resolve.
- This feature is rather hard to implement and opens the door to creating a slew of bugs both in calibre and in CC.
- Adding a general mechanism to calibre for a device to update metadata in the library is not easy. For example, what happens if the column is changed in both calibre and the device? What happens if the user has multiple libraries? What happens if the user deletes the custom column? Which value does CC show between the edit and the connection?
- Questions about user expectations. Being able to edit *some* columns will immediately create the demand to edit *all* columns, complete with negative reviews because we can't. Editing (for example) title, author, and series creates problems that we really don't need. Negative reviews create significant support and sales problems. Following the "do it right or don't do it" principle, perhaps it would be better to do nothing if we can't do everything.
- Questions about usability. The natural place to put the editing is in book details. However, people will probably want to edit on the group lists, increasing the complexity of the UI and the implementation.