Quote:
Originally Posted by Katja_hbg
it seems there is no good solution as
‐ catalog is an old feature which is not maintained anymore
‐ only allow text and number fields text and number fields while rating is «specific»
‐ distinguish only between «any» and «unknown» for combined fields
If you are realy interested in it, you may think about the following workaround:
You need one column for each rating. Those can be used for catalog prefix with value = «any».
This example for one of the columns: rating3 either with «3» or keep it empty
{#rating3:'cmp(field('rating'),3,'',3,"")')
|
Thanks, not sure if it'll be worth the effort.
I still use catalogs, since I have my entire collection (>5000 books) on my Kindle, and like to be able to look for something to read (including by genre, which the Kindle doesn't do), so I put a catalog on it in a collection by itself so that it's easily accessible when I need it.