Hi,
I started getting inconsistency warnings for a lot of my records (saw other people reporting it as well), and I don't think they are useful. For example, I'm using female married names in the "last name" field, which means, for example, that Orvydas may have a daughter who has last name Kulnienė (after husband) in last name field, and Orvydaitė in the birth surname field. Apparently, the inconsistency detector considers that a problem, while I don't think it is.
Did anyone run into similar issues? I think that at the very least the detector should try and match the father's name with birth surname, instead of what it does now. In order for it to work meaningfully for Lithuanian surnames, this matching cannot be literal.
The discrepancy is in the actual naming of the fields. In English it is Birth Name where as in Lithuanian it is Mergautinė pavardė (maiden name).
These are two separate things for a female her maiden name is her birth name; for a male his surname is his birth name but not really a maiden name - the male's surname never changes.
It is frustrating because the system is telling us that there is an error. If you go in and make a correction, it still shows it as an error exists.
Benediktas Jankauskas - the surname/pavardė has to be the legal name that one would be searching. A hyphenated surname is a "legal" surname that has been registered at birth. We cannot create a surname that doesn't exist in legal records.
That is how I have always viewed the creating of the family tree.
The consistency alerts were quite the surprise, yes. What is most annoying is having to check hundreds of profiles to "ignore" what is in most cases a perfectly formed Lithuanian woman's married name.
I also agree with Angele that creating "fictional" hyphenated surnames is not something that makes sense. Ideally, Geni would be able to parse the father's surname, find the "root" portion of the name in the daughter's name, and disable the inconsistency alert. We'll see, I guess.
--David Venckus
This is a poor implementation of what seemed like a good idea to an English language speaking computer programmer. We should all write to the help desk and open trouble tickets asking this feature be turned off until they can reprogram it so it does not apply to surnames entered under language tabs other than the "default" which is English of course.
My comments are based on the research I have done in the past 5 years. Even in Google when you type the name - the information thrown out is based on Government information, birth, death, marriage. All surnames that surface are what I call legal. Official documents have been filed to make the name "official". So if a male adopts his wifes name that too has to made official.
The worst challenges in research for the family tree is the "brutalized" versions of Lithuanian surnames upon the arrival to the USA and probably because our ancestors were not "able for what ever reason" to fill out their own forms - but they were filled out by people who had no idea how Lithuanian names were spelled - recorded what they heard - so for example my surname became not Narusevicius but Narusavage or Narcavage - which even DNA can't really prove if we are related.
SO I agree with @Edward Stavin - the programmers still have a lot of work to do to make this work for Lithuanian surnames. I am not about to change 2000+ profiles.
we should report our problems at https://help.geni.com/hc/en-us/requests/new Use the submit a ticket feature.
Be sure to include that you are taking issue with https://help.geni.com/hc/en-us/articles/360037797034-What-is-the-Ch... and how it falsely identifies issues with the surnames of Lithuanian children when all the rules of the Lithuanian language have been followed.
If someone has an additional idea or a better one let me know.