View Single Post
Old 01-29-2015, 08:53 PM   #6
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,779
Karma: 30237628
Join Date: Mar 2012
Location: Sydney Australia
Device: none
Quote:
Originally Posted by eschwartz View Post
I am thinking of duplicating the regex functionality, actually. I personally would match it all to the #origfile field, but others might prefer differently. Hence -- fluidity.
Would that handle this

Quote:
Originally Posted by Alexander Turcic View Post
There may be even more information from the original attachment that we would like to extract and embed in the calibre database. For example, the timestamp of the original upload date. Again, this could probably be encoded in the filename if we could somehow tell calibre that this part signifies a custom field named "upload date"
Why reinvent the wheel for what could be done with a handful of saved bulk metadata edit Search and Replace items - we know they will work, I assume the bulk upload to calibre is one off job.

BR
BetterRed is offline   Reply With Quote