Skip to main content
expanded question
Source Link
douggro
  • 2.6k
  • 11
  • 3

While I realize that dealing with duplicate questions is probably a tedious, time-consuming overhead issue for Moderators, I'm wondering if there can't be a better way of handling them rather than the simple

possible duplicate of …[link to dupe question]

Most of the time, this happens to new users posting their first question, and on the face of it, it seems rather a condescending way to handle it. Granted, the user probably invested no time in researching their problem before posting. And if it truly is a dupe question, it'll get flagged and closed as such at some point, which is as it should be.

So perhaps a more expansive explanation of why it may be a dupe and some hints on how to deal with it might be a more "Friendly AU" method of dealing with it.

Your question appears to be a duplicate of this question [link to dupe question].
Please investigate the answer(s) provided there. If those do not seem to apply to
your situation or don't resolve the issue, edit and expand your question with
details as to what differentiates your issue from the other question. Duplicate
questions are subject to being closed.

A simple boilerplate like this could be used that is more informative and helpful to the user resolving the issue, and how to deal with it if the suggested dupe doesn't shed results on the problem.

EDIT / EXPANSION

Following Eliah Kagan's expansive (and very helpful) answer, here's the real meat of the source of what is behind this question:

Take yourself out of the context of Moderator / Admin / Seasoned Ubuntu User. How does the possible duplicate of … response occur to the user? Get over in their seat and think about how getting that communication is going to land with you. What are you getting from it? What does it leave you with?

If there's any chance that the response occurred as dismissive or rude, then it is exactly that, regardless of what postfacto-spin or rationalization we try to put on it.

I'm no noob when it comes to AU and online forums/discussion boards - I've been doing this for over 20 years. I've been a Mod/Sysop. I get that dealing with users who don't exercise any due-diligence in researching their problem for solutions can be like dealing with four-year-olds who expect an answer right now. And still, with that experience under my belt, when I see the possible duplicate of… comment, I get left with it being somewhat dismissive.

Now, I'm all for having short, succinct responses, for some of the very reasons Eliah pointed out (keeps things small and readable). But if there's the possibility of expanding a response to provide just enough additional information to help the user, then I think that it's worth it. If the system isn't set up to allow for it, then I think that needs to be looked at.

While I realize that dealing with duplicate questions is probably a tedious, time-consuming overhead issue for Moderators, I'm wondering if there can't be a better way of handling them rather than the simple

possible duplicate of …[link to dupe question]

Most of the time, this happens to new users posting their first question, and on the face of it, it seems rather a condescending way to handle it. Granted, the user probably invested no time in researching their problem before posting. And if it truly is a dupe question, it'll get flagged and closed as such at some point, which is as it should be.

So perhaps a more expansive explanation of why it may be a dupe and some hints on how to deal with it might be a more "Friendly AU" method of dealing with it.

Your question appears to be a duplicate of this question [link to dupe question].
Please investigate the answer(s) provided there. If those do not seem to apply to
your situation or don't resolve the issue, edit and expand your question with
details as to what differentiates your issue from the other question. Duplicate
questions are subject to being closed.

A simple boilerplate like this could be used that is more informative and helpful to the user resolving the issue, and how to deal with it if the suggested dupe doesn't shed results on the problem.

While I realize that dealing with duplicate questions is probably a tedious, time-consuming overhead issue for Moderators, I'm wondering if there can't be a better way of handling them rather than the simple

possible duplicate of …[link to dupe question]

Most of the time, this happens to new users posting their first question, and on the face of it, it seems rather a condescending way to handle it. Granted, the user probably invested no time in researching their problem before posting. And if it truly is a dupe question, it'll get flagged and closed as such at some point, which is as it should be.

So perhaps a more expansive explanation of why it may be a dupe and some hints on how to deal with it might be a more "Friendly AU" method of dealing with it.

Your question appears to be a duplicate of this question [link to dupe question].
Please investigate the answer(s) provided there. If those do not seem to apply to
your situation or don't resolve the issue, edit and expand your question with
details as to what differentiates your issue from the other question. Duplicate
questions are subject to being closed.

A simple boilerplate like this could be used that is more informative and helpful to the user resolving the issue, and how to deal with it if the suggested dupe doesn't shed results on the problem.

EDIT / EXPANSION

Following Eliah Kagan's expansive (and very helpful) answer, here's the real meat of the source of what is behind this question:

Take yourself out of the context of Moderator / Admin / Seasoned Ubuntu User. How does the possible duplicate of … response occur to the user? Get over in their seat and think about how getting that communication is going to land with you. What are you getting from it? What does it leave you with?

If there's any chance that the response occurred as dismissive or rude, then it is exactly that, regardless of what postfacto-spin or rationalization we try to put on it.

I'm no noob when it comes to AU and online forums/discussion boards - I've been doing this for over 20 years. I've been a Mod/Sysop. I get that dealing with users who don't exercise any due-diligence in researching their problem for solutions can be like dealing with four-year-olds who expect an answer right now. And still, with that experience under my belt, when I see the possible duplicate of… comment, I get left with it being somewhat dismissive.

Now, I'm all for having short, succinct responses, for some of the very reasons Eliah pointed out (keeps things small and readable). But if there's the possibility of expanding a response to provide just enough additional information to help the user, then I think that it's worth it. If the system isn't set up to allow for it, then I think that needs to be looked at.

Source Link
douggro
  • 2.6k
  • 11
  • 3

Better handling of marking duplicate questions?

While I realize that dealing with duplicate questions is probably a tedious, time-consuming overhead issue for Moderators, I'm wondering if there can't be a better way of handling them rather than the simple

possible duplicate of …[link to dupe question]

Most of the time, this happens to new users posting their first question, and on the face of it, it seems rather a condescending way to handle it. Granted, the user probably invested no time in researching their problem before posting. And if it truly is a dupe question, it'll get flagged and closed as such at some point, which is as it should be.

So perhaps a more expansive explanation of why it may be a dupe and some hints on how to deal with it might be a more "Friendly AU" method of dealing with it.

Your question appears to be a duplicate of this question [link to dupe question].
Please investigate the answer(s) provided there. If those do not seem to apply to
your situation or don't resolve the issue, edit and expand your question with
details as to what differentiates your issue from the other question. Duplicate
questions are subject to being closed.

A simple boilerplate like this could be used that is more informative and helpful to the user resolving the issue, and how to deal with it if the suggested dupe doesn't shed results on the problem.