* Importing Generations GEDCOM
-
pandasonthemove
- Newbie
- Posts: 4
- Joined: 30 Oct 2014 21:33
- Family Historian: V5
Importing Generations GEDCOM
I'm following the instructions in the knowledge base for migrating from Generations Family Tree to FH5. I have run the preload source clean and then imported the updated GEDCOM file.
The log file contains numerous EXCLUDED errors along the following lines:
Record Type=Note. Gedcom Id=N82. Record Number=78.
l.29437 - EXCLUDED: Invalid line level. Branch ignored: "3 TEXT RG11/1954/46/1"
l.29437 - EXCLUDED: invalid line : "3 TEXT RG11/1954/46/1"
Grateful for any advice...
Thanks
Pete
The log file contains numerous EXCLUDED errors along the following lines:
Record Type=Note. Gedcom Id=N82. Record Number=78.
l.29437 - EXCLUDED: Invalid line level. Branch ignored: "3 TEXT RG11/1954/46/1"
l.29437 - EXCLUDED: invalid line : "3 TEXT RG11/1954/46/1"
Grateful for any advice...
Thanks
Pete
- tatewise
- Megastar
- Posts: 27088
- Joined: 25 May 2010 11:00
- Family Historian: V7
- Location: Torbay, Devon, UK
- Contact:
Re: Importing Generations GEDCOM
Welcome to the FHUG.
I am not a Generations expert but I recognise the error message.
The problem is associated with Note Records that have a Source Citation attached.
Those Source Citations have some Text From Source lines which don't quite adhere to the GEDCOM 5.5 spec.
I don't know how familiar you are with GEDCOM text files but here goes.
(If none of this makes sense then please ask.)
The cleaned up GEDCOM (.ged) file your are loading into FH is a plain text file.
This file can be edited with a plain text editor such as Start > All Programs > Accessories > Notpad.
Run Notepad and click File > Open then bottom right of Open dialogue change Text Documents (*.txt) to All Files (*.*).
Now you can navigate to and open the GEDCOM (.ged) file.
To find the Note Record mentioned in the error report use Edit > Find and enter 0 @N82@ NOTE and click Find Next.
Scroll down to show a few more lines that should look somewhat like:
I suspect the problem is that there should be a 2 DATA line between 1 SOUR and 3 TEXT.
Try entering such a line in a few rogue Note Records and see if that fixes the error message.
If it does, and there are not too many, then fix them by hand.
Otherwise, ask for advice.
I am not a Generations expert but I recognise the error message.
The problem is associated with Note Records that have a Source Citation attached.
Those Source Citations have some Text From Source lines which don't quite adhere to the GEDCOM 5.5 spec.
I don't know how familiar you are with GEDCOM text files but here goes.
(If none of this makes sense then please ask.)
The cleaned up GEDCOM (.ged) file your are loading into FH is a plain text file.
This file can be edited with a plain text editor such as Start > All Programs > Accessories > Notpad.
Run Notepad and click File > Open then bottom right of Open dialogue change Text Documents (*.txt) to All Files (*.*).
Now you can navigate to and open the GEDCOM (.ged) file.
To find the Note Record mentioned in the error report use Edit > Find and enter 0 @N82@ NOTE and click Find Next.
Scroll down to show a few more lines that should look somewhat like:
Code: Select all
0 @N82@ NOTE The Munro family came from Arizona.
1 SOUR @S41@
3 TEXT RG11/1954/46/1
Try entering such a line in a few rogue Note Records and see if that fixes the error message.
If it does, and there are not too many, then fix them by hand.
Otherwise, ask for advice.
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry
-
pandasonthemove
- Newbie
- Posts: 4
- Joined: 30 Oct 2014 21:33
- Family Historian: V5
Re: Importing Generations GEDCOM
Hello Mike,
That's a really helpful reply - thanks very much indeed. I am not familiar with the details of GEDCOM, but I get your drift so I will have a go at editing the file and see what happens.
Cheers
Pete
That's a really helpful reply - thanks very much indeed. I am not familiar with the details of GEDCOM, but I get your drift so I will have a go at editing the file and see what happens.
Cheers
Pete
-
pandasonthemove
- Newbie
- Posts: 4
- Joined: 30 Oct 2014 21:33
- Family Historian: V5
Re: Importing Generations GEDCOM
Interesting (well in a geeky kind of way!). It looks like you need to add a DATA tag as you suggest Mike, BUT modify the levels as well - see below.
Pete
---------------
Here's a sample note from the problem GEDCOM - note the sequence 1 CONC, followed by 2 SOUR:
0 @N1@ NOTE
1 CONC Rye states that she was neice and co. heir of Robert Bene Esq.,
... more CONC records in here ...
1 CONC
2 SOUR @S12@
3 TEXT 271
2 SOUR @S22@
2 SOUR @S106@
3 TEXT p110, MIS/111
2 SOUR @S16@
Now if I amend it like this then it works:
0 @N1@ NOTE
1 CONC Rye states that she was neice and co. heir of Robert Bene Esq.,
... more CONC records in here ...
1 CONC
1 SOUR @S12@
2 DATA
3 TEXT 271
1 SOUR @S22@
1 SOUR @S106@
2 DATA
3 TEXT p110, MIS/111
1 SOUR @S16@
Pete
---------------
Here's a sample note from the problem GEDCOM - note the sequence 1 CONC, followed by 2 SOUR:
0 @N1@ NOTE
1 CONC Rye states that she was neice and co. heir of Robert Bene Esq.,
... more CONC records in here ...
1 CONC
2 SOUR @S12@
3 TEXT 271
2 SOUR @S22@
2 SOUR @S106@
3 TEXT p110, MIS/111
2 SOUR @S16@
Now if I amend it like this then it works:
0 @N1@ NOTE
1 CONC Rye states that she was neice and co. heir of Robert Bene Esq.,
... more CONC records in here ...
1 CONC
1 SOUR @S12@
2 DATA
3 TEXT 271
1 SOUR @S22@
1 SOUR @S106@
2 DATA
3 TEXT p110, MIS/111
1 SOUR @S16@
- tatewise
- Megastar
- Posts: 27088
- Joined: 25 May 2010 11:00
- Family Historian: V7
- Location: Torbay, Devon, UK
- Contact:
Re: Importing Generations GEDCOM
Yes, perfect!
Generations is getting the SOURce tag level wrong, and omitting the DATA tag.
Are you happy to correct all the others by hand, or is that too many to contemplate?
It will only have to be done once.
P.S.
As a newcomer to FH don't forget our [kb]|> Wiki[/kb].
To start you off visit how_to:key_features_for_newcomers|> Key Features for Newcomers
Generations is getting the SOURce tag level wrong, and omitting the DATA tag.
Are you happy to correct all the others by hand, or is that too many to contemplate?
It will only have to be done once.
P.S.
As a newcomer to FH don't forget our [kb]|> Wiki[/kb].
To start you off visit how_to:key_features_for_newcomers|> Key Features for Newcomers
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry
-
pandasonthemove
- Newbie
- Posts: 4
- Joined: 30 Oct 2014 21:33
- Family Historian: V5
Re: Importing Generations GEDCOM
Thanks Mike and thanks for the links. I'll take a look...
There are just over 1000 notes in the file, so I had a go at producing a plug-in to parse the file and sort it out automatically. Admittedly I started from one of the existing plug-ins but WOW it was pretty straightforward and it seems to have worked. Dead chuffed!
Next issue is to deal with REPO tags as FH is also excluding those!
Pete
There are just over 1000 notes in the file, so I had a go at producing a plug-in to parse the file and sort it out automatically. Admittedly I started from one of the existing plug-ins but WOW it was pretty straightforward and it seems to have worked. Dead chuffed!
Next issue is to deal with REPO tags as FH is also excluding those!
Pete
- tatewise
- Megastar
- Posts: 27088
- Joined: 25 May 2010 11:00
- Family Historian: V7
- Location: Torbay, Devon, UK
- Contact:
Re: Importing Generations GEDCOM
Pete, I can tell you are going to have a WOW of a time exploring all the customisable corners of FH.
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry