Beefy Boxes and Bandwidth Generously Provided by pair Networks
Problems? Is your data what you think it is?

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
I think you have a good point re the usergroup, it may start off well, but would probably not keep uptodate much or stay that way.

Voting as such is a nice idea, though as you say it will produce a lot of data. Which reminds me that I added, and then removed again, the "Rating" field, and you've reminded me what that was - we already keep track of how many times a keyword was added to a particular node, which is sort of like voting, only doesn't store who added which keyword, and allows users to add the same keyword multiple times themselves.

Having this as a level power sounds like a good idea.

I wasn't really out to *design* a new keyword system, so much as make the existing one more usable. With a search at least *I* can find stuff I've keyworded the same, and with a documentation, theres a slightly increased chance that others will use the same or similar ones.

If its a concern of the size the table will get, how about attaching the keywords to the nodes themselves somehow? (In the node table, since I'd like to be able to tag everything and anything), although that wouldn't solve the "who tagged it" problem (if there is one).

I'm not entirely sure I understand why there would be any use for anyone abusing the vote-on-keyword thing at all, the search will/should show rating(relevanace), but can be sorted by many other criteria. Also since keywords can be removed, all the effort would go to waste fairly quickly. Adding keywords to someones nodes should *not* IMO, give XP of any kind, either to the adder or the node owner. Limiting votes will just get us less keywords..

Does this mean you don't approve of a documentation at all, currently, or just that you'd like a better system in the future. (This solution will mostly solve my itch, at least, even if I'm the only one using it..)


In reply to Re^2: Keyword Nodelet / Tagging documentation (vote > privilege) by castaway
in thread Keyword Nodelet / Tagging documentation by castaway

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, 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, 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.
  • Log In?

    What's my password?
    Create A New User
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others meditating upon the Monastery: (8)
    As of 2020-05-29 08:27 GMT
    Find Nodes?
      Voting Booth?
      If programming languages were movie genres, Perl would be:

      Results (168 votes). Check out past polls.