CINXE.COM

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta http-equiv="content-type" content="text/html; charset=UTF-8"> <meta name="viewport" content="width=device-width, initial-scale=1"> <title>Curlie - Category Moderator Guidelines</title> <link rel="icon" href="/img/curlie-ico.gif" type="image/x-icon" /> <link rel="shortcut icon" href="/img/curlie-ico.gif" type="image/x-icon" /> <link href="/css/docs.css" rel="stylesheet" type="text/css"> <link rel="stylesheet" type="text/css" href="/css/docs.css" /> <link rel="stylesheet" type="text/css" href="/css/font-awesome-5.13.0/css/all.min.css" /> </head> <body> <div id="headbar"> <h1><a href="/" title="Return to Curlie Home">Curlie</a></h1> </div>  <div id="side"><div class="navhead">The Curlie Directory</div> <ul class="nav"> <li><b><a href="/">Directory</a></b></li> <li><b><a href="/about.html">About Curlie</a></b> </li> <li><b><a href="/guidelines/">Editing Guidelines</a></b> <ul> <li><a href="/docs/en/guidelines/admin/">Administrator</a></li> <li><a href="/docs/en/guidelines/meta/">Meta</a></li> <li><a href="/docs/en/guidelines/catmod/">Catmod</a></li> <li><a href="/docs/en/guidelines/editall/">Editall</a></li> <li><a href="/docs/en/guidelines/greenbuster/">Greenbuster</a></li> <li><a href="/docs/en/guidelines/kguidelines/">Kids & Teens</a></li> <li><a href="/docs/en/guidelines/regional/">Regional</a></li> <li><a href="/docs/en/guidelines/travel/">Travel</a></li> <li><a href="/docs/en/guidelines/gambling/">Gambling</a></li> <li><a href="/docs/en/guidelines/adult/">Adult</a></li> </ul> </li> <li><b><a href="/erz/">Editor Resources</a></b> </li> </ul> <div class="navhead">In Other Languages</div> <ul class="nav"> <li><a href="/docs/ar/guidelines/catmod/">毓乇亘賷賾丞 - Arabic</a></li> <li><a href="/docs/de/guidelines/catmod/">Deutsch - German</a></li> <li><a href="/docs/es/guidelines/catmod/">Espa帽ol - Spanish</a></li> <li><a href="/docs/fr/guidelines/catmod/">Fran莽ais - French</a></li> <li><a href="/docs/pl/guidelines/catmod/">Polski - Polish</a></li> <li><a href="/docs/ro/guidelines/catmod/">Rom芒n膬 - Romanian</a></li> </ul> </div> <div id="mainContent"> <h1>Category Moderator Guidelines</h1> <ul class="toc"> <li><a href="#intro">Introduction</a></li> <li><a href="#general">General Guidelines</a></li> <li><a href="#newcat">New Category Permissions</a></li> <li><a href="#forum">Joint Meta Forum</a></li> <li><a href="#abuse">Abuse</a></li> <li><a href="#editallcatmv">Editall/Catmv Features</a></li> </ul> <h2 id="intro">Introduction</h2> <p>Category Moderators, a.k.a. CatMods, provide leadership in specific sub-communities, and round out the leadership ranks of the editing community. CatMods have a unique set of privileges which combine the aspects of the Editall and Meta permissions, but their scope is limited to one top level category node (e.g. Arts, Computers, etc.). <br />The purpose of this role is to allow exceptional editors who specialize in a top level category, the ability to become a leader, or moderator, and to oversee the needs of individual category nodes. Category Moderators should lead forum discussions in their subjects, mentor new editors, keep editors on track with reorganizations and current events, and essentially be the expert for that given category.</p> <h2 id="general">General Guidelines</h2> <p>CatMods, as leaders of their category node, are expected to focus more on the community-related aspects of higher editing. Each sub-community should embrace the CatMod as their first point of contact for any conflicts or issues, including heated taxonomy discussions or editor disputes and abuse. Likewise, the CatMod should keep up to date with all related forum threads, and seek out editors to promote, as well as sift out abusers.</p> <p>Category Moderators have the following permissions:</p><ol> <li>Ability to view and process <a href="#newcat">New Category Permissions</a> for their category node.</li> <li>Access to the private <a href="#forum">Joint Meta forum</a>.</li> <li>Ability to <a href="#abuse">warn editors</a> and post notes on an editor's profile.</li> <li><a href="#editallcatmv">Editall/Catmv</a> for their category node only.</li> <li>Ability to view and process <a href="/docs/en/guidelines/meta/reinstatements.html">reinstatements</a> for their category node.</li></ol> <p>Although initially CatMod had a 6-month term limit, it has been extended to a more permanent permission, although it can still be revoked (e.g. for non-use) or changed to Meta at any time by Admin consensus. CatMod is not normally granted for more than one category node at a time.</p> <p>Since the CatMod has many of the same privileges as the Editall and Meta, much of the text below are direct excerpts from the <a href="/docs/en/guidelines/editall/">Editall</a> and <a href="/docs/en/guidelines/meta/">Meta</a> Guidelines. It would be helpful to read those Guidelines in full to give you an overview of their responsibilities, and how the duties of a CatMod relate to those of the other positions of leadership in Curlie.</p> <h2 id="newcat">New Category Permissions</h2> <p>CatMods have the ability to access the New Category Permissions (new perms) queue. However, their access and ability to process applications is limited to their specific category node and below. For instance, an Arts/ CatMod can only view applications submitted for an Arts/ category. We expect CatMods to have an excellent grasp of their fellow category editors, as well as the special issues and needs of certain categories, and will rely on their expertise to make good decisions in processing newperms.<br /> Below is the guideline for New Category Permissions, adapted from the <a href="/docs/en/guidelines/meta/">Meta Guidelines</a>:</p> <p>Be judicious about who you approve for new permissions. Remember, it is very labor intensive to clean up after a bad editor, so it is important to keep these things in mind when evaluating a new permissions applicant:</p><ol> <li>Check to see how many active editors are in the category the applicant wants to edit. There may be enough active editors already.</li> <li>Look at the applicant's Total Edits - unique adds and deletes. Unique adds show a commitment to growing the directory.</li> <li>Check for recent activity.</li> <li>Review a few of the edits. <ul><li>Are the titles and descriptions clean?</li> <li>Have the sub categories the editor has created been logical?</li> <li>Should the editor have a business interest in the category, do they look to be doing a fair and unbiased build out of content?</li> <li>Are the sites in their category appropriate for the category?</li> <li>Have they marked their own site as cool?</li> </ul></li> <li>Check out the date the editor first joined <abbr title="or DMOZ or ODP">Curlie</abbr>.</li> <li>Are there any profile notes that indicate past abuse, poor editing, etc. <strong>or</strong> positive notes indicating outstanding work?</li> <li>If you are unsure of the applicant, there are a couple of things you can try. Check to see if there have been any problems with this editor by reviewing the forums and communicating with other Category Moderators, Editalls, and Metas. Look at the applicant's previous requests. In some cases another CatMod or Meta may have rejected them, and you can thus follow up and find out why, particularly if it isn't evident from the notes.</li></ol> <h2 id="forum">Joint Meta Forum</h2> <p>This forum was initially created as a place to house discussions between the classic Curlie Metas and the Kids & Teens Metas. Many of the issues pertain to editor discussions and issues that overlap the entire directory. As a CatMod, it is important to have access to these discussions, especially when processing newperms. <a href="http://curlie.org/forum/viewforum.php?f=127">Joint Meta</a> should be your primary area to discuss any difficult issues regarding editors with the Meta community. Most likely, a Meta will be able to guide you in the right direction, or the Meta community will be able to provide a consensus when a decision needs to be made. All reports of editor abuse should also be posted in Joint Meta.</p> <h2 id="abuse">Abuse</h2> <p>Unfortunately, part of keeping the directory clean and running smoothly means that you will uncover abuse from time to time. Although CatMods do not have the ability to remove editor permissions, they can issue a formal warning to an editor about their abusive editing and/or report the editor in the Joint Meta forum where the Meta community may decide to take further action against the editor. Catmods can participate fully (including voting when applicable) in discussions as long as the permissions of the editor concerned are within the node of the directory that the CatMod oversees. CatMods can also investigate abuse reports, but should only do so in cases that affect editors or categories within their node. If matters addressed in the abuse report (or uncovered in investigating the report) extend outside the boundaries of a CatMod's node, the CatMod should relinquish the "Investigator" role and alert a meta to the situation.<br />Below is an adaptation of the <a href="/docs/en/guidelines/meta/abuse.html">abuse section of the Meta Guidelines</a>:</p> <p>As a Category Moderator, you will undoubtedly come across instances of bad editing and potential editor abuse. In cases where an editor is not following the guidelines, you should use <a href="/docs/en/flag.html#guidance">editor guidance flags</a> which enable editors including CatMods to leave helpful comments on individual listings for other editors to see. Pink in color, they work best where active editing is taking place, and for less important issues; otherwise feedback or use of the <a href="/docs/en/guidelines/meta/features.html">Warning feature</a> to send a documented notice to the editor may be more appropriate. <br /> Keep in mind that we are all human, and some editors are not as active, and aware of Curlie culture as others. Please be diplomatic and courteous in your approach. Make sure you give the editor sufficient time to correct any mistakes.</p> <p>Here are some examples of the kinds of abuse you might run into:</p> <dl> <dt>General Bad Editing</dt> <dd>Poor editing differs from abuse, in that, there is no intent to cause harm to the directory. In these cases, if the editor continues to edit poorly, you may wish to send another email, or consider starting a thread to discuss partial (or full) category removal, allowing the editor a few categories to improve their edits.</dd> <dt>Guideline Abuse</dt> <dd>If an editor has been warned and continues to disregard the guidelines, this is considered abuse. Here are a few examples of guideline abuse: repeated self-cooling, manipulating titles/descriptions to favor their own site, deleting competitors' sites, and creating vanity categories.</dd> <dt>Extreme Abuse</dt> <dd>In the event of an editor doing immediate and serious damage to the directory, or violating forum communication and privacy guidelines in the most egregious way possible, the Meta community should be notified via the Joint Meta forum. Admins should also be contacted and referred to the appropriate thread. Immediate damage to the directory generally refers to an editor who is mass-deleting sites or mass-spamming the directory and/or the forums, but can refer to any situation where serious damage is in progress.</dd> <dt>Other Violations</dt> <dd>Editors who cannot work with others in a team, and make editing an uncomfortable experience for co-editors should also be reported in the Joint Meta forum. This includes flaming other editors, submitters, or the administration. Violating the confidentiality of the forums or editor notes is also unacceptable. These kinds of violations apply to editors of all levels. Admins should be consulted only as a last resort when every attempt at a resolution has been made.</dd> <dt>Notes</dt> <dd>The Notes feature is a tool that allows you to jot down notes about editors directly on their profile page. This is especially helpful when a good or bad editor ends up in the newperms queue - their name will appear in the corresponding color code that you choose when leaving a note.</dd> </dl> <h2 id="editallcatmv">Category Editall/Catmv Features</h2> <p>Category Moderators also have Editall-like abilities, but limited to their category branch. As with any major move, you should have the support of the community before proceeding to make any significant changes to the directory's taxonomy. Smaller changes can be made with the consultation of any individual editors in the affected categories.<br /> Below is the text regarding the procedures for Editall/Catmv, adapted from the <a href="/docs/en/guidelines/editall/">Editall Guidelines</a>:</p> <dl> <dt>Overview</dt> <dd>Category Moderators are able to do a number of different things for which a standard edit login won't allow. Following are a list of the basic permissions a CatMod has:<ol> <li>Move a category within their category branch</li> <li>Rename any category in their branch</li> <li>Delete any category in their branch if <strong>all</strong> the sites have been removed</li> <li>Move/Rename @links in their branch</li> <li>Create a new category in their branch and list up to one editor as editor</li></ol> </dd></dl> <div class="footer"> Last update:  Tue Sep 17 11:45 EDT 2024 <br /> Copyright © 2024 Curlie.org (<a href="/docs/en/termsofuse.html">Terms of Use</a> - <a href="/docs/en/license.html">License</a>) </div> </body> </html>