Automatically identify related/potential duplicate correction issues to the same item?

Automatically monitor correction issues (paper revisions, metadata corrections, author page requests) for potential duplicates/related ones?

**Why I believe this would be useful to have**
I sometimes forget to check whether there is already a related issue. Issue submitters are usually not aware of related issues or even if they are, they might not mention this at all.
I've closed duplicates or marked related issues for all three kinds in the past manually. It is hard to guess what effect the author system change will have on this (closing old requests without ORCIDs vs newly submitted ones because "their" author pages changed contentwise)

Knowing about related issues helps me to gather all relevant information to process the request and avoid doing the same work twice saving us time. Identifying duplicates helps to keep the number of issues down, making it more manageable and feasible to achieve milestones on the maximum number of open issues.

**How to implement it?**
We could just check the issue title as the first step. This might be imprecise, but less prone to overgeneration. Imprecise because some delete the id from the issue title or make it harder to parse out, also for multiple author pages people might only refer to one page in the title vs multiple in the description.

Can this be done via GitHub actions? Or would it be received as distracting chatter? Is it worth the effort?

We could add a field in issue templates asking submitters if they have opened an issue before about this or are aware of related issues - but not everyone is going to use it, so I prefer an automatic approach.

**What issues should be identified as related for the three correction types?**
- paper revisions: if multiple revisions for the same paper are submitted before they are processed, it's good to know about their relation to avoid unnecessary work.
- metadata corrections: people might not be aware someone else submitted a metadata correction already. The issues for the same item can be about different parts of the metadata (e.g. abstract, title, author list).
- author page requests: either by same author (with same/different account) or a namesake about the same name. Multiple issues could be opened to raise awareness/signal urgency, provide updated info etc. The updated info can be useful while processing requests. Also, two namesakes reporting necessary disambiguation provide can help verify submitted info (if both agree on a partition of the papers: "paper 1 is not mine, but paper 2 is" - "paper 1 is mine, but paper 2 is not").

---
Identifying metadata corrections relevant to an author page request is not part of this issue, though this would be useful information too. (I tend to link metadata corrections to author page requests if I become aware of them: mostly for requests to merge pages that are actually solved by metadata corrections).