* Order Facts by Sort Date functionality changed in V7?

[jbtapscott]

Just checking that I'm not missing something obvious with the new V7 version of the plugin.

The details with the plugin say that in V7 it will "....turn each LMO Sort Date into a real Sort Date" whereas in the V6 version the plugin created the LMO Sort Date but crucially (to me!), also checked existing Sort Dates and flagged any errors (e.g. where I had changed, say, a Birth Date and omitted to change the LMO Sort Date value). This check does not appear to take place with the V7 version, nor, indeed, does a new Sort Date get added to an event if one did not exist before.

I am aware that adding a Sort Date is now available as a user option and assume this is why the plugin no longer undertakes this task, but just double checking as I found the error flagging very useful in V6.

[tatewise]

Than you for that feedback.
My prime objective was to make all my Plugins available and perform some useful function ASAP in FH V7.
Apart from converting LMO Sort Dates to real Sort Dates, I had not thought any further.

I can see the error checking might be useful, but not sure about adding a Sort Date to every fact, except perhaps where consecutive facts have the same Date or no date.

I have added those ideas to my "To Do List" for review in the New Year.

I guess it would not be too difficult to write a custom Fact Query that checked actual Dates against Sort Dates.

Out interest, why would you now find it useful to add a Sort Date to a Birth event with an actual Date?
In FH V6 the plugin gave every Fact an LMO Sort Date so it was necessary to keep them updated.
But most Facts in FH V7 won't need a Sort Date, so the check is less useful.

[jbtapscott]

Thanks Mike. No real interest in adding a Sort Date to new events (Birth or whatever) as it is mostly unnecessary (as you imply), but my interest is more in the error checking side of things for my existing events. If I make a change to the Date on an existing event (particularly via AS which I use for capture of BBMDB), then I have to remember to go in to the record in FH and make a change to the Sort Date otherwise I could find things out of order.

By way of explanation, what kicked the original question off was my entering a Baptism event with a date that was, in fact, before the "circa" Birth Date I had recorded on the Birth Event for that individual and which resulted in the Baptism Event being placed before the Birth Event (which had a LMO Sort Date generated by the plugin V6 and which had been updated to a Sort Date after running V7 plugin) . Running FH's own Tools / Re-Order Out of Sequence Data left the Baptism listed before the Birth event as, presumably, that process utilises event Sort Dates (if they exist). The V6 Order Facts plugin would have highlighted this.

[jmurphy]

By way of explanation, what kicked the original question off was my entering a Baptism event with a date that was, in fact, before the "circa" Birth Date I had recorded on the Birth Event for that individual and which resulted in the Baptism Event being placed before the Birth Event (which had a LMO Sort Date generated by the plugin V6 and which had been updated to a Sort Date after running V7 plugin) . Running FH's own Tools / Re-Order Out of Sequence Data left the Baptism listed before the Birth event as, presumably, that process utilises event Sort Dates (if they exist). The V6 Order Facts plugin would have highlighted this.

This reminds me that while we do expect to see a birth date before a baptism date in most cases, it is possible to have an individual with a reported birth date which is after the baptism date (i.e. late registrations where the birth date was fiddled).

It's useful when plugins can alert us to oddities like baptisms before birth dates so we can investigate further.