I don't know that we have to change the policy. We just have to fix it so when you click "2 place connections found", the search/sort function will match the Mt St Helens, Miss, USA with its proper sources.
Remember, the classic example I brought to the table was that the GEDCOM said Salt Lake. Utah, but the searcher said Salt Lake Utah and could not find Salt Lake Utah.
It appears to me that the searcher was searching the original GEDCOM and not finding any match because the original GEDCOM had no Salt Lake Utah. Similarly, Mt. St. Helens (in the GEDCOM) will fail the search because the PGV search will look for Mt St Helens , which does not exist.
PGV will say there are 3 place connections, but then it will not find them. I think this is likely a bug rather than a policy decision. There must be a code difference between whatever is reporting "3 place connections found" and whatever is bringing the connection up.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I expect to see for instance Dan I002 or Amos I003 under Helsinki, Finland but for some reason they are not there.
When I click on his birth-place Helsinki, Finland I see some other people linked to Helsinki, but not him.
One of the linked people I see is Meliza I001, who does not have any Helsinki, Finland address.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I don't know that we have to change the policy. We just have to fix it so when you click "2 place connections found", the search/sort function will match the Mt St Helens, Miss, USA with its proper sources.
Remember, the classic example I brought to the table was that the GEDCOM said Salt Lake. Utah, but the searcher said Salt Lake Utah and could not find Salt Lake Utah.
It appears to me that the searcher was searching the original GEDCOM and not finding any match because the original GEDCOM had no Salt Lake Utah. Similarly, Mt. St. Helens (in the GEDCOM) will fail the search because the PGV search will look for Mt St Helens , which does not exist.
PGV will say there are 3 place connections, but then it will not find them. I think this is likely a bug rather than a policy decision. There must be a code difference between whatever is reporting "3 place connections found" and whatever is bringing the connection up.
p.s. John is right. PGV should be dot insensitive. But it isn't. John's great vision is that
AZ
should match
Az aZ AZ. Az.
We just need to make this true.
Back to my original message.
I expect to see for instance Dan I002 or Amos I003 under Helsinki, Finland but for some reason they are not there.
When I click on his birth-place Helsinki, Finland I see some other people linked to Helsinki, but not him.
One of the linked people I see is Meliza I001, who does not have any Helsinki, Finland address.