• Only registered members can see all the forums - if you've received an invitation to join (it'll be on your My Summary page) please register NOW!

  • If you're looking for the LostCousins site please click the logo in the top left corner - these forums are for existing LostCousins members only.
  • This is the LostCousins Forum. If you were looking for the LostCousins website simply click the logo at the top left.
  • It's easier than ever before to check your entries from the 1881 Census - more details here

Historic & Modern OS Maps

Alexander Bisset said:
Anne, as I add more features extra things will be revealed. It struck me when I was adding support for age facts that I wasn't actually reporting anything about custom fact types I was ignoring. So I decided I'd report that during load and load the facts anyway. Thus it should pickup and display more facts.

So you don't actually need to do anything it's simply a warning that there are custom fact types it doesn't understand. eg: one of the testers discovered that he had a custom fact type of censuss 1871. This was getting ignored but he could clearly see that it was just a typo on his behalf so he was able to fix it.

BTW on the date errors I may be able to do something about that if you can give me an example. I take it they are all just 3 digit years?
Click to expand...


Thanks Alexander for explaining this - I can see that the fact types are generally custom ones

Recorded unknown fact type Banns
Recorded unknown fact type Divorced
Recorded unknown fact type Petition
Recorded unknown fact type Possible marriage
Recorded unknown fact type Employment
Recorded unknown fact type Address
and some I can change to be more consistent (Employment to Occupation for example).
The date errors are:
Error parsing date 'ABT 966' for I15317: William' error message was : String was not recognized as a valid DateTime.
Error parsing date 'BEF 963' for I15318: Guillaume TALVAS' error message was : String was not recognized as a valid DateTime.
Error parsing date 'ABT 980' for I15319: Matilda DE GANELON' error message was : String was not recognized as a valid DateTime.
Error parsing date 'ABT 942' for I15320: Yves DE CREIL' error message was : String was not recognized as a valid DateTime.
Error parsing date '997' for I15320: Yves DE CREIL' error message was : startIndex cannot be larger than length of string.
I have tried removing the ABT and BEF, but it makes no difference - I just get a different error (see last entry). As you can see there are only a few, so I'm not concerned, but if there is a fix, it may help others with more really old ancestors.
 
I've added support for 3 digit years with the proviso that its the year only ie: any of the above examples would work but a 3 digit year with a month/day combo would fail as that is far more likely to be a typo. I reckoned that for any genuine 3 digit years it is exceptionally unlikely that you know the actual month or day of the event. Thus this seemed like a decent compromise. Understand years without failing to pick up combinations that are likely to be an error.
 
BTW for Banns/Divorce/Petition are they family facts or individual facts. They should be supported if they are family facts as there are official GEDCOM tags for them.

MARB - Marriage Banns
MARC - Marriage Contract
DIV - Divorce
DIVF - Divorce Filed
ANUL - Annulment
ENGA - Engagement

Are the additional ones for a family fact. It may be that you created specific custom events if your family tree program didn't understand these official ones. However if it does understand them it would probably be best to use the official tags.
 
Alexander Bisset said:
BTW for Banns/Divorce/Petition are they family facts or individual facts. They should be supported if they are family facts as there are official GEDCOM tags for them.
Click to expand...


The banns/divorce are not ones that I have set up (not knowingly, anyway!), just ones in the default event list provided with Legacy.

Alexander Bisset said:
I've added support for 3 digit years with the proviso that its the year only ie: any of the above examples would work but a 3 digit year with a month/day combo would fail as that is far more likely to be a typo. I reckoned that for any genuine 3 digit years it is exceptionally unlikely that you know the actual month or day of the event. Thus this seemed like a decent compromise. Understand years without failing to pick up combinations that are likely to be an error.
Click to expand...


Thanks, I'll give it a go with just the years.
 
Ah ok Anne have you got a GEDCOM snippet of how Legacy records Banns/Divorce you can show me. It may be it's using non standard tags.
 
Alexander Bisset said:
Ah ok Anne have you got a GEDCOM snippet of how Legacy records Banns/Divorce you can show me. It may be it's using non standard tags.
Click to expand...

I've just created a Banns and Divorce for myself (so it's easy to find on the gedcom, at the top), and it looks like:

1 EVEN
2 TYPE Banns
1 DIV
 
Hmm ok, so Banns is using a custom event rather than MARB. Whereas Divorce is correctly using DIV tag. I know that Legacy 8 is in beta maybe they've fixed this bug in version 8 if not perhaps you should point it out. Basically it is converting the data from its internal database to GEDCOM and in the conversion process writing out the wrong tag.
 
Alexander Bisset said:
Hmm ok, so Banns is using a custom event rather than MARB. Whereas Divorce is correctly using DIV tag. I know that Legacy 8 is in beta maybe they've fixed this bug in version 8 if not perhaps you should point it out. Basically it is converting the data from its internal database to GEDCOM and in the conversion process writing out the wrong tag.
Click to expand...

I'll report it, perhaps as you say it may have been fixed in v8.
 
Ooooo, an LC ancestor number predictor? Sounds interesting, not sure I can wait till next July though!!
 
You must log in or register to reply here.
Back
Top