Category terminology consistency
| Project: | Drupal |
| Version: | 7.x-dev |
| Component: | usability |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Remove taxonomy from handbook.
Example sites
Explain what you can do with one one term
Multiple terms for shadowing effect of using multiple terms - Use case
-one term means something to one use
-two terms might capture someone else
-Could have second vocabulary that would lend it self to a different use case.-meta data
-search
-similar things get value when given context. Semantic context of content. More information, the power of synonymous terms for accessibility. Helps in discrimination.
Advocacy-welfare,
Narative structure: usability issues
Folksonomy: completely separate,
Ajax autofill will help you want to understand.
Obvious: order of the characters -
Semantic meaning helps people-
War - occupation , free election, support
Building out different vocabularies:
Progressive: Occupation, imperialism, violence, crusade
Converstive: Liberation, support our troops, democracy, election
New storys, foriegn news, international, !interivew, !editorial
Ethnic groups: -
Resources would inform how to go about creating these terms: Information architecture: Role of editor,
Discover the common language
#1
I have collected a few quotes from people on taxonomy.
"Why do you put taxonomy under classification, when it clearly is taxonomy. I searched my site for ages, after reading about Drupals taxonomy, but never thought it would be stuck under classification"
"This is really confusing: You have classifications, terms, vocabularies and taxonomy. I understand that terms are the tags in a vocabularies and that that is called taxonomy, but what is the relation with classification?"
"What drives me nuts is the fact that you (drupal.org) keep on giving examples with "directories", or "how the world sticks together in taxonomies", how they can be used to make my navigation wowee. But nowhere is anything to be found about how I can use it to simply add three or four sections to my weblog!"
(this is a random cut from various Dutch quotes from clients)
the commom denominator is:
We use FAR too many different words for one thing. It should be either classification (in which case we must find a new name for trees (voc) and terms (tags) ), OR taxonomy+term+vocabulary. We fail to fullfill (explain) the simple needs by diving right into "the enormous power of taxonomy".
taxonomy, the word, is not the problem. The interface and the explanation is.
On top of that, I found that when having a simple set of example taxonomies, there is nothing going on. Taxonomy is not hard to grok, its the power and uses of that power, that are hard.
Bèr
#2
What progress have we made on this issue? We should reopen the dialog on this issue.
#3
Judging by the help text in Categories admin in Drupal beta 2, none:
"The taxonomy module allows you to classify content into categories and subcategories; it allows multiple lists of categories for classification (controlled vocabularies) and offers the possibility of creating thesauri (controlled vocabularies that indicate the relationship of terms), taxonomies (controlled vocabularies where relationships are indicated hierarchically), and free vocabularies where terms, or tags, are defined during content creation. To view and manage the terms of each vocabulary, click on the associated list terms link. To delete a vocabulary and all its terms, choose "edit vocabulary".
Nobody can grok this!
Even more confusing, when you have no vocabularies at all, the list message is "No categories available". But you can't create categories, you have to create vocabularies.
"Categories" is just the admin page's name, it is not used anywhere else. In fact it would be less confusing if the admin page was named "Classification".
#4
We should use the term Category when referring to the feature.
We should use the term Category Set when referring to a vocabulary.
We should user the term Category when referring to the terms of a vocabulary
We should use the term Add Categories when referring to the action adding terms to a Category set
we should use the term Add Category Set when referring to the action of creating a new vocabulary.
What do you think gang?
#5
On second thought, I found this issue: http://drupal.org/node/48576
There they suggest a naming of Categories (category, term, keywords)
I like that, but I'm confused. I've tried to create a new vocabulary and terms in my test site and I only see the creation process as 2 levels deep. I create a vocabulary and I create terms for that vocabulary, but I can't create anything that is grouped for that term.
#6
Is there a consensus to avoid the word "tag"? "Tag" is used everywhere these days, everybody knows what a tag is. "Term" is more vague, but maybe "tag" now has too many meanings as they are used and misused in very different ways on the web.
A category would be described as a group -or a set- of tags on a particular topic.
Categories / Category set / tag?
Also, keep in mind that each "term" can have children terms ("subcategory sets", if you prefer)
#7
I use the del.icio.us bookmark service. They also utilize terminology of tags. They call each "term" a tag. For them tags are their atomic unit. You then are able to group tags into Bundles. You can also group bundles into bundles.
Perhaps this bottom-up organization is best.
#8
The user experience project is closing so this issue is being moved to the usability component under the Drupal project