Mailing List Archive

Log page code consolidated
While I'm at it; I've consolidated the log page handling for the upload
and deletion logs into a LogPage class.

This should make it easier to add more logs of things that are currently
hard to track -- page protections/unprotections, ip blocks and unblocks,
etc.

But before doing that; would it be more worthwhile to use some kind of
event log table instead, from which the logs could be extracted through
simple filtering? Or is using wiki pages which sysops can correct,
rotate, and backup through the regular editing tools better?

-- brion vibber (brion @ pobox.com)
Re: Log page code consolidated [ In reply to ]
On Sunday 15 December 2002 12:00 pm, wikitech-l-request@wikipedia.org wrote:
> But before doing that; would it be more worthwhile to use some kind of
> event log table instead, from which the logs could be extracted through
> simple filtering? Or is using wiki pages which sysops can correct,
> rotate, and backup through the regular editing tools better?
>
> -- brion vibber (brion @ pobox.com)

Well it has been nice to be able to edit the logs. Both you and I have made
the logs more useful by adding header information, timestamps and links. I've
also been doing monthly archives of the deletion log and have been tracking
the the number of monthly edits (we are in a downward trend). So I favor the
current way of doing things.

BTW, would it be possible to make logs only appear once in Recent Changes
instead of appearing each and every time a file is uploaded or pages are
deleted? Many sysops often delete pages in chunks and many users upload files
in batches. This leads to the creation of a lot of noise in Recent Changes
(esp. for uploads since each upload generates two entries in RC). No biggie,
but if it can be done easily it would be nice.

--Daniel Mayer (aka mav)
Re: Re: Log page code consolidated [ In reply to ]
On Sun, 2002-12-15 at 15:13, Daniel Mayer wrote:
> On Sunday 15 December 2002 12:00 pm, Brion Vibber wrote:
> > But before doing that; would it be more worthwhile to use some kind of
> > event log table instead, from which the logs could be extracted through
> > simple filtering? Or is using wiki pages which sysops can correct,
> > rotate, and backup through the regular editing tools better?
>
> Well it has been nice to be able to edit the logs. Both you and I have made
> the logs more useful by adding header information, timestamps and links. I've
> also been doing monthly archives of the deletion log and have been tracking
> the the number of monthly edits (we are in a downward trend). So I favor the
> current way of doing things.

Header text of logs, like the Recentchanges header text, could be
editable separately.

Monthly archives are useful because the page gets too long to load
comfortably; an event log table could be displayed in chunks of
arbitrary size, and one could jump back to arbitrary time periods,
obviating the need for manual cut-n-paste.

A table would also make it very easy to generate statistics.

And, the logs could be somewhat language independent; if we recombine
the image upload space for instance, the upload log should have to show
all files for all languages. Local date/time format and "uploaded"/
"deleted"/"banned"/"restored"/etc would be nice.

> BTW, would it be possible to make logs only appear once in Recent Changes
> instead of appearing each and every time a file is uploaded or pages are
> deleted? Many sysops often delete pages in chunks and many users upload files
> in batches. This leads to the creation of a lot of noise in Recent Changes
> (esp. for uploads since each upload generates two entries in RC). No biggie,
> but if it can be done easily it would be nice.

I'd say the same of pages in general -- I don't want to see half my RC
taken up by [[Richard Wagner]]. ;) But at the same time I want the
information accessable... since the page history doesn't behave quite
the same on log pages as on regular pages (many automatic additions show
up in one 'revision'), the only way to tell whether one or a hundred
pages have been deleted would be to load the (too long for modem user)
log file and check the times of the previous entries.

Erik's dynamic unfolding suggestion would be helpful here. (I've enabled
the dynamic threading on my Kuro5hin account, and it's *wonderful*. If
we can do something like that cleanly for recentchanges, that'd be
awesome.)

-- brion vibber (brion @ pobox.com)
Re: Log page code consolidated [ In reply to ]
Brion Vibber wrote in part:

>Header text of logs, like the Recentchanges header text, could be
>editable separately.

Speaking of which, why isn't the header text of special pages
editable with the normal wiki user interface?
When I first found Project Sourceberg,
I thought that it was so neat that I could edit its Recent changes!
(Of course, we'll need [[Special talk:]] to go with this.)


-- Toby