Gedcom corruption error on Ancestry #general


Victoria Fisch
 

For some reason I recently began to use a forward slash mark to separate Anglicized or American names from Hebrew names in the first name box on Ancestry. Today I discovered that using a slash mark on Ancestry can corrupt a downloaded Gedcom.
 
DO NOT separate multiple names using a forward slash mark in either the first name box OR the surname box.
 
If you do, when you download your Gedcom, the slash mark will tell the file to separate the double or triple first names, jump one of the first names to the surname box, and delete the original surname.
 
When you upload the Gedcom back into an Ancestry account, the last name will now be missing and one of the first names will be in the surname box.
 
Victoria Fisch
Sacramento CA
 
 


Odeda Zlotnick
 

A google search for "Gedcom forward slash" indicates this seems to be true of all Gedcoms - not only on Ancestry - a forward slash is part of the Gedcom syntax for separating the given name from the surname
--
Odeda Zlotnick
Jerusalem, Israel.


Dahn Cukier
 

                      
The forward slash is to offset the family name.
I have not tried, but I think the software (Ancestry) should
have refused the forward slash as part of the name.

The exported  GEDfile  line comes out as
1 NAME Dahn  /Zukrowicz/   

I suggest looking at the exported file.
If all the names appear, then the download, worked and
can be repaired. The slash can be changed to a dot (.),
but check that it loads correctly before changing all the
names.

ALWAYS copy the file as a backup and work on only one of the
files. Save the corrected file often so you can go
back to a later more corrected version.

Good luck
Dahn  Zukrowicz   


When you start to read readin,
how do you know the fellow that
wrote the readin,
wrote the readin right?

Festus Hagen
Long Branch Saloon
Dodge City, Kansas
(Gunsmoke)


On Sunday, July 18, 2021, 3:51:08 AM GMT+3, Victoria Fisch <victoriafisch@...> wrote:


For some reason I recently began to use a forward slash mark to separate Anglicized or American names from Hebrew names in the first name box on Ancestry. Today I discovered that using a slash mark on Ancestry can corrupt a downloaded Gedcom.
 
DO NOT separate multiple names using a forward slash mark in either the first name box OR the surname box.
 
If you do, when you download your Gedcom, the slash mark will tell the file to separate the double or triple first names, jump one of the first names to the surname box, and delete the original surname.
 
When you upload the Gedcom back into an Ancestry account, the last name will now be missing and one of the first names will be in the surname box.
 
Victoria Fisch
Sacramento CA
 
 


suemo63141@...
 

I think there must be many ways to corrupt gedcom files. I am guilty of several travesties on ancestry - question marks, quotes, parens, hyphens, commas, and I despair of being able to correct what needs correction. Is there a "Gedcom for Idiots" source that someone could recommend? I don't know how to look at the file, or whether it is possible to correct it without making matters worse. I have a big tree (7000-ish), and did not recognize the problems that I might be causing by editorializing in the critical fields, but correcting every entry is very daunting. I don't speak technie, so please have pity! 
--
Susan Cullen SCHWARTZ


Feige Stern
 

While I can't speak about the issue of file corruption, I do have a suggestion for including Jewish names on each person's profile.  I think this is very important information to include and I can't tell you how often I've been called on to retrieve this information- especially for things like burials, Aliyahs, baby naming etc.

I enter Jewish names as a Fact under "also known as".  This also works for including nicknames.

Feige Kauvar Stern
Cleveland, OH


Sarah L Meyer
 

If you have this problem, please open your Gedcom as a TEXT file in Notepad or Wordpad (do not use Word).  You can edit it there replacing that slash with something else (such as a dot) using search and replace (and if these places are the only places that you used a slash) you could try a replace all.   Then save your file.  I edit my gedcom files regularly tp replace NPFX with TITL .  If you use UFT-8, I strongly recommend Notepad because it does not interfere with foreign alphabet characters.  
--
Sarah L Meyer
Georgetown TX
ANK(I)ER, BIGOS, KARMELEK, PERLSTADT, STOKFISZ, SZPIL(T)BAUM, Poland
BIRGARDOVSKY, EDELBERG, HITE (CHAIT), PERCHIK Russia (southern Ukraine) and some Latvia or Lithuania
https://www.sarahsgenies.com


Sally Bruckheimer
 

Many databases use certain Special Characters for certain things, so use of / or * or other characters might cause problems.
 
But as a Database Administrator, I know that what should be in a certain box of the program is a single name - either a Double Name or a First and Middle name included. Aliases usually go into separate Alias or other boxes in the program. If your program has a place for Aliases, you would put somebody's Hebrew or Yiddish name there, as well as secular names. For example, my ggrandfather was born Baruch Lopes de Leao in Amsterdam, grew up as Barnett Lopes de Leao Laguna in London, and became Bernard Laguna in the US: his name and 2 aliases.
 
That said, in Ancestry, I put multiple names in the given and surname boxes, as Ancestry will search all given names and surnames to find Hints.
 
Fathers' names do not go in the name box: if he was Simon ben Abraham, his given name was Simon and his surname was ben Abraham. Either those would be his name, or perhaps an alias of Sam Cohen (a secular name of somebody in the US or UK). Legacy Family Tree, that I uses, allows for aliases, and allows you to 'swap' an alias and the primary name, but it will always show both in the search for a name, if you choose.
 
Dates can be a problem. If I have a Jewish date for some event, many programs won't allow it, but I wouldn't want to assume that today's ease of changing to a Christian date was available 100 or more years ago, so I wouldn't change to the Christian date, and I don't need to in Legacy Family Tree, although I have to turn off error checking of dates. Some other programs won't allow you to enter Jewish at all. A must be April or August, not Adar!
 
Sally Bruckheimer
Princeton, NJ


Sarah L Meyer
 

In Legacy, you can use Jewish dates in the description or note fields but not in the date fields at this time.  About 10 years ago, I met someone from the Legacy team in person (on a plane I think), who said that they were working to make the program more "Jewish friendly", he mentioned the dates.  I mentioned the individual input screen's baptism field, which I now understand can't have a different label but could be hidden in a new version of Legacy.  I keep waiting for that to happen.
--
Sarah L Meyer
Georgetown TX
ANK(I)ER, BIGOS, KARMELEK, PERLSTADT, STOKFISZ, SZPIL(T)BAUM, Poland
BIRGARDOVSKY, EDELBERG, HITE (CHAIT), PERCHIK Russia (southern Ukraine) and some Latvia or Lithuania
https://www.sarahsgenies.com


Sally Bruckheimer
 

"In Legacy, you can use Jewish dates in the description or note fields but not in the date fields at this time"

I have been using Jewish Calendar dates in date fields since I started using it.

Sally Bruckheimer
Princeton, NJ