|
There's no pressing need, IMO, for custom columns to be usable for collections. The same effect can be produced by either enclosing all the tags you don't want to create collections from (workflow tags, for instance) in [square brackets] or, if you want to use a custom column, do as I do and move the workflow tags into that custom column, leaving in the standard tags only those tags you want to create collections from. I have a column named "workflow" -- slightly inaccurately named, actually, because it also includes tags for internal/card destination, DNU for books that shouldn't be uploaded (mostly PDFs that give my 505 fits), etc. Everything in my normal tags column is genre, etc., to create collections.
|