· Can artificially inflate the importance of an issue.
· Can negatively impact searching results as the importance becomes artificially inflated.
· Will artificially skew some metrics in terms of threads, posts, views, etc.
· May indicate the presence of SPAM.
As explained in the article on Managing Posts and Threads: Merging Threads, true duplicates by the same user in the same forum can be collapsed into a single thread:
Duplicate Posts in Multiple Forums
Figure 1: Reference to Another Post
1. The problem should be solved where the problem should actually live. In this scenario, A Visual Studio 2008 post should be discussed on MSDN. However, since the issue is already discussed on MSDN without much success, we don’t want to simply move the thread to MSDN. That would leave the customer with a bad experience.
2. Escalate the issue to a forum owner or the private moderator forum to help gain traction where the thread lives (MSDN).
3. Once a response is given where the thread lives, the thread is now effectively “owned” by the other property.
4. Notify users of the thread being discussed in the incorrect place (Microsoft Answers) that the thread is now being handled correctly and that the thread will be locked for one week and then deleted after that.
5. Immediately lock the thread.
6. Delete the thread after one week.
yottun8 edited Revision 7. Comment: Added "Other Languages" and ja-JP version.
Karl Mitschke edited Revision 6. Comment: Modified figure number, copied image back in from original version of the article.
Zoltán Horváth edited Revision 5. Comment: Replaced the first sentence, just not to start a page with "back to". Tagging.
More information about what to do with duplicate posts is available in the topic on Merging Threads at social.technet.microsoft.com/.../forum-moderation-guide-managing-posts-and-threads-merging-threads.aspx
Please confirm under what circumstances community moderators in Answers permitted to delete OPs.