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 Administrator 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/de/guidelines/admin/">Deutsch - German</a></li> <li><a href="/docs/fr/guidelines/admin/">Fran莽ais - French</a></li> </ul> </div> <div id="mainContent"> <h1>Administrator Guidelines</h1> <ul class="toc"> <li><a href="#abilities">Abilities</a></li> <li><a href="#individual">Individual Expectations</a></li> <li><a href="#group">Administrator Group Expectations</a></li> <li><a href="#responsibilities">Group Responsibilities</a></li> </ul> <p>Administrators (Admins) are responsible for project management of the Curlie Directory. This includes all aspects of the project.</p> <h2 id="abilities">Abilities</h2> <p>Admins have access to the same set of tools and resources as those with Root privileges. This includes all tools and privileges available to (k)meta editors, as well as the ability to:</p><ul> <li>Grant/revoke/remove/reinstate (k)cateditall+ permissions.</li> <li>Make changes to the public interface.</li> <li>Create and modify submission policies, editing guidelines, and other documentation on curlie.org.</li> <li>Create and change the dashboard message.</li> <li>Oversee editorial activities and community governance/engagement.</li> <li>Upload modified language strings.</li> <li>Moderate the editor forums.</li> </ul> <h2 id="individual">Individual Expectations</h2> <p>Each individual Administrator is expected to:</p><ul> <li>Actively participate in the functioning of the Admin group. In addition, administrators should be visible in discussion forums and editing activities. If time constraints do not allow an active level of participation for an extended period of time, the individual is expected to resign from their Admin privileges.</li> <li>Act according to group consensus, often following discussion, and support group decisions.</li> <li>Act and communicate in a professional and objective manner at all times. Administrators should adhere to the highest standards.</li> </ul> <p>Failure to satisfy these expectation will result in the removal of Admin privileges.</p> <h2 id="group">Administrator Group Expectations</h2> <p>As a group, Administrators are expected to:</p><ul> <li>Take an active, visible role in managing the project.</li> <li>Communicate a shared philosophy and vision of the directory to internal and external parties.</li> <li>Work with editors of all levels to ensure that quality standards are being met in terms of editing, ontology, and community management.</li> <li>Evaluate and implement innovative proposals designed to improve the directory.</li> <li>Encourage self-regulation at all levels, but resolve escalating contentious issues when necessary.</li> </ul> <h2 id="responsibilities">Group Responsibilities</h2> <p>Each Admin has a primary area of responsibility. This helps promote specialization, ensure that all key areas receive the necessary focus, and provide clear points of contact for the community. It does not, however, preclude any Administrator from participating in other activities. In fact, Administrators are encouraged to participate in all activities, as their interests, abilities, and time allow.</p> <p>The focus areas are:</p> <ul> <li><strong>Technical Administration</strong> <ul> <li>Work with technicians to address operations issues, and software bugs and features.</li> <li>Editor produced tools and cooperative initiatives.</li> <li>Management of the DevId system.</li> <li>Internationalization/Localization issues.</li> </ul></li> <li><strong>Community Administration</strong> <ul> <li>Cateditall+ promotions and editor application oversight.</li> <li>Reinstatements oversight.</li> <li>Abuse report oversight.</li> <li>Work with metas on editor-specific issues and community management concerns.</li> <li>Monitor forums for escalating issues, etc.</li> <li>Ensure that editors' communications are civil and polite.</li> </ul></li> <li><strong>Editorial Administration</strong> <ul> <li>Oversight of taxonomy and ontology.</li> <li>Oversight of directory quality.</li> <li>Monitor initiatives aimed to improve directory organization and data quality.</li> </ul></li> <li><strong>Marketing / Product Management</strong> <ul> <li>Public Relations.</li> <li>Documentation on curlie.org.</li> </ul></li> </ul> <div class="footer"> Last update:  Tue Sep 17 11:53 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>