There are several ways to handle these and each country or region uses a different method.

Even if we come to a consensus on one there will be someone else to come along who feels it should be done a different way.

If anything, we should come up with a "default" method of entering any given name and after it is shown that a credited person has a double name/maiden name, change that person's credit to whichever method the group decides on. Of course, this should be "region-location specific".

Otherwise, we will see this revisited time and again as we already are.

Quoting Dan W:

Quote:
Of course, this should be "region-location specific".

Common names have to be global, locality specific common names would break the linking system.

Quoting RHo:

Quote:
Quoting Dan W:

Quote:
Of course, this should be "region-location specific".

Common names have to be global, locality specific common names would break the linking system.

It does not have to be global. The data base is broken up by region and then by locality. What works in a region 1 profile would not have to be the same in a region 2 profile. In turn the Localities are also separate.

I agree, and if I understand correctly, the common name should be global across the whole database. Region specific common names wouldn't work.