Quote:
Originally Posted by compurandom
Despite your apparent irritation at this being brought up again, I was grateful the last time it was brought up, because I didn't get it when I read the instructions.
The instructions as currently written do a great job of explaining the best way to do it, but they don't explain well why it is useful to make a new custom column for tags rather than use the perfectly good one that already exists.
|
If that was JSWolf's problem, I'd be OK. But, his problem is that he doesn't think custom columns should be mentioned at all. The instructions could probably do with a rewrite. And if someone wants to do that, then good.
Quote:
|
I assume by that you mean that the pre-existing tag column is useless because it becomes polluted with what publishers think things should be tagged with, rather than what you want your shelves to be. Not that a tag formatted custom column is useless, which is what I think you don't mean to imply.
|
Yes the "tags" column is useless. The type of information in them tends not to be how I want to organise things. Plus, it would lead to a much larger number of collections. I use two or three different tag type columns, but one is a status column associated with some Reading Lists, and the other is manually maintained.