Hello.
I am having an issue with Rootsmagic Technical Support and would welce further involvement.
The problem I have encountered relates to new date processing in RM9.
I would preface these remarks by stating that I can only comment on the situation in the UK although I don’t expect other countries to be any different.
RM8 caters for the common situation where a baptism date is known but only the birth year is known. Unless a copy of the birth certificate is obtained (expensive and not practical for obscure relatives) or the birth date is recorded in the Baptism Register, the GRO Index (UK) is the most likely source to provide birth details.
However that index was originally compiled quarterly so is not 100% accurate because of the time allowed to register a birth. In some cases the birth could have taken place in the previous year with the GRO entry in Q1 of the subsequent year.
In the example I quoted to the Tech Team the baptism date was obtained from the Baptism Register and the birth date from the UK GRO Index. Both dates are valid because of the time allowed to register the event. The data input is:
Birth Dec Q 1851
Baptism 30 Sep 1851
Death Jun Q 1852
Burial 28 May 1852
RM8 was quite happy with this situation as it correctly recognized the sequence of events and that a baptism is always preceded by or is equal to the birth date (same for deaths & burials).
RM9 does not accept these conditions and creates an unnecessary Problem Report stating:
Born after Baptism
Burial 90 days after Death
The response from the Tech Team is to Use the Sort date but that only corrects the sequence of events and does not prevent the generation of the Problem Report.
The only way to prevent the Problem Report is to input a specific month rather than the Quarter, i.e, by recording the birth as July it accepts the data matches the RM9 validation checks BUT that is misleading (I accept “Q4 1851” is also misleading but – to me- indicates the correct REGISTRATION date).
I believe the RM8 validation is to be preferred as it results in the correct recording of Events and does not require addition User action to use Sort Date and/or resolve erroneous Problem Reports.
I also believe that a hierarchical approach which always sequence Birth before Baptisms before Deaths before Burials should be used. This would avoid having to use Sort Date when, for instance, an exact Death date is known but only the (assumed) burial month is known.
Interested to hear other views.
Andy