There will be new fields on Names for next major release.
I suppose some users will try to make some "data migration"
ie. nickname set on attribute will move to nickname field or some data set into alternate names will move to surnames, etc ...
I started a bug-report  for generating a set of filter rules matching these Name data/fields/types, but I see some specific issues.
1. NameType() drop list
The first list used as selector works with AttributeType() but not with NameType(), where I need to write the name type myself.
I suppose it is related to the object status (Name versus Attribute), but I cannot see why it does not work as planned.
2. New fields on Filters/Rules/Person/_HasNameOf.py
On current stable release we have: Given name, Family name, Suffix, Title, Prefix, Patronymic, Call Name. These fields are also used on filtersidebar for matching name.
On trunk, some additional fields: Nick Name, Single Surname, Connector, Family Nick Name
The problem is on the global filter dialog for Person filter rules. To have 11 fields extends the dialog height. ie. Some users will not be able to click on the 'OK validator' button anymore: that's annoying.
First, I thought on move the additionnal fields to a subclass.
This should work, but Nick Name is for given name. So this will not be logical on user side.
Then to split into 2 subclasses : Family Name and related & Given Name and related. But _HasNameOf.py is used by filtersidebar and some arguments have been already set on user profil.
+ maybe try to also add a rule for matching SurnameType()
Get latest updates about Open Source Projects, Conferences and News.