I'm in the thick of getting ready to migrate my TMG project to FH6 and want to know how to handle BDM registrations.
The BDM certificates (originals or GRO copies) are easy - they will become multi-media entries linked to a marriage fact (or perhaps become a source in their own right with a citation link from the marriage fact - still debating Method 1 and Method 2).
In TMG the BDM registration events were treated separately, as the act of registration happened separately (and sometimes very much later than) the BDM event itself.
So in TMG I often had a BDM event (e.g. Marriage) and a BDM registration event (e.g. Marriage registration), each with their separate sources and citations. What's the "best" way of handling this in FH6?
TIA ... John.
* BDM registrations
- jimlad68
- Megastar
- Posts: 911
- Joined: 18 May 2014 21:01
- Family Historian: V7
- Location: Sheffield, Yorkshire, UK (but from Lancashire)
- Contact:
Re: BDM registrations
I used TMG for many years and never thought of using the BMD "registration" tags until you just mentioned it. I just considered it to be part of or source for the "event".
I tried to keep things simple and had say 1 tag for a birth and anything to go with it including any details which would either go with the source note or with the birth tag memo, including registartion info. I would have a separate tag and date for Christening. If I did not have a birth date and only Christening and no other birth date reference I would create a birth date of "before the Christening" as I like to create a birth date even if only very approximate/calculated. I have carried this over to FH.
I can't see any BMD registration tags/facts in FH, so I suppose the obvious thing would be to create a custom one. But first off try a direct import and see what FH does to it. It should then be possible to use the Plugin "change any fact tag" to convert to what you want. The main thing with the import is to experiment, look at the log for errors, check how the data has come across, go back to TMG and amend if required (with e.g. TMGutility) and try again.
Others who are more genealogically correct and more knowledge of FH might have a better answer!
I tried to keep things simple and had say 1 tag for a birth and anything to go with it including any details which would either go with the source note or with the birth tag memo, including registartion info. I would have a separate tag and date for Christening. If I did not have a birth date and only Christening and no other birth date reference I would create a birth date of "before the Christening" as I like to create a birth date even if only very approximate/calculated. I have carried this over to FH.
I can't see any BMD registration tags/facts in FH, so I suppose the obvious thing would be to create a custom one. But first off try a direct import and see what FH does to it. It should then be possible to use the Plugin "change any fact tag" to convert to what you want. The main thing with the import is to experiment, look at the log for errors, check how the data has come across, go back to TMG and amend if required (with e.g. TMGutility) and try again.
Others who are more genealogically correct and more knowledge of FH might have a better answer!
Jim Orrell - researching: see - but probably out of date https://gw.geneanet.org/jimlad68
- tatewise
- Megastar
- Posts: 27089
- Joined: 25 May 2010 11:00
- Family Historian: V7
- Location: Torbay, Devon, UK
- Contact:
Re: BDM registrations
Jim is correct. The more usual approach is to integrate the Registration and the Birth Certificate with the Birth Event. Similarly with the Death Event. Marriage registration usually coincides with the Certificate and the Event.
This is where Method 1 wins over Method 2. In the specific Source Record for the Source Document you can include a complete Transcript in the Text From Source field, which includes the Registration Date and Place as well as the Event Date and Place. It also usually links to Multimedia for an image of the Source Document and also images of the GRO Registration entries if you want.
Method 2 does not let you do that without jumping through hoops &/or duplicating data entry, and I believe makes tidy Report layout more difficult to achieve.
Also you should consider ancestralsources:index|> Ancestral Sources and how you would use it in capturing new entries in the future. Ideally you will want the imported TMG data to match future AS created data.
Go ahead and experiment with your TMG direct import, but wait a while until some of the teething troubles in FH V6 are resolved. We know that Calico Pie are aware of some of them, and an update is probably not too far away.
This is where Method 1 wins over Method 2. In the specific Source Record for the Source Document you can include a complete Transcript in the Text From Source field, which includes the Registration Date and Place as well as the Event Date and Place. It also usually links to Multimedia for an image of the Source Document and also images of the GRO Registration entries if you want.
Method 2 does not let you do that without jumping through hoops &/or duplicating data entry, and I believe makes tidy Report layout more difficult to achieve.
Also you should consider ancestralsources:index|> Ancestral Sources and how you would use it in capturing new entries in the future. Ideally you will want the imported TMG data to match future AS created data.
Go ahead and experiment with your TMG direct import, but wait a while until some of the teething troubles in FH V6 are resolved. We know that Calico Pie are aware of some of them, and an update is probably not too far away.
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry