Coming from a library science standpoint -- it's fallen out of vogue with the general public. Things like Google and other web-search engines show that you can get a reasonable level of findability with minimal human effort through use of full-test searching.

Unfortunately, as time is showing, it's very possible for people to game the system by inserting false or misleading terms, and search quality suffers when there are many words that describe the same concept (synonyms), or many concepts used by the same word (homonyms).

Cataloging has its benefits, and can lead to improved findability in many situations -- but it takes work. And it requires continuous maintenace, as there has to be a group that deals with decisions about adding new categories, or pruning old categories, and work required to reclassify the existing items as the word list changes.

So basically -- it's a lot of work. The work grows above linearly for both size and time. (I don't know that it's exponential, though, maybe for small values (1.01^size) or similar).

Perhaps this is something that AnnoCPAN can add in, so the work can be distributed across multiple people. (but then you have to make sure that everyone is clear on exactly what the categories are, so there's consistent catalogging).


In reply to Re^3: Module categorization by jhourcle
in thread Module categorization by szabgab

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.