New inconsistency detector triggers for Lithuanian records

Started by Jurij on Sunday, November 10, 2019
Problem with this page?

Participants:

Showing all 22 posts
Jurij PRO
11/10/2019 at 5:57 AM

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.

11/10/2019 at 6:26 AM

Agree. It's not useful at all. It's misleading

Private User
11/10/2019 at 6:53 AM

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.

11/10/2019 at 6:55 AM

Yes, a lot of my profiles with Lithuanian names are flagged for inconsistency, for the reasons mentioned above. I agree that they are not useful, and ignore them.

11/10/2019 at 7:04 AM

Sorry, I did'nt run in such issues.

11/10/2019 at 8:48 AM

Hallo, thank you for applaying. I do`nt see there inconsistency. There is simple solving this problem; we need to write Orvidaitė-Kulnienė in case of presented sample, or Narbutaitė-Kellet, if husband of Narbutaitė is Kellet.

With best wishes
Benediktas Jankauskas

Private User
11/10/2019 at 10:55 AM

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.

11/10/2019 at 4:38 PM

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

11/10/2019 at 5:03 PM

agree - an absolute nuisance

11/11/2019 at 2:21 AM

I think you are seeking for unnecessary requirement for globalisation. Remember, please, Esperanto! Lithuanian language is very old, therefore very specific language, unique Indo-European language. We need to keep such a property.

11/11/2019 at 5:13 AM

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.

Private User
11/11/2019 at 5:47 AM

Private User, lithuanian male CAN change his surname to of his wife when marrying her.

Private User
11/11/2019 at 6:03 AM

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.

11/11/2019 at 2:45 PM

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.

11/11/2019 at 3:11 PM

@Edward Stavin, thanks. Good suggestion. I opened a ticket.

11/11/2019 at 7:19 PM

I have also opened a ticket. Hoping they disable this dubious "feature" until it can accommodate non-English surname conventions.

11/12/2019 at 2:02 PM

I've just received answer from Geni customer support:
Thank you for bringing this to our attention. We currently recognize patronymic names from several countries / cultures, and exempt those from the inconsistency checks where applicable. We'll add Lithuanian patronymics.

11/12/2019 at 10:41 PM

Here is the response I got regarding my ticket:

Thank you for the information. We will be taking into account the Lithuanian surnames so those will not be flagged as an inconsistency. We will be re-running the consistency checker for 'Children with different last names' tomorrow.

11/13/2019 at 7:44 AM

I also received the same response as Stephen. It will be good if their changes fix the problem.

--David

Private User
11/14/2019 at 5:39 AM

I have not received a similar alert. I am convinced that this is because I choose Lithuanian when entering data.

11/15/2019 at 3:32 AM

I also received the same response. And I see that the problem was already fixed.

1/6/2020 at 1:51 PM

Aš jų nei vieno nepažįstu.

Showing all 22 posts

Create a free account or login to participate in this discussion