Posting Guidelines |
WHAT'S GOOD
WHAT'S NOT GOOD
WHAT'S NOT CONSIDERED
THE PURPOSE of POSTING GUIDELINES
HOW THE POSTING GUIDELINES ARE APPLIED Reports by Regular Member are held for moderation, which amounts to my reviewing each report for adherence to the Posting Guidelines. Senior Members have already demonstrated their willingness to follow the Posting Guidelines, and thus I don't need to monitor their contributions. This is the intent behind the Regular Member / Senior Member System. As a side note, I must also observe here that there are a number of Senior Members who were grandfathered into the status, but who still insist on making contributions that don't follow these Posting Guidelines, mostly by writing in chat room style with no capital letters or punctuation. Of course, these Senior Members make it doubly difficult for me to maintain the minimum requirements of the Posting Guidelines among the Regular Members, many of whom will naturally mimic the writing style they see utilized by the Senior Members under the assumption that this represents the acceptable practice. I'll have a discussion on this subject in the future, for now I'm going to focus on one issue at a time. The moderation process is somewhat time consuming. On any given day, approximately 70% of the pending reports are fine as submitted, but there's the other 30% that need to be edited, either because they are written in chat room style, or written in ALL CAPS, or with weird punctuation (see description below), or because they constitute SPAM, etc. Each day, I go through each of these reports and make the necessary edits, and then I paste an "Editor's Note" at the bottom of the edited report to advise the author what and why I was compelled to edit, hopefully to avoid repeats of the same situation. I also post the Editor's Note so I can keep track of whose reports I have had to edit, so if the author requests an upgrade to Senior Member, I can look back and see their history. Otherwise, as I am reviewing a prospective Senior Member's report history, every report would look perfect because I had fixed them. I try to be somewhat moderate in deciding at which point I will paste an Editor's Note in a report. Generally, I don't even bother for just a few mistakes because everybody makes typo's, so it's only the pattern mistakes that warrant a notice. I'm also more liberal when it comes to correcting reports from members who are reporting on international locations when it appears that English is not their native language. In these cases I'm sensitive to my own limited foreign language capabilities, and I certainly don't want to discourage these contributions. In the beginning of my stewardship of the Forum, I would send a email to the author of a problem report, either describing how I had to edit their report, or sometimes providing them with a copy of the entire report and a request that they modify it themselves and re-post it. However, that became too cumbersome because so many of these emails either wouldn't be received because it was a mail box that the member would rarely check, or would be returned undelivered because the email address that the member had used to register their membership was no longer valid. To this day I am amazed at the number of people who won't provide me with a useable email address, in spite of the fact that I've never distributed the membership email list or spammed the members. Maintaining a valid email address is a membership requirement, but I'll deal with this issue on another day. Another problem that requires editing work on a daily basis is the misuse of the Forum's Quote function. Apparently there are a lot of people who simply don't comprehend the correct positioning of the [quote] and [/quote] tags, which results in several reports every day that look like one big quote, or that have been rendered completely unreadable. It's an aggravation to me because I then have to read the actual report content in an attempt to discern where the actual quote ends, and then move the improperly positioned tag to the correct location. I'm giving serious thought to removing the function entirely, but I'll make it a subject of a future discussion first. |