Spent ages awhile back delving deep into sorting audio tools into a multi-dimensional framework, convinced that deciphering their taxonomy would unleash their full potential. It's frustrating how there are no comprehensive directories for these tools (Linux or not for that matter)
I applaud your initiative and suggest you give more thought to categorization.
The good'ol "organize your stuff" problem. The problem with "categories" is that a) usually a "thing" can only belong to 1 category and b) a category often belong in a hiarchy of categories and can only be 1 place. So that is why I've used _tags_ instead, which is more of a many to many "flat" releation. Not sure I understood your comment correctly? ..I've certainly given this quite some thought already, but nothing is perfect
I agree, and moreover, the more complex the taxonomy, the more likely you'll find people who disagree with it. So perhaps you're right that a simple tags list is the best "simple" solution, and I'm not saying your list is deficient.
One thing I had in mind is allowing an "AND" operator, like searching for "vintage" AND "eq"
a) usually a "thing" can only belong to 1 category and b) a category often belong in a hiarchy of categories and can only be 1 place
That's why I love hierarchical tags (where tags can have multiple parents) : You can put a "thing" under more than one category/tag while a tag can belong to more than one parent. However, it's true that this is rarely implemented.
Comments
Spent ages awhile back delving deep into sorting audio tools into a multi-dimensional framework, convinced that deciphering their taxonomy would unleash their full potential. It's frustrating how there are no comprehensive directories for these tools (Linux or not for that matter)
I applaud your initiative and suggest you give more thought to categorization.
The good'ol "organize your stuff" problem. The problem with "categories" is that a) usually a "thing" can only belong to 1 category and b) a category often belong in a hiarchy of categories and can only be 1 place. So that is why I've used _tags_ instead, which is more of a many to many "flat" releation. Not sure I understood your comment correctly? ..I've certainly given this quite some thought already, but nothing is perfect
I agree, and moreover, the more complex the taxonomy, the more likely you'll find people who disagree with it. So perhaps you're right that a simple tags list is the best "simple" solution, and I'm not saying your list is deficient.
One thing I had in mind is allowing an "AND" operator, like searching for "vintage" AND "eq"
That's why I love hierarchical tags (where tags can have multiple parents) : You can put a "thing" under more than one category/tag while a tag can belong to more than one parent. However, it's true that this is rarely implemented.