fix tagloud limitation

Issue #1096 new
Robert Jäschke
created an issue

The new tag cloud size limitation seems to break some tag clouds, e.g., the tag cloud on

http://www.bibsonomy.org/group/kde

shows only the first X tags by alphabet!

Even worse, the related tags (!) for

http://www.bibsonomy.org/user/jaeschke/sys%3Aentrytype%3Abook

are also sorted alphabetically (they should ALWAYS be sorted by frequency).

Please check this and discuss solutions with Robert.

Comments (7)

  1. Anonymous

    Commented by derbeukatt: This bug is not as easy to fix as one would think. Problem persists in the chain that handles the database access. If a system tag is found it redirects the query to find all existing tags from the user. As a result in my testcase about 2000 tags were returned.

    This means the ratio of tag.usercount to cmd.tagGlobalCount for the related tags is always below the offset of 0.03, so no tag gets a tagclass. This results in the alphabetical ordering of the related tags.

    To solve the problem we have to fix the handling of system tags and query the related tags of system tags. This is not so easy because we have to join the tas table with the bibtex table to get info for entrytype system tags. The bibtex table unfortunately does not have indexes for year and entrytypes in that table.

    Another solution would be to simply not show the related tags for system tags.

    As this bugs needs further investigation and handling I would suggest to possibly fix it after the next release.

    Any further suggestions?

  2. Anonymous

    Commented by derbeukatt: Still no proposed solution. Assigned to nobody, because I won't be working as Hiwi from April on.

  3. Log in to comment