View Single Post
Old 10-16-2013, 07:33 PM   #3
At_Libitum
Addict
At_Libitum ought to be getting tired of karma fortunes by now.At_Libitum ought to be getting tired of karma fortunes by now.At_Libitum ought to be getting tired of karma fortunes by now.At_Libitum ought to be getting tired of karma fortunes by now.At_Libitum ought to be getting tired of karma fortunes by now.At_Libitum ought to be getting tired of karma fortunes by now.At_Libitum ought to be getting tired of karma fortunes by now.At_Libitum ought to be getting tired of karma fortunes by now.At_Libitum ought to be getting tired of karma fortunes by now.At_Libitum ought to be getting tired of karma fortunes by now.At_Libitum ought to be getting tired of karma fortunes by now.
 
Posts: 265
Karma: 724240
Join Date: Aug 2013
Device: KyBook
Quote:
Originally Posted by theducks View Post
Sounds like a good case for a PI.
Map detected optional DC Metadata to PRE-designated Custom fields
Well, actually it seems dc:source is one of the standard fields so I would consider that not a good solution because then you lose the original data as nothing else but Calibre can read Calibre's custom metadata

Of course if dc:source is present in the original it will likely remain present, but if you create an epub from scratch (i.e. metadata going in the other direction) then you have to be aware that custom columns will end up as custom metadata and that you will still need to fill in these 'standard' fields manually if you want to have them contain data.

Last edited by At_Libitum; 10-16-2013 at 07:37 PM.
At_Libitum is offline   Reply With Quote