Admin tools

[George]

We need some basic community management tools in place.

In addition to the new Admin Dashboard page, we need a slightly more detailed view on our patrons and anonymous editors, and some tools to help keep things under control.

* All Admin pages should only be accessible to the Staff usergroup

1. ADMIN HOME

Here's the mock-up of the Admin page:
http://home.us.archive.org/~larthur/admin.html

* It's main purpose is to give us an overview of activity on Open Library, and show trends over time at a glance.
* Should display a graph of the number of edits per day (or, a count at least)
* Should differentiate between human & bot edits, logged-in humans & not-logged in humans
* Similarly, for new accounts, display a count of new accounts created per day, ideally in graph form as well
* Time frames for comparison should be All Time, Last Month, Last Week, Yesterday, Today
* Would be very nice if a % change could be calculated and displayed too.
* We need a way to see often-edited items, because chances are, that's where the action is
   * If a page has been edited more than 3 times in the last hour, it should show up on a list on this page, with a link to the page in question, and perhaps a note of the last edit and editor.
* Would be good to show Raj's Unique IP graph on this page too, just so we don't have to look in 2 places
* We should move edition/full text counts from current home page to this page. Having those numbers on the home page is a bit weird, and was only set up for Brewster, afaik. We can have him look here instead.

2. PATRONS

Here's the mock: http://home.us.archive.org/~georgeo/upstream/admin-patrons.html

* A more detailed list of patron activity, both logged in and anonymous
* 2 lists:
   1. New accounts. Display, say 50. Show timestamp for creation, username, email address, link to public profile, link to Admin view and a count of # of edits so far.
   2. Recent Changes. Just the same list as you can see on http://upstream.openlibrary.org/recentchanges except links point to Admin view

3. PATRON ADMIN VIEW

Here's the mock: http://home.us.archive.org/~georgeo/upstream/admin-patrons-patron.html

Need a way to provide support to people and take control of unruly users.

* Show minimal account config information: username, last login, email address, IP, list of edits
* Provide a way to change email address (for support)
* Provide a way to reset password (for support)
* Provide a way to block User's IP address. (Not clear to me what the effect of this is from the user perspective.) Should include "Are You Sure?" alert before complying. If user's IP has been blocked, we need a note here to that effect.
  * Can a user page have an ADMIN history??
* Need a way to delete a user account. This should definitely be noted in an account's history.

Nice To Have:
* Links from www.openlibrary through to this Admin View. Links must only show up for usergroup = staff
* A search box you could use to find a username. Links go to 3. PATRON ADMIN page.

[George (george-archive)]

Re: Unique IPs

The numbers are uploaded here every day:
http://www.archive.org/details/stats

They are in a file called numUniqueIPsOL.sqlite. direct link to this file:
http://www.archive.org/download/stats/numUniqueIPsOL.sqlite

If you have a hard time dealing with the sqlite db, you can convert it to text using this code:
http://home.us.archive.org/~rkumar/git/gitweb.cgi?p=stats/.git;a=blob;f=sqlite2txt.py;hb=HEAD

Hope that helps!
-raj

[George (george-archive)]

Hey. Not sure why I did the layout this way initially, but, now that I see it, the order of columns in the Members table on http://upstream.openlibrary.org/admin should be reversed, so they start at "Today" and end with "All Time".

[George (george-archive)]

Priority is low, as long as Stats Bot is still chugging away.

* Grand totals in the tables aren't updating.
* Flickr API call is busted

[George (george-archive)]

Anand - as we approach the soft launch, having these Admin Tools in place moves up the priority chain.

I'd like you to work on the first iteration of these tools as soon as possible.

To begin, we need the ability to:
1. BAN AN IP ADDRESS from making any more edits, and ideally
2. REVERT ALL EDITS per IP

- If someone comes to the site with a banned IP address, the EDIT button should either not work, or be hidden
- Reverting all edits should revert back to the last edit not made by that IP

Case in point: http://upstream.openlibrary.org/recentchanges?ip=87.101.146.203

It would be most convenient if ADMINS ONLY could see these two options as buttons on the Recent Changes by IP page, as per the attached mockup. We should probably add an Are You Sure check as well.

[George (george-archive)]

And:

- Consider making these admin actions detached from Admin performing the action. IE, make the history note read "Adminstrator" instead of George, and don't show these Admin tasks on George's page. (Could make staff a target for trouble.)

[George (george-archive)]

it would also be good if reversions set at this level (all reverted by administrators) didn't appear in the Around the Library chunk at the bottom. Draws unnecessary attention to problematic edits.

[Anand Chitipothu (anandology)]

Added code to hide reverts from around-the-library.

Implemented minimal support for blocking IP Addresses.

http://upstream.openlibrary.org/admin/block

Block your IP address and try to edit any book to test this.

[George (george-archive)]

Block IP should not show up in Recent Changes. Even though the /admin/block page is permission-controlled, the fact that we block IPs should not be public knowledge.

Anand - when can you complete this as spec'd ?

[Anand Chitipothu (anandology)]

On 25-Mar-10, at 12:59 AM, George wrote:

> Block IP should not show up in Recent Changes. Even though the
> /admin/block page is permission-controlled, the fact that we block IPs
> should not be public knowledge.

As I mentioned earlier, the backend was designed to keep everything
world-readable.

For now, I changed the recentchanges template to hide add /admin/
changes.

[Lance Arthur (lance-arthur)]

I don't think block IPs is working, at least in this case:
http://upstream.openlibrary.org/recentchanges?ip=65.242.84.75

I blocked that IP on Wednesday, and on Friday he/she was still at it.

[George (george-archive)]

Anand - pls make this your critical bug.

[Edward Betts (edwardbetts)]

IPs are blocked on upstream, not yet on production.

[George (george-archive)]

Argh. Thanks for the pointer, Edward. The sooner we can transition to WWW, the better!

[George (george-archive)]

IP Blocking requirements:

- add wildcard IPs, like 202.23.56.*

CAPTCHA

- only to anonymous edits
- add captcha to any pages edited anonymously 3 times in the last 8 hours