View Single Post
Old 01-15-2016, 02:43 AM   #4
BetterRed
null operator (he/him)
BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.
 
Posts: 21,803
Karma: 30277270
Join Date: Mar 2012
Location: Sydney Australia
Device: none
@kensmosis - arrgh - you mean the file system dates Sorry, I think of the file system and the operating system as two different beasties.

You're not going to like this - I don't think there is a way to wrangle mtime, ctime, atime, or dtime directly into calibre.

Calibre has two accessible standard date columns: Date/timestamp and Published/pubdate, the Modified/last_modified column is a read only column.

If you were to put the create date (crdate) into the file name (via say a mass rename) then you could put that into Published/pubdate via an add time regex - see Preferences->Add Books->Configure metadata from file name.

The 'difficulty' with importing file system timestamps relates in part to: a) calibre supporting various file systems on various operating systems, b) there can be more than one format file for a book each with its own dates, and c) in most cases the file system dates bear no relationship to anything but when the file landed on my computer and what's happened to it since.

BR
BetterRed is online now   Reply With Quote