Quote:
Originally Posted by chaley
They could be hierarchical (separated by dots instead of commas) instead of tags-like, which would make them "clickable" in different ways from the tag browser. Whether or not this would help isn't obvious.
|
True.
From the tag browser only, not the Book Details, and you would only have one series position (for the amalgamated name), and sorting by series wouldn't work (since it is all fundamentally different series' altogether), but at least they would be clickable.
Quote:
Originally Posted by smmorris
Well not the news I wanted to hear but do appreciate the time spent in responding.
Just to clarify. I have the created "series-like" columns for the different types of series.
Not using a plugboard since series isn't a column I can send info to with a plugboard, And my problem is really how the info "displays" in calibre, not how it gets to my tablet.
I am able to make the different series clickable in my combo column but it doesn't display correctly in the column but does display correctly in the book details. In my effort to provide info I suspect I may have obscured the fact that I can't get it to "work" and display correctly at the same time. I can display correctly or make clickable but can't seem to do both at the same time.
|
No need to clarify, that fact was evident in what you said (at least to me).
The fact that
- it displays "correctly" but isn't clickable when using a plaintext column, and
- is clickable but doesn't display correctly when using a tag-like custom column built from other columns
is exactly what I initially read from your post, and is exactly what I said will not work, by design.
You already have multiple series columns. Use those to click on.
Do not use a custom column built from other columns to amalgamate the series' in the Book Details. This is not useful information, except when squeezing it into a Send-to-device plugboard (since devices do not support calibre custom columns).
On which note, you absolutely can insert the series info into the title, which is the usual workaround for devices e.g. the Kindle that don't support a series metadata field.