Commons talk:Categories

From Wikimedia Commons, the free media repository
Jump to: navigation, search
Info non-talk.svg Need help with categories? Try the Commons:Help desk. Questions about how to handle a category issue? Try Commons:Help desk or (if the issue has wider implications), Commons:Village pump.


Legitimate cases of over-categorization[edit]

Belongs in cat:Dih4 cycle graphs because the top vertex shows a Dih4 cycle graph, but it would be wrong to remove its parent cat:Dih4 because this image is no cycle graph.

I sometimes stumble upon images that illustrate foo in general, and thus should be in cat:foo - but also show some detail of foo, so that they should be in cat:foo detail as well. (See image on the right.) Technically this is COM:OVERCAT, but I think it is the right thing to do. Opinions? Maybe the guideline COM:OVERCAT should define cases where this is legitimate. mate2code 14:55, 28 February 2014 (UTC)

My opinion on this is rather strict. If this image shows two different aspects of foo it should be in two different subcategories of foo but not in Cat:foo and Subcat:foo. In other words there is no „shows topic in general“, images or media always show specific aspects. --MB-one (talk) 09:01, 14 May 2014 (UTC)
Mate, this does occasionally come up. COM:OVERCAT does state it is a "general rule" because occasionally there are images that arbuably belong in a parent and sub cat. Having said that, I am not in favour of trying to define cases where this would be permitted. It's already hard enough to enforce COM:OVERCAT in balck-and-white cases without additional vague text about "legitimate" violations (which people will inevitably use to drive a truck through COM:OVERCAT). Best left alone. --Skeezix1000 (talk) 15:05, 14 May 2014 (UTC)

Branching and crossing of categorization threads[edit]

I've removed this section from COM:OVERCAT (I've copied it below). If there was discussion with a consensus to change OVERCAT to add this exception, then my apologies and please let me know. Otherwise, it is problematic. First, it's very difficult to understand. I'm a lawyer, I interpret dense legalese every day, yet I do not find this particularly clear. There must be a better way to describe this than referring to "a multifactorial net with multihierarchic traits". Second, I am not sure that I necessarily agree. Just to use the same example of the regional administrative office. It isn't a given that the file should be categorized directly in the subcat for the street as well as in the main parent category for the region. I would consider that COM:OVERCAT. The better solution would be to create a subcategory for regional government buildings or for the regional government. Anyway, hopefully we can sort this out. --Skeezix1000 (talk) 18:38, 7 July 2014 (UTC)

"Note that Commons category structure (as well as Wikipedia categorization) is not a simple hierarchy (like biological taxonomy) but rather a multifactorial net with multihierarchic traits. That's why one subject can be categorized into any category by one factor and into its parent category by another factor and such categorization should be not considered as overcategorization.

  • Example: a category of the Regional Office is categorized to the category of the street where the office bulding is. As regards location, the building should be not categorized directly into the category of the city or the region. However, by attribution it should be categorized into the category of the region because the office is an administrative body of the region and the building is owned by the self-governed region. Such categorization is not overcategorization even though the second category is a parent category of the first category.
  • Similarly, a category of a village which is part of a municipality can be categorized under the neighbouring village by cadastral division (because it fall under its cadastral area) and simultaneously directly to the category of the municipality (because both villages are co-equal municipal parts administratively).

Exceptionally, different categorization threads can even meet each other in the opposite direction (category A is subcategory of B by one factor and simultaneously category B is subcategory of A by another factor) and can create a quasi-cycle. However, such a solution is not preferred and should be avoided if possible."