Seven ways to help revive/refresh a question (including closed questions), and its answers are by:
using the share button beneath the question to advertise it to your networks (no rep needed)
suggesting an edit to improve it that then gets approved i.e. provide additional details or clarify existing details (no rep needed)
raising the need for more editors/...
Cross-posting, or asking on multiple SE sites, is generally discouraged. You should pick the most appropriate site and ask there. If little or no response, you could flag with a request that it be migrated to an alternative.
You can post a link to a question in another SE site within your question, but they don't show up in the Linked or Related sections on ...
There is one more reason why you shouldn't delete your new question. You might have phrased the question or problem differently than the original question. Maybe you phrased it in simple and non-technical terms.
In the future some beginner might have a similar question and wouldn't know what keywords to search for. So he might use a non-technicial term in ...
I would say to just leave it, as (and this is just one reason) it could be used as a statistic to help find "canonical" questions. In other words, if a question has been referenced many times by duplicated questions, it might be considered canonical.
There might be ways to query this information out of the Stack Exchange Data Explorer, e.g. Most Commonly ...
I think if both questions have same quality, flag the newer one to be a duplicate of the older (this is the default action).
On the other hand, if a newer question has (much) more quality than the older one (i.e., there is no doubt about it), flag the oldest as the dupe.
Here are 2 posts from Meta Stack Exchange in line with above:
Should I vote to ...
When marking a question as duplicate, the Quality of Question and Answers is far more important, than the age of the Question.
Secondly, you should avoid chaining of duplicates. What I mean is that suppose Question X is marked as duplicate of Question Y. Now when you see a new Question A, which can be marked as a duplicate, it would be better to mark it as ...
If the best answer to the other question actually does answer the second question, mark it Duplicate, and add a comment to fine tune (not absolutely necessary but nice; a straight "this is dupe" can be off-putting).
If other question's answer is correct, but needs rephrasing to fit current context, then do so as an answer and still mark as dupe.
I believe moderators do not have the same restrictions--and they can also unilaterally just delete one of the questions if necessary--so one option is to flag the question for moderator attention. Please provide a link to the duplicate when you do so. Leaving a friendly comment pointing to the account merge help page would also be a nice thing to do if you ...
There is an excellent Meta SE Q&A about this:
Is cross-posting a question on multiple Stack Exchange sites permitted if the question is on-topic for each site?
In particular I think this quote by Jeff Atwood in his answer is highly relevant:
Allowing cross-posting is a slippery slope.
If you might have slightly better odds of getting an answer ...
The best way to avoid this sort of closure is to include a paragraph in your question saying something like - I read the following answers and they help but are missing the exact measurement I need.
While this is the most important question on the site for you, others (and especially the moderators) are reading 10's of questions a day and may spend only a ...
I've clarified the question title and afterwards reopened the question.
Along PolyGeo's lines, I would like to encourage everyone to help improve questions - especially by clarifying the question titles. Very often, the titles are too generic to be of any help even. This combined with a lack of clarification from the side of the original author can be a ...
Please do not re-ask the question: that goes against one of the principal aims of the site, which is to have a well-organized canonical set of answers. Re-asking creates a duplicate. Duplication more than doubles the efforts of those who search the site for answers (including your moderators and many active community members who conduct these searches as a ...
I prefer to treat questions about code separate from questions about the GUI of a GIS product too.
That is why I rarely support questions being coded as:
qgis and pyqgis; or
arcgis-desktop and arcpy
arcgis-desktop and arcobjects
arcgis-pro and arcpy
arcgis-pro and arcgis-pro-sdk
Sometimes the only answer to a question from a GUI only user is to use code. ...
Regarding the question title:
Should we close Questions as duplicates of old, unanswered Questions?
It is not possible anymore to mark a question as a duplicate, without the older/original thread having an upvoted or accepted answer on it. See here.
2013-02-01: The "close as duplicate" process has been updated: the interface to search for duplicate ...
I'm glad you asked about this because I saw the same question come through and tried to close it as a duplicate of the earlier one with the same result as you.
I just saw this Meta SE Q&A (Is it OK to post a duplicate of a question that didn't get upvoted or any accepted answer?) and it got me thinking.
The way I think I will handle such a ...
Thank you for bringing that to our attention. I have marked the second question as a duplicate. As you indicated, you need 15 reputation (source) to start flagging questions. This is to ensure that users have the sufficient experience to properly flag a question and not generate undue noise for reviewers.
This is certainly not your fault, but I cannot help wondering how much easier your project and our task would be if:
all of our question bodies had only a single question (indicated by the only question mark in the question);
all of our question titles were concise summaries of their bodies; and
all of our questions were tagged consistently
From what I ...
Moderators can mark questions as duplicates of Q&As with unaccepted answers. In this situation I would recommend flagging (which you did) for a moderator to mark one as a duplicate of the other.
I think this should probably be done instead of adding an answer to the newer question. Even without it being accepted, you can still get votes on the ...
In the answer to What is a "merged" question? it says:
If you believe a merge stub is no longer useful, flag it for moderator
attention and ask for it to be deleted.
I think that is the way to proceed.
I do not think it matters whether a merged question (merge stub) has come from the same asker as its master. If a merge stub adds nothing of ...
The ability to retract re-open votes is the subject of a feature request at Meta Stack Exchange - see Ability to retract reopen/delete votes.
It has been open for more than 5 years and appears not to have been implemented nor declined by the Stack Exchange developers.
In the type-in field at the top I always paste the URL to the duplicate rather than its title.
I had not noticed the suggestion that a search could be used, though.
Rather than a bug I think it is an in application documentation error but the bug tag on this should attract the SE developers to clarify whether the search option is expected to work.
On a few occasions I have made earlier poor questions into duplicates of later much better ones by a different user. I may even have done that for the same user using a single account over the course of a few hours/days.
On this occasion the two questions were asked by what I believe to be the same person using two different accounts about 10 minutes apart,...
To address this dot point:
We can't make the "accepted" answer non-accepted, and the accepted answer is always at the top.
A minor point is that the accepted answer is always at the top, unless an asker accepts an answer of their own - in which case its position is determined by its votes alone.
On the main point, I am not too concerned if the ...
I think this answer (which I am now updating) is a good place to address this part of your question:
For various reasons, only a small fraction of users will use/edit old questions and provide new answers. This means the question is only
getting a fraction of the exposure it got when it was a new question;
thus any new answers are likely to be ...
This issue came up in the Canonical Question question I asked a while back here on meta. How do you find that canonical answer which is the same when the question might be very different? My original question title for that was something along the lines of canonical answers vs canonical questions.
In fact, I actually voted to agree with the dupe flag on ...
As the poster of the question referenced above, I woudl like to make a few points. You may have to read this through a few times to get the sequence of things clear, but I do think that it is important.
I made a mistake. I phrased my original question so that it could be answered by recommending an application. It was duly answered, I realized my mistake ...
This is not only about merged questions from same OP, but also about normal duplicates from same OP (i.e. self-duplicate questions).
The merged ones are a particular case because they are locked posts and hence, not qualified for automatic deletion, besides not being eligible for voting, etc.
This will almost happen because OP asks a question, then nobody ...
Having reviewed the two Q&As that you cite, my preferred approach on this would have been for:
the earlier Question to have been edited by the later asker to improve it (no one expects a Question written 3 years ago to be perfect for today); and
the later Answer to have been added to those on the earlier Question where I would expect to see it "float" ...
When a question is marked as duplicate, the message that appears to the Original Poster (OP) is a different message that appears to everybody else.
See @Jaydles's answer here and @Rachel's answer here.
The OP gets the message encouraging to edit the question, so it can go to the reopen queue.
The argument they have used to support this feature is that ...