User:Raidarr/Admin guide

A staff guide covering general topics for staff to know. You don't have to memorize this, check sections as needed or curious and feel free to suggest new things to add.

All staff

Import page and merge with a copy + paste

This is useful to get the complete history of a page as it was originally written. Several steps are needed to do it correctly. But because of this process, people can simply 'paste' a page and then a history with a notice to attribute the original content, and the full history can be added in later.

1. Import the original page into a temporary place. This is critical. Do not overwrite the live page yet. This is done with Special:Import.
   • Check this box: "Assign edits to local users where the named user exists locally".
   • I suggest you import as subpages to your inbox. If it's a handful of pages you can keep track with the Special:PrefixIndex tool.
2. Merge the live page into the imported page. This is using Special:MergeHistory (use it carefully). The source page is the copy pasted page that exists. The destination is the page in your sandbox.
3. When complete, move the page from sandbox to where it belongs.

Deleting templates and moving categories

In both cases it's not this simple. Templates and categories are not changed on the pages they are part of. To delete a template it must also be removed from every page its used. Likewise the category must be removed or replaced on every page that uses it.

Handling user rights

User rights are managed at Special:UserRights.

Confirmed is a temporary right to reduce inconvenience while trusted users meet the 10 edit 4 days requirement. It should only be permanent if the user will not reach 10 edits anytime soon.

Bot is not something to worry about unless you already know about it and there is a clear need.

Autopatrolled is a mark of trust for strong editing and good behavior. It should be assigned with care as it has a few abilities most users don't get. Moderators are able to remove AP from misbehaved users, but admins make the choice initially.

Moderators help keep the wiki clean. Most staff should have this unless they have a clear need to use other rights and they have the required skills + maturity. This replaces autopatrolled, because moderator is autopatrolled + tools to help manage things like protection, deletion and blocks. Ensure they have browsed at least this guide before giving them the right.

Administrators have extremely broad access, which is why it should be given very carefully. Admins should set an example and correct issues moderators may have, and deal with technical issues short of managewiki. Any major decision should be discussed with fellow admins and even moderators so everyone knows what is going on. This replaces Moderator and/or Autopatrolled.

Bureaucrats have the most sensitive access, with managewiki and the ability to manage admins. Generally, only Original Authority can remove them. They have the highest expectation and need to be the ones with a plan for the wiki's future if not the rest of the admins. A new bureaucrat should generally be approved by the entire admin team if available. This is added to the administrator right.

Warnings and blocks

Per the rules, a warning should be issued first if possible. If the issue is serious like vandalism, you can proceed to a block. If it's a new user clearly here to vandalize or post shock content etc, perma block (but avoid uncivil commentary in your block reason, just get rid of them).

Do this carefully. Do not block unless it's clear the user is not going to listen; you can try a short block as a warning shot. When you can say you've given them chances and they don't listen, block. Let admins+ deal with users who've contributed but are drama cases, but feel free to give them a short block if they're on a rampage. Know that users have the right to appeal on the QP:SN if they are able, or on their talk page. These should be reviewed by admins only.

A new mod recently asked about when and how to warn. This was my advice:

This is a good question, here are some things to keep in mind.

If you're at all unsure just run a sanction by a fellow mod or even me for a second opinion. See if the action has to happen now, or if it can wait for that extra opinion. The second is best where possible.

If it's not then I'll give you some common issues.

[section moved below]

Excessively uncivil comments or comment spam should be removed with a warning.

A common problem is people putting unfinished pages in mainspace. These should be moved to a user's personal space (User:Username/sandbox/Pagename) without a redirect. Unless the page has nothing on it, would never be accepted even if complete, or is truly nonsense, it shouldn't be deleted and a full-on warning isn't needed. If it's an opinionated piece but decently written, you have the option to move it to their User Blog space instead (User Blog:Username/Pagename). Where possible please do not create redirects, you can politely remind people of this if they do it often. They should only be left for clear connections to a page's title.

