Quote:
Originally Posted by Terisa de morgan
Cannot you include that column when you define fields to include the catalog?
|
As far as I can tell the only options to include fields in an EPUB catalog are:
- Which field is used for Genre section (Genres index). Only text-type fields are acceptable. Composite columns are not acceptable.
- "extra description notes": text included next to the cover thumbnail. Series-type columns are not acceptable. This is per-book, not indexed.
- "merge with comments": This puts the value of the column before or after the comments in the catalog. Again, only text-type columns are acceptable, including multiple-valued columns and composites. Series-type columns aren't acceptable. This is per-book, not indexed.
If I am reading this right, there is no option to include a series-type column anywhere. The only exception is "series", which is a base-level section.
If you want a column to be indexed then the only options are one of the built-in sections such as "tags" or a text-type custom column named in the "Genres" section. Series-type columns can't be used so there is no way to involve the series_index in the section.
You can get a highly-expanded index of custom series information by creating a tags-like column where each tag is "series name":"series index". This can't be a composite column so would require building by hand or using Action Chains to populate it from some series column. To ensure proper order the series index must be formatted with leading zeros. The downside is that each member of the series will appear in the index, not just the series name. One could add these values as a tag using Action Chains, leaving the Genre column available for something else.