(b)
My People overview list is grouped by last name. It is really useful to have all the same family names, so that all people are listed/grouped with the same familyname together.
That is why I choose to enter for example “Declercq” even in the records it was written as “Declerq” for example.
Then I go to the person, Names tab and fill in one or multiple alternative surnames.
going to another “Declercq” person these alternative surnames are not listed. I have to add them manually to each person.
Let’s say that I have 500 people Declercq but I find a new alternative spelling then I will have to add it manually to 500 people their alternative list.
It feels like i’m doing something wrong. There is also preferred name, alternative name. I can add multiple lines, add multiple names on a single line.
Help, i’m confused and would like to see some real examples of how it should be used properly.
Can the “Group by” be used for the search/filtering? If all the Schmidt surnames have been Grouped in Smith, would searching for “Smith, Georg” find “Schmidt, Georg”?
Of course, Grouping wouldn’t help searching for the Given name variants.
Tthe Soundex searches should help phonetically similar variants. But that appears to be surname-based too.
Yet you don’t answer it, at least not as I read @wst’s post. You talk about searching for names but the question is about best practice for entering names.
There is the Group As option in the Name Editor. This allows you to group variations in the surname spelling together. I give each variation the same Group As option and apply it to all instances of the name.
In your example each surname will get the following:
Declercq (Declerk, Decklercq, Decleirc, Declerc)
Note: Setting the Group As option does NOT alter the entered Surname. The resulting grouped names show up in the Grouped People list but not in the flat People list.
To make the Grouped People view really take advantage of the Group As function, you actually need to alter the Displayed name option in Preferences to a more natural Given Surname, Suffix. This displays Johannes Decklercq and Johannes Declerk next to each other.
There is no such grouping for given names.
If a person has various spelling of their given name and/or surname this is where adding alternative names to a person’s record becomes desirable. If one found document does not completely match another document, you can give the person multiple name records with the Type “Also Known As” or other appropriate name Type.
Note: Each name record can have notes and citations added to document the variations you discover.
The biggest decision you will need to make… which of the names will get slotted as the Preferred name. (right-click on a name to move a name into the preferred slot.) It is the Preferred name that displays and is used in reports. Most reports do not access alternative names although the Complete Individual and the Narrative Web do (my go to reports).
ok, I didn’t know about the "override “group as” in the Name Editor. This will allow me to have every family member under the same name in the Grouped People view as I understand.
Not sure what you mean by “This displays x and y next to each other”.
If I have a Person: Johan Declerck.
I can open the Person dialog and go to tab [Names] and there is the Preferred name: Declerck, Johan
Do I add a new name there in the Person dialog, by clicking [+] and set it as Also known as in the name editor?
or do I double click the Preffered name “Declerck, Johan” and in the Family Names section add a new entry in that list? Still confused what the difference is. The latter only allows me to set an additional surname not a given name.
People > Preferred name
People > [+] Alternative name
or
People > Preferred name
People > Preferred name > [+] Family name
Let’s say people call Johan Declerck also “Jo DC” whould that be an alternative name of the person, filled in with nick name: Jo DC or do we fill in Given: Jo and Surname: DC
As Jo DC is the nickname but actually the first and lastname of the “also known as”.
Oh this is confusing.
Some extra screenshots or a video tutorial on this would be great.
(Guess for now I’ll be playing a bit further around with the “Group As”)
Within the Grouped People list you have now brought those named Decklercq and those named Declerk (and other variations) together using the Group As override functionality. But within the grouped name list, the names are still sorted using the default Name Display set in Preferences.
With the display name set to Surname, Given Suffix the names will display as…
Decklercq, A
Decklercq, B
…
Decklercq, Z
Declerk, A
Declerk, B
…
Declerk, Z
By switching the displayed name format to Given Surname Suffix, the names in the Grouped list will now display as…
A Decklercq
A Declerk
B Decklercq
B Declerk
…
Z Decklercq
Z Declerk
The names displayed in any list will always remain the name set in the Preferred Name slot. That is not to say individuals may have additional names added to their record and each of these names can have their own Type.
But each person can have only one Preferred Name which you set from the names you add to the person’s record. The preferred name is what will be displayed in lists and the only name used in most (not all) reports.
Once in the Names tab, clicking on the + add icon will allow you to add additional names to list. It will open the Name Edit window to enter the information.
Double-clicking an existing name in the list, or by clicking on the Edit icon for a selected name, will open the edit window allowing you to make changes.
If you want to swap names into the Preferred Name slot, select the desired name and right-click for the option. Or you can drag-n-drop from the name list into the preferred slot.
def sort_name(self, data):
handle = data[0]
cached, name = self.get_cached_value(handle, "SORT_NAME")
if not cached:
name = name_displayer.name_formats[2][4](data[COLUMN_NAME])
self.set_cached_value(handle, "SORT_NAME", name)
return name
Right now I edit the Sort order in all name records. I just set each to “Given”
It is not as onerous as you might think. With surname guessing, the modified Sort is carried forward from father’s record to a child or child to father. The only records that need to be manually set is when a spouse is added or when additional name records are added. (I do all names even if they are not the preferred.)
I did have to edit the XML file manually with a lot of search and replace to alter already existing records (before supertool if it could have done it).
@emyoulation I’ll look at that code to see if it can be used to separate the default sort from the default display.
Ok I understand the “Group as” where the found name is for example “Mineu” but you want to group it together as “Minne”.
In the screenshot I have an example with a “Minne” but I have found many other surnames. Am I using these alternative surnames correctly?
The Person card > Names can have multiple alternative names but an alternative name can have also multiple surnames. Still not sure how to use this correctly… and how these alternative names could be reused with the other “family” members.
As from what I understand if you have “Catherina Minne” and “Egidius Meny” you can override the name from “Egidius Meny” so that it groups under “Minne” (“Egidius Meny”).
But this does not reflect the “Minne (Meny)” somewhere.
And what if I find Egidius Meny and Egidius Moni which should both the “Minne”
I can add both surnames to Egidius his card. And for his brother “Pedro” I have to redo all this work and set the names “Meny” and “Moni” and “Minne”. So that when I do something with “Pedro” that I know that it is actually “Minne, Meny or Moni”. There is no way for me right now to see that “Pedro Meny” could also be Moni or Minne (when doing research online that I have to search for multiple names).
overload me with screenshots and examples héhé as I am confused.
When you add more than one Surname to a person’s record you are telling Gramps that all the surnames combined together are the person’s surname. In this example the person has two surnames. In most instances with two or more surnames there may be a connector between the names (often a hyphen) but in this case there are no connectors.
In your example for Catherine Minne, you are using the multiple surnames to account for all the various spellings of the name. I dare say she was only born with one surname.
To account for all the various spellings of the surname, this is where the override for Group As comes into play. Set her Group As surname override to Minne (Meny, Monie, Moni)
And set Egidius Meny’s Group As override to Minne (Meny, Monie, Moni)
Set Amanda Monie’s Group As to Minne (Meny, Monie, Moni)
Set Pedro Moni’s Group As to Minne (Meny, Monie, Moni)
You can use the Group All option to set every record with the same surname to the same Group As override.
And a person CAN have more than one name record. If for Catherine’s marriage record uses the surname Meny you can add an “Also Known As” record with this spelling with the same Group As Minne (Meny, Monie, Moni)
In these cases, my Group as are specially named (e.g: Legoux << Legou[xt]) and I have defined a naming preference firstname lastname.
With this setup I can use this Supertool script, which redefines Sort as for grouped people with this “<<” in its grouping name, permitting me to swap from the standard sorting (lastname firstname) to that one I’ve defined:
[Gramps SuperTool script file]
version=1
[title]
People - Sort_as of grouped people
[category]
People
[initial_statements]
# The last Name Format entry in Preferences should be: First Name, Last Name[Name]
# /!\ Do not check Commit Changes, the commit is explicit in the script
sort_by_fn = True # By firstname -> True; By lastname -> False
symbole_groupement = "<<"
if sort_by_fn:
sort_order = -1
else:
sort_order = 0
[statements]
nobjs = nameobjs
if symbole_groupement in db.get_name_group_mapping(nobjs[0].get_group_name()):
modifie = False
for n in nobjs:
if n.get_sort_as() != sort_order:
n.set_sort_as(sort_order)
modifie = True
if modifie:
db.commit_person(person, trans)
[filter]
[expressions]
[scope]
all
[unwind_lists]
False
[commit_changes]
False
[summary_only]
False
