Another request for a different calculation of the tagsize within the cloud. Usually the tagcloud represents those tags bigger, that have more nodes tagged with it. That is a representation of what topics are best served with content. This is good for a communitysite.

Now think the other way round: The site is made by a single person and the tag cloud should represent those tags bigger, that have the highest average hitrate. That is representation of what topics are mostly read.

In fact, there is the module "interests" but that depends on "users" interests again. A user can see the popularity of certain tags he is interested in as a cloud. So this is not a general module for the relation "one content creator" -> "mostly anonymous readers". And I'd like to have one module for Tagclouds instead of many for different features.

My suggestion is to implement a feature, that is enabled, when core-module "statistics" is enabled. The average hitrate of all nodes with a certain tag should effect its size within the cloud. To prevent too high, constant cpu-load a cron-based calculation could also be implemented for highly frequented sites.

--
Felix aka YAFA

Comments

Bèr Kessels’s picture

Status: Active » Closed (duplicate)