Excessive use of colors, caps, bolding should be removed and if you catch it quick enough you can remind people to please avoid this in mainspace articles.

If people are arguing about keeping a pointer or not, this is an approach I prefer: if it can be sourced it can probably stand, if no proper source exists it can be challenged and removed.

Making pages positive or negative is a point of controversy that's going to have to be discussed. If you have discord feel free to join it since I will be fielding this conversation there first, but it will come to the wiki in time. I prefer to say, put positive sections first if overall reception from aggregates (imdb, RT, metacritic) is over 60%. I do not believe youtube commentary should affect this, they are best used to reinforce pointers. I'd get someone more senior if this becomes a problem you have to deal with and you get pushback.

In general if it's something quick and easy you can just do it, warning should come if it's repeated or a relatively serious case (unacceptable page for the wiki even with revision, multiple pages that need to be sandboxed, incivility and such). A short block should happen if warnings have been ignored/the offense repeated. If people disagree with your handling they should be pointed to an admin or straight to me to look it over. Fire at will of course for vandalism, spam, overt trolling and such.

Deleting inadequate pages

If possible, move an unfinished page to the creator's sandbox for them to figure it out. If it has no clear author, they've been inactive a long time or there's virtually nothing on the page, delete.

Eliminate redirects that are fixing typos, and don't make a redirect when moving from the mainspace into a sandbox or blog space. I suggest you don't leave a redirect from your userspace to the mainspace when finishing a page either - it will never be used but it will be forgotten and clutter the wiki.

Featuring pages

Mods can feature pages at will. Keep in mind the comment at the top regarding not adding too many - ideally, replace existing ones to keep them fresh. Prioritize pages with all sections completed, at least some sources, decent logic. Try to keep the flair text short.

Handling a dispute

In an active edit war (more than 3 back and forth reverts), what needs to happen is that editing stops - revert to last uncontroversial change, message both parties to work it out on the talk page. You can use temporary protection to enforce this if needed. Whatever the issue is, have the conflicting users put up their case: this is how to resolve it, not additional reverts. Unless it's directly enforcing a rule you should take this approach yourself if a regular user disagrees with you and have someone else mediate. If the answer isn't obvious you can forward to an admin from there. Your job here is to mediate - choose the outcome that is closest to what the rules are and/or staff in general agree on, and if something isn't clear lets work it out in staff so it can be handled better next time. Don't hesitate to raise the issue in the staff discord channel if you're there.

Admin+

Editing the wiki style

Do this with care. If you don't have Raidarr's experience you should work with someone like him or Original Authority to make changes.

Most cosmetic changes are done with the skin's css file, for example, MediaWiki:Vector.css. Note that the mobile skin has a different file. Test changes in your userspace before publishing them live to reduce issues. Keep in mind that changes to MW files are not instant, it takes a minute to apply. Other changes such as tweaks to make extensions behave are found in MediaWiki:Common.css. These apply regardless of the skin in use. Inspect Element is your friend but be careful how you select elements: they can be tricky and you need a just-right spot of selecting the right thing, but making sure that's what you really want. Selecting a single link, vs changing all related links, vs changing all links. Look up w3schools and get to know both HTML and CSS if you are interested in wiki styling.

Bugs and other issues

Original Authority is very responsive and can deal with interface errors. Admins should be able to deal with simple complaints, like a styling problem or error on a major page. Bureaucrats can play with ManageWiki and deal with issues there, carefully. Problems should go like this: admins take a look -> passed to bureaucrats if necessary -> passed to Original Authority by bureaucrats. OA should not have to step in for issues the wiki can deal with locally. Check with experienced admins to see who should take a look first.

Editing the sidebar

This wiki uses GroupsSidebar. The basic sidebar is edited through MediaWiki:Sidebar, but certain sections exist for users and for staff. For users this will be MediaWiki:Sidebar-user including community links and editing help. For staff these are MediaWiki:Sidebar-moderator and MediaWiki:Sidebar-sysop. These include resources to help staff learn new tricks and do things consistently.