| suggestion to fellow moderators re: duplicate posts [message #243752] |
Fri, 08 June 2007 15:00  |
 |
Barbara Boehmer
Messages: 9102
Registered: November 2002
Location: California, USA
|
Senior Member |
|
|
I seem to recall one or more moderators requesting guidelines and/or discussion of how to handle various things. I have noticed duplicate posts being handled in various ways and thought I would offer my advice on the issue of duplicate posts and see what the rest of you think.
As I see it, the object is to clear the clutter and prevent future clutter, by notifying the poster either by pm or within the thread not to do that. When I notice duplicate posts, I usually click on the user and check for their other messages to see if there are triplicate and quadruplicate posts and so on. For duplicate posts that have not been responded to, I delete them, using the method that includes the option to notify the original poster with a copy and an explanation. If the posts have already been responded to, then I merge them, changing the title to indicate the number of merged threads. The poster can then be notified by pm or within the thread if a responder has not already done so.
I see that some newer moderators are locking the duplicate threads, rather than deleting or merging. This does not clear the clutter and people browsing the forums end up still wasting time clicking on duplicate threads and reading them. I am glad to see the newer moderators eagerly contributing and locking is better than nothing, but I would prefer deleting or merging. What do the rest of you think?
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Re: suggestion to fellow moderators re: duplicate posts [message #259973 is a reply to message #259920] |
Fri, 17 August 2007 01:15  |
 |
Maaher
Messages: 7065
Registered: December 2001
|
Senior Member |
|
|
Ok, just to be clear:
- merge duplicates, leaving the oldest on top.
- delete unresponded duplicates AFTER THE MERGE.
Here's a thought: when a moderator is about to move/merge/delete/lock, can't he report the message? That way other moderators can see what he/she is up to. Afterwards the report can be deleted. That should avoid mistakes, doesn't it?
MHE
[Updated on: Fri, 17 August 2007 01:15] Report message to a moderator |
|
|
|
| Re: suggestion to fellow moderators re: duplicate posts [message #259980 is a reply to message #259973] |
Fri, 17 August 2007 01:31 |
 |
Michel Cadot
Messages: 68729
Registered: March 2007
Location: Saint-Maur, France, https...
|
Senior Member
Account Moderator |
|
|
| Quote: | when a moderator is about to move/merge/delete/lock, can't he report the message?
|
I don't think this will prevent from errors.
Just a few thoughts.
You have to refresh the page to see there is a reported message, and during the "move/delete/lock/..." process you don't refresh, you see the refreshed page after.
On the opposite, if you refresh before executing your action and someone else did it then you see the result and don't execute your action.
The question is: what is faster reporting or doing the action? I only see "merge" that is slighty slower.
The main problem is when you want to execute complex action like "move + merge".
In addition, we will have then many reported messages, the time you read all these messages to see nobody reported the same you want to report, maybe someone reported the message.
...
Regards
Michel
|
|
|
|
|
|
) 1 Vote
] 
Blog
Search
Help
Members
Register
Login
Home
