Apologies if this has been reported before: I've had a look but have not found a similar looking topic.
I have noticed that when creating a census entry, if an individual is recorded whose first spouse has died, A.S. assumes their marital status is Widowed, even if they have subsequently re-married.
* Marital status after second marriage
-
LornaCraig
- Megastar
- Posts: 2996
- Joined: 11 Jan 2005 17:36
- Family Historian: V7
- Location: Oxfordshire, UK
-
NickWalker
- Megastar
- Posts: 2401
- Joined: 02 Jan 2004 17:39
- Family Historian: V7
- Location: Lancashire, UK
- Contact:
Marital status after second marriage
It just makes an educated guess, in the same way that it might suggest occupation or birth place for a census entry but it may not match the census entry. It is by no means perfect and you need to check the suggestions and change them if necessary.
If I get time I'll try to improve this for the (very imminent) next version.
Nick
If I get time I'll try to improve this for the (very imminent) next version.
Nick
-
LornaCraig
- Megastar
- Posts: 2996
- Joined: 11 Jan 2005 17:36
- Family Historian: V7
- Location: Oxfordshire, UK
Marital status after second marriage
Hi Nick,
I've just noticed that a red 'thumbs down' has appeared against this topic so I guess this means it won't be 'tweaked' in the next version. It's a very minor issue because the marital status can easily be changed. I was just slightly surprised that on one hand AS cleverly takes account of the date of death of the first spouse to revise its 'educated guess' from married to widowed, but on the other hand doesn't take account of a subsequent marriage to change the status back again.
Looking forward to the next version. Thanks for all the time you spend on it.
Lorna
I've just noticed that a red 'thumbs down' has appeared against this topic so I guess this means it won't be 'tweaked' in the next version. It's a very minor issue because the marital status can easily be changed. I was just slightly surprised that on one hand AS cleverly takes account of the date of death of the first spouse to revise its 'educated guess' from married to widowed, but on the other hand doesn't take account of a subsequent marriage to change the status back again.
Looking forward to the next version. Thanks for all the time you spend on it.
Lorna
Lorna
-
Jane
- Site Admin
- Posts: 8442
- Joined: 01 Nov 2002 15:00
- Family Historian: V7
- Location: Somerset, England
- Contact:
Marital status after second marriage
Lorna, I suspect the symbol is actually flaging Nick's need to look at the code, but I could be wrong.
Jane
My Family History : My Photography "Knowledge is knowing that a tomato is a fruit. Wisdom is not putting it in a fruit salad."
My Family History : My Photography "Knowledge is knowing that a tomato is a fruit. Wisdom is not putting it in a fruit salad."
-
NickWalker
- Megastar
- Posts: 2401
- Joined: 02 Jan 2004 17:39
- Family Historian: V7
- Location: Lancashire, UK
- Contact:
Marital status after second marriage
Hi Lorna
I've flagged it as something that isn't currently solved by the current version I'm developing. Its something which at first glance seems reasonably straighttforward. But what always complicates things whenever dates are involved is it has to be able to deal with missing information and conflicting information. e.g. the individual might be married twice but the death of first partner isn't recorded, or there is no marriage date for the second marriage or there is a date range (between...) for the second marriage that overlaps with the death date of the first partner, etc.
Of course all this can be resolved and ultimately if there is conflicting information it can make a guess, but its the kind of thing that will take me a while to think through, program and test and currently my focus is on getting the next version tested, debugged and released.
As you said it is a minor issue, but I promise I'll look at it sometime! I don't like having the red thumbs-down in the forum
Best wishes
Nick
I've flagged it as something that isn't currently solved by the current version I'm developing. Its something which at first glance seems reasonably straighttforward. But what always complicates things whenever dates are involved is it has to be able to deal with missing information and conflicting information. e.g. the individual might be married twice but the death of first partner isn't recorded, or there is no marriage date for the second marriage or there is a date range (between...) for the second marriage that overlaps with the death date of the first partner, etc.
Of course all this can be resolved and ultimately if there is conflicting information it can make a guess, but its the kind of thing that will take me a while to think through, program and test and currently my focus is on getting the next version tested, debugged and released.
As you said it is a minor issue, but I promise I'll look at it sometime! I don't like having the red thumbs-down in the forum
Best wishes
Nick