View Single Post
Old 09-22-2010, 07:05 AM   #77
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 12,476
Karma: 8025702
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
Quote:
Originally Posted by Manichean View Post
Actually, never mind, it just occured to me that I can do this by creating one of those composed custom columns.
For a lot of reasons I agree with dwanthy's opinion. The complexity is already extremely high, and templates would make it worse.

However, I am willing to add composite columns as a source field. It provides a template facility, but it does so in a way that makes the choice between source fields explicit and obvious. Of course, the composite fields cannot be a destination, and wouldn't be offered as one.

Imagine you set up a composite as '{series} - {series_index} {title}'. Specify this as the source. Use a regexp '^(- )**' and a null replacement. Set the destination to title (or wherever). For books with series Foo index 1, the result is 'Foo - 1 - Title'. Without series, you get 'Title'.
chaley is offline   Reply With Quote