By coincidence I realized that there are people that have more than one name. It seems that they came into being in a merge operation, at least there is a mention in the person attributes.
1 NAME Josef Aurelius /Lütolf/
2 TYPE birth
2 GIVN Josef Aurelius
2 SURN Lütolf
1 NAME Johann Aurel /Lütolf/
2 TYPE birth
2 GIVN Johann Aurel
2 SURN Lütolf
1 SEX M
1 BIRT
2 DATE 27 AUG 1740
1 DEAT
2 DATE 28 MAY 1772
1 FACT I11913
2 TYPE Merged Gramps ID
One of the names is Josef, one is Johann. The one in my database is Josef, but when I upload my Gedcom export into Stammbaumdrucker (with which I make my trees) it takes the second (wrong) name. The people there tell me they can’t change which one it takes, it takes the second one.
I do not see the name Johann anywhere in the Gramps program, only in the GEDCOM export. So I do not know how to change it. If I can’t find a way to delete the second name in Gramps, the only idea I have is to export GEDCOM and edit in a text editor and then reimport. Then I lose at least my tags and whatever else I have not thought about yet.
I see now that I can filter for lists of either merged ID associations or people with alternative names. That gives me the same number, which in this case is quite large, over 2000. Is there any way to output name and alternative name side by side to make checking easier? The Gedcom is hard work since the entries are below each other, separated by other entries.
There is an advanced tool called SuperTool that can do this easily. Listing alternate names is almost trivial: put “names” in the Expression field and limit the listing by putting “len(names) > 1” in the Filter field.
As an example, in the Gramps sample database there are two people with multiple names:
Many thanks. The Super Tool looks very interesting and I definitely need to understand all it can do.
For my particular problem I think what I’m seeing (but please tell me if I’m wrong) is that the tool will show me the people who have alternate names, but not the actual name and alternate name side by side. If I want to process the 2000 + people in my database that have more than one name entry I need to be able to compare the names easily to throw out the ones that were not put in consciously but purely the result of a merge.
But I will study the SuperTool further. I never stumbled across it when I looked at the add-ons but maybe I was not looking closely enough.
“all it can do” is practically unlimited. It is one of a couple ways to use Python to call the Gramps Engine without having to wrap in in a lot of interface. (If you are experienced in Python, you might want to also explore the Python Eval gramplet.)
No, it does show names side by side. It lists the Preferred name followed by any Alternative names (separated by hyphens).
Hyphens might not be the best delimiter for names … considering they can be part of double-barrelled given or surnames. You might want to use an ampersand (&) or bar (|) instead. The list of names uses the the “Surname, Given Suffix” format regardless of the Name Format selected.
In the following script, the “name” was added at the beginning of the “Expressions to display”. It DOES use the Name Format preference. in this case: Title Given "Nickname" SURNAME Suffix.
Here’s the “Copy” clipboarded after Executing the modified script:
I0044,"Dr. Lewis Anderson ""Big Louie"" GARNER VON ZIELIŃSKI Sr","Garner von Zieliński, Lewis Anderson Sr | Garner, Louis | Garner, Louie",Person,GNUJQCL9MD64AM56OH
But, as you can tell from this excerpt from the Reports → Text Reports → Complete Individual Report…, Names can have a lot more information that that default name format does not include.
Thanks, but that won’t work since I do not know what the merge put into alternate. Some of those names are wrong or incomplete. I won’t get around looking at each one and in many cases confirming with the original source (church records).
Do we know what the logic is for setting the alternate? Is that always the newer ID?
You make a choice of the resultant person during the Merge. (The following Person and Family merge dialogs are not typical. The people involved are so wildly different that you’d never merge them. But that difference is easier when describing which piece of data takes precedence. This also illustrates that Gramps applies no safeguard logic in a merge. The merge process just does what you tell it to do.)