Quote:
Originally Posted by dwanthny
Quote:
Originally Posted by Worldwalker
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.
|
Many of the same folks who would like custom columns for collections have let their tags build from metadata downloading. For the most part it really isn't a question of workflow, and bracketing the 100s of tags they have would be more work then it's worth. |
Well, I don't download tags, and I still want custom fields as collections. I don't like the hack of enclosing tags in [ ], because they sort to the wrong place and they are harder to read. In addition, almost all my tags are hierarchical (like genre) with a restricted namespace, and that is very hard to do with a single tag category. I tried for a while to do it with prefixes, but they grew long and ugly. Solving this problem was my biggest driver for building custom columns.
Fortunately, custom fields as collections is on my to-do list (and is mostly done), so I will get what I want.
