Quote:
Originally Posted by chaley
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'.
|
I don't think it's really worth the trouble, if it's that complex. It works fine for me as is, it just requires a bit manual labour.