Beefy Boxes and Bandwidth Generously Provided by pair Networks
Do you know where your variables are?

keywords baby steps

by tye (Sage)
on Mar 21, 2007 at 21:28 UTC ( #605926=pmdevtopic: print w/replies, xml ) Need Help??

I think a relatively small step toward making keywords (as in the Keyword Nodelet and keyword search, the latter currently "tough beans" for non-pmdev) eventualy much more useful and more immediately somewhat less useful for anonymous abuse, would be the addition of an approved keywords table.

This approach occurred to me in part because it would also make keyword search less likely to become a resource hog. It won't do enough to make keywords /really/ useful, but I think it is a small step in the right direction that could eventually result in a reasonably nice system.

The idea is a new table that only vetted group members could add keywords to. I'd just make a new access rule rather than a new group, at least at first, allowing janitors, sidedocclan, and pedagogues to add/delete approved keywords and delete (at least at first) keywords on nodes. Those wanting access to do keyword approval could join pedagogues. Note that I wouldn't add pmdev as the ranks there are too swolen and unchecked, IMHO.

The other pices to be added, in nearly whatever order, include:

  • Hiding or de-highlighting unapproved keywords displayed in the keyword nodelet
  • Adding a user option to show unapproved keywords in the keyword nodelet (which selects between the "hiding" vs "de-highlighting" above and default to "don't show", that is, "hide")
  • Encourage addition of only approved keywords via the keyword nodelet, but allow addition of unapproved keywords to be considered as requests for new keywords to be approved by the vetted users or as clear abuse to be deleted by them (or something between to be left in limbo). I'm not sure the best interface for this "encouragement" (does HTML allow drop-downs that also allow editing? I don't think so).
  • Prevent anonymous users from adding unapproved keywords (they won't see them either since they can't change the user setting away from the default value)
  • Accountability and voting. So abusers can't be anonymous and so non-vetted monks can chip in selecting the best keywords. The current "voting" is pretty pointless for many reasons. Voting per keyword per node is likely too much data to be worth doing. But voting on approval status of keywords might be worthwhile.
  • Only showing approved keywords in the keyword search drop-down. To search for an unapproved keyword, you'd need to just type it in or, for vetted members, request the list of unapproved keywords (perhaps a new node for that).
  • Add a "keyworders' wiki" that all non-anonymous monks can write to (at least at first) for discussing keywording. (Note that creating a usergroup with a large number of members is not a good thing to do at PerlMonks.)

Note that I'm not volunteering to implement this. Just a design idea as a starting point. I'll certainly do some applying of patches, creating of tables based on MySQL definitions someone else works up, etc. Those gods-only tasks, etc.

- tye        

Replies are listed 'Best First'.
Re: keywords baby steps
by bobf (Monsignor) on Mar 22, 2007 at 03:23 UTC

    Thanks, tye, for a very well thought out node on this subject.

    In essence you are proposing to construct a controlled vocabulary for keywords. As someone that has been working with controlled vocabularies and metadata for the last two years (see the ISO/IEC 11179 standard for metadata registries or the Wikipedia entry, if interested), I appreciate the effort. If done well and used properly, this could add significant search functionality to the site.

    According to your outline, terms in the vocabulary can be proposed by members of the community but they are approved and maintained by a small group. IMO, this is a very reasonable way to start and it is similar to my experiences in this area.

    I agree that voting on each keyword of each node is probably more effort than it is worth. I'm not sure about voting on the approval status of individual keywords, either, unless many controversial keywords are anticipated. I suspect it will be pretty clear-cut which should be approved, and the others could simply be left as unapproved (similar to our current moderation process). I would hope that the wiki could be used for discussion and to achieve consensus without having to implement a formal voting process, but I'm probably wishing for too much. :-)

    As a start, we could limit keywords to module names, entries in perldoc (similar to the [doc://] tags)), and a few obvious key words (e.g., "data structure"). Key words that are too general (e.g., "Perl") may not be worthwhile.

    I'd be happy to help with this effort if another monk were willing to lead it, but I do not have the expertise required to pursue this on my own.

Log In?

What's my password?
Create A New User
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others surveying the Monastery: (3)
As of 2017-07-26 02:35 GMT
Find Nodes?
    Voting Booth?
    I came, I saw, I ...

    Results (383 votes). Check out past polls.