View Single Post
Old 02-09-2010, 02:51 PM   #6
theducks
Well trained by Cats
theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.
 
theducks's Avatar
 
Posts: 31,147
Karma: 60406498
Join Date: Aug 2009
Location: The Central Coast of California
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
This completely blows an idea I had out of the water.
I was going to request comments on having an additional "Last Changed date" field to record the date of the last change made to the underlying files.
Add a Format. Date bumps.
Change Meta data. Date bumps

Date current records the Creation date of the Record entry. I realize, it can be changed, but I think having a First entered date is useful.

Having the Last changed date allows me to determine what needs to get sent to my device next connection.
Since Calibre is managing things, why not have a separate BMK_(file-ver) file that gets merged/sent only on transfer or read if View

This eliminates the confusion of which version is the "newer" file. (Am I the only one correcting spelling and formatting?)
theducks is online now   Reply With Quote