Welcome to Codidact Meta!
Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.
Comments on List all duplicates for a question on the target question's page
Parent
List all duplicates for a question on the target question's page
Currently when viewing a post, there is no indication that it's being used as a duplicate target.
As a curator, it's useful information to me that when I view a question, I am also informed if any other posts are linked to it as a duplicate. As such, I'd also want easy access to these posts.
As a reader and answer seeker, it is useful to see similar posts linked to it, especially if other answers were posted to the duplicates that contain something useful not in the duplicate target's answers (or they present the information in a different, and more useful, way). I would argue that we have a problem if the reader needs to go seek these posts out, though, since it would mean we have failed to deliver the best Q/A possible.
On the question page itself, I'd like to see the number of posts closed as a duplicate of it. I also want to access the full list of duplicates. Either, there's a link to the search page (with search arguments filled out) somewhere on the Q/A page, or the list is shown somewhere on the page (in the sidebar, below the post, or elsewhere). If the list is long, only a subset of its content can be shown directly, though.
So, if posts B and C are closed as duplicates of A, I want to see on A's page, that B and C are closed as duplicates of it.
Post
I like this idea, but I wonder if it should be optional.
For the link to search results that you mention, that sounds sufficiently unobtrusive that perhaps it wouldn't need to be optional. I think it would need a feature request for search first though - I don't think there's currently a way to search by which question a duplicate targets.
I would argue that we have a problem if the reader needs to go seek these posts out, though, since it would mean we have failed to deliver the best Q/A possible.
Although we strive to deliver the best possible, we're all fallible so it would be good for the reader to have this opportunity to judge for themselves, and potentially raise on Meta if they disagree about which of the posts should be closed as a duplicate.
0 comment threads