Why is there no option to create rejected match between someone born 200+ ago and an unlisted profile?

+6 votes
In searching for matches to my watch list, I often come across profiles of people born 200-400 years ago that have a potential match to an unlisted profile.  It is my understanding that people born more than 200 years ago should have open profiles.  If that is the case, then the unlisted profile can't match.  Why don't I have the option of creating a rejected match?  It is not a big deal for me, it is just annoying to keep seeing these "potential" matches.
in Policy and Style by Daniel Nordlund G2G6 (8.8k points)
Have you asked the profile manager to change from unlisted to at least public. It's worth a try, anyway.
No, I haven't asked. I assumed that the profiles were unlisted for good reason.  My question arose because it was my understanding that someone who was born more than 200 years ago must have an open profile (i.e., couldn't be public, private, or unlisted).  If that is not the policy, then my question can be ignored.
That's the policy, certainly, but there are still people who want to keep everything locked down as either private or unlisted even if it's over 200 years old. It certainly can't hurt to ask.

2 Answers

+3 votes
Well, I think the theory is that the profiles that you want to call rejected matches are those which actually might be a match but you know aren't and you don't want someone proposing a merge that would be a disaster.  I don't think people would try proposing a merge like yoiu suggest for the very reason you state.  But if you see someone who you know is a cousin but lived somewhere else, it's useful not to have people potentially trying to merge them.  When I'm entering new profiles, I often see a bunch of potential matches but can reject them all at a glance. In other words, it's not likely to ever be a problem.
by Dave Dardinger G2G6 Pilot (410k points)
+2 votes
I agree with Dave.

An unlisted profile normally represents a living child, so there shouldn't be much chance of confusing them with someone who lived 200+ years ago. Let's reserve "rejected matches" for profiles that a reasonable person might possibly confuse.

When I look at the "rejected matches" on a profile I get annoyed when I find that I'm being shown people who obviously don't match -- in a hypothetical example, when Mary (Pinney) Martin, born in 1637 in England, has a rejected match with Anna Mary (Martin) Swanson, born in 1924 in New Zealand. Those obvious nonmatches take up space on the profile and divert attention from similar-looking profiles that contributors may need to be aware of.
by Ellen Smith G2G Astronaut (1.3m points)

Related questions

+1 vote
1 answer
110 views asked Mar 13, 2020 in WikiTree Help by Katharine Jones G2G5 (5.8k points)
+4 votes
1 answer
+4 votes
1 answer
138 views asked Apr 25, 2015 in WikiTree Tech by Ellen Smith G2G Astronaut (1.3m points)
+7 votes
1 answer
+6 votes
2 answers
142 views asked Jun 18, 2014 in Genealogy Help by anonymous
+1 vote
1 answer
135 views asked Jan 14, 2019 in WikiTree Help by Gale Spates G2G Rookie (170 points)

WikiTree  ~  About  ~  Help Help  ~  Search Person Search  ~  Surname:

disclaimer - terms - copyright