Hi… Thinking of changing my user-name to ‘Troublemaker’… but…
Why must I first enter a Fact with date, enter a second Fact with date following the first date, then need to mess around with the Sort date to get them in the right order IF logic can easily understand proper date order. Adds to frustration… I’m sure many of you have seen this as it is also present in RM11, and probably before.
Below, I entered these in the proper sequence; “bef 20 Jul 2002” and then “from 20 Jul 2002 to 17 Feb 2017”. After entry, the second one jumped above the first!
It is obvious to the viewer that this is not the right sequence. Can’t the software recognize that? Is this the reason the Sort date field was added in the first place, to cause the user extra data entry?
sort seq
if date like 'before' then row-position = date - 1,
if date like 'between' then row-position =
first-date + (second-date - first-date)/2
if date like 'after' then row-position = date + 1,
if date like 'from' then row-position = first-date + 2
if date not in ('before','aft','from') then row-position = date
end sort seq
I’d love to see a fux where the user only needs to rarely be involved in sorting the date positions of facts.
In the tags at the top of this post, I put both feature-request and issue. But, this is truly a display logic bug.
A little background on the 2 examples above. The couple (family) lived at the place together until the husband died, leaving the wife to live at the place for several more years. Thus, I needed 2 facts…
I would really like software that does my research for me so that I don’t have to expend any effort in doing it myself. I keep suggesting and asking for a new feature but the developers (not just of RM but other packages) keep ignoring me like I am making stupid suggestions or something.
This is a very old issue and I doubt you will find disagreement as regards the additional unnecessary effort required.
Some software packages follow a logical sorting of life events, We all know Birth comes before Baptism, Death or Burial etc. even if all occur on the same date, software should apply the same simple logic.
My suggestion would be to raise a support ticket and keep your ticket number safe so you will be aware of any updates.
Not saying I agree – but having SORT date field allows anyone to get things sorted in the way they want without needed any rules or logic-- its a “work around” the delivers the results - I suspect too many people would disagree on whatever method RM used so this “solves” that
With respect, knowing that numerous requests for such an “auto-sort” arrangement mechanism have not been acted upon by the programmers, does that not signal a programmatic reluctance?
They obviously decided that adding a tranche of code that would execute the processing of all facts for a particular person every time a particular fact or facts is/are added, …is a less than desirable endeavor.
Screen input for particular fact(s) being added, Interrupt that action of adding a Fact to Read the database for all Facts for the Person, Capture the current Fact order, Determine which Facts w/o Sort Date were added before any with Sort Date, Write a new Fact order to database that accounts for the “auto-sorting”, Refresh/Update screen display of Fact order. Repeat for every Fact added. More code to be maintained and might possibly interfere down the road with feature extensions or redesign, etc.
exactly (and does not cover not one the variations / scenarios of 20K users. Even if something might be simple to implement - it might not be simple so support also.
I for example have family in my own town that have resident facts after death – that is normal and expected but more importantly desired this means I do not need to do anything – if I did the sort would fix it. So here is a question “why might I have legitimate Resident facts after there – and here is a hint usually one or two years after death?”
I agree, however being with Family Origins (1997) through to Rootsmagic 7 (2020) I was simply trying to add some reference for those new users who may not be aware of the historical wish.
Escalation isn’t the issue. This really boils down to the author of the programs preference in handling facts with the same date. Having a sort date and the ability to add -1, -2, -3 to control facts with the same date is the method we use.
Not in some of my Irish civil registration entries. I have many instances where the baptism occurred before the birth date recorded in the civil register. Because there were penalties for late registration, a later birth date was sometimes given to make the registration appear timely.
there really is NOT one solution where most everyone is going to be happy (or even reasonably satisfied in some cases) – I guess the SORT date field was the best “work around” to most anyone needs without creating too much confusion. It may be far from perfect in many cases but should work when used correctly.
That’s a weird one, I know the Birth date and registration date are quite different, know the registration rules and can see misreporting could happen as we all see in research.
However the OP frustration was Normal operation as opposed to anomaly
I am aware of one Burial before Death and then there’s the famous lady who was buried twice, still these are anomalies.
I guess I was thinking the solution could work on two levels. First, automatically apply the assumption that certain date phrasing makes a sort obvious and apply that (e.g. before is followed by current which is followed by after, etc.), followed by exact same dates being automatically sorted based on realistic event flow (e.g. christening never happens before birth, burial (hopefully) never happens before death, etc.).
In the idea I was having, the current Sort date field would not go away… It could then be used to override any of the above logic.
That would allow for ease of use by users that are not necessarily tech savvy who might not understand (yet) that they can alter the Sort date.