Possible Duplicates and other Red Flags are not showing up on the Tree

LegacyUser

Leroy Roberts said: The "Possible Duplicates" and other red flags are not being shown on a persons Tree. There are far too many duplicates on FS and users can't make corrections or merges if they can't see the Red Flags on a persons tree. Please restore the flags back to the tree. See example below.

LegacyUser

Jeff Wiseman said: Try checking your options on the tree window and ensure that the Show Data Problems checkbox is checked:

LegacyUser

Leroy Roberts said: All the option are checked, except "Invert Colors". I'm using Windows 10/Chrome.

LegacyUser

Jeff Wiseman said: That certainly looks like a problem then.

I looked at the PID in your example, but there were no data problems on it, so I just assumed that you had gone through and fixed them already.

LegacyUser

Leroy Roberts said: Yes, I merged the two duplicates, but the problem is still there. The red flags do not appear in the trees of other "possible duplicate" people.

LegacyUser

Leroy Roberts said: Here's another example. I won't merge it this time.

LegacyUser

Leroy Roberts said: I signed in with my wife's ID and got the same condition, so this is effecting everyone in FS.

LegacyUser

Jeff Wiseman said: This is obviously broken, I hope that Someone from FS addresses it.

LegacyUser

joe martel said: Thanks, it looks broken in all tree views. The team is aware.

LegacyUser

Jeff Hawkins said: Hi Leroy,
You are correct that Possible Duplicates are not displayed on the pedigree views. Unfortunately, the service that computes duplicates can not support the demand of the pedigree views. We had to remove it from that presentation. We hope to be able to offer that capability in the future. For now, you will have to visit the Person page to see Possible Duplicate data problems.  

Jeff

LegacyUser

Leroy Roberts said: Jeff,
The Possible Duplicates were previously displayed in the tree view. There are far too many duplicates and it will be impossible to find any of them without see them in the tree view.

Please refer to my other post "Other Red Flags not showing on Tree View"

LegacyUser

Tom Huber said: I have never seen possible duplicates in any of the tree views. That is using both Firefox and Chrome on Windows 7 and Window 10 over the past several years.

LegacyUser

Juli said: Ditto what Tom said: I only ever use the fan chart, and it has never shown possible duplicates. The only time anything was colored red was recently when that automated process removed a bunch of place standardizations.

LegacyUser

Jeff Wiseman said: Regardless of whether this was supported before or not, the "Possible Duplicate" is identified in the Research Helps as a "Data Problem" (i.e., using icon with the red box and white "!"). The Options settings in the Pedigree view allows you to specifically set it up so that "Data Problems" (identified with the red box and white "!" icon) are all displayed. This is an obvious inconsistency in the interface.

Perhaps the Options list should look more like this:

LegacyUser

Paul said: Makes a good conundrum:
Q. "When is a data problem not a data problem?"
A. "When it's a 'possible duplicate'."

LegacyUser

Jeff Wiseman said: Almost, but more precisely:

Q. "When is a data problem not a data problem?"
A. "When it's a 'possible duplicate' type data problem."

But all sarcasm aside :-) I do understand what Jeff Hawkins said. It seems likely that possible duplicates are calculated "on the spot" for a person record when it is being viewed by going out and "Discovering" the potential duplicates each time the record is viewed or updated. It is likely a a very resource heavy algorithm. Therefore stacking a whole bunch of persons all in the same view (i.e., the pedigree view) will compound that system loading significantly.

LegacyUser

Jessie Hearle said: Just another point
The Family Tree Mobile app fan chart view DOES flag possible duplicates & record hints, but does not show other data problems

LegacyUser

Leroy Roberts said: In my original post I hinted that there are other data problems besides "Possible Duplicates" that are not showing on the tree view or pedigree view . At that time I couldn't find examples of the other data problems (I call them Red Flags which is a better description than data problems or an icon with the red box and white "!"). A few days later, I found some examples. Please refer to my post "Other red flags not showing on tree view" for screen shots.

1. Birth before Mother Could Have Children.
2. Birth before Father Could Have Children.
3. Child Born before Father.
4. Child Born before Mother.
5. Birth after Father's Death.
6. Birth after Mother's Death.

There may be more but I haven't found any.

LegacyUser

joe martel said: Leroy, what are the PIDs?

LegacyUser

Leroy Roberts said: This problem effects all trees, but if you need PID's here are a few:

LBMF-J9J
L1FT-HS2
LB4F-XJS
LKYX-ZH7

Here are more data problem to add to the list above:

7. Possible Duplicate Child. PID is L1FT-CQ7.
8. Birth after Mother's Child-Bearing Years. PID is L56N-G7Z.

LegacyUser

Leroy Roberts said: I'm not too familiar with programing, but instead of calculating data problems "on the spot", can't you set a "bit" for each type of data problem in the person page and display the results in the pedigree view.

LegacyUser

Tom Huber said: That's a good suggestion, but I don't depend upon the pedigree views to determine if I need to resolve a data problem. It is part of the routine I use to periodically check to see if new sources have been made available for my ancestral relatives, especially since new indexes are being introduced quite often.

LegacyUser

Leroy Roberts said: Tom, that's exactly what I do, but I have to find the data problems just like finding the record hints in order to review and attach the hint or fix the data problem.

LegacyUser

Jeff Wiseman said: Leroy,

What you suggest is one way of doing it, but there are (sometimes significant) tradeoffs. It's the difference between a system event occurring which is then processed in real time, or the system "polling" for events that have recently reported and then processing them (possibly out of order because of the polling sequence which is inherent in that approach).

The programming can be problematic and is dependent on how other features and data surrounding it have been implemented.

LegacyUser

Jeff Wiseman said: As Tom mentioned above, I also rarely have the need to see data problems at the pedigree level. I tend to systemically go through the tree and address individuals one at a time. That way I can collect as much information on that one individual and relationships as I can, and then if possible duplicates show up for that individual, I can address them being better informed. I never address any of those issue from the pedigree.

But that is just the workflow that I use that seems to work well for me.

LegacyUser

Leroy Roberts said: As Tom mentioned, he uses the pedigree view to search for new "Record Hints" or sources that have been recently added to his ancestors. I do the same thing, but I would like to see ALL the data problems as well.

Regardless of what I or any patron uses it for, ALL Data Problems should be displayed in the pedigree view, not just the ones that are easy to program. I have given the engineers a list of 9 data problems that are not being shown in the pedigree view.

Joe Martel, please escalate this post to the next level engineer.

LegacyUser

Leroy Roberts said: Joe Martel,

Have you escalated this thread to the next level engineer? Or do you need more PIDs? I'm not satisfied with the excuses that have been given.

LegacyUser

Paul said: Jeff

I have just revisited this topic after having added a few generations of a family with a relatively common surname. I can assure you, the reintroduction of this feature (that Jeff Hawkins suggests might be possible at some later date) would be extremely helpful.

Why does ANYTHING show up in the pedigree / landscape view? One main reason is it being far quicker to pick-up common data problems that likely apply to many members of that branch. For example, a few generations of a couple of branches I am working on nearly ALL have the same problem of having the same "missing standardized --- place". Working back and forth from Landscape I can correct all of these very easily. Tom appears to do something similar when it comes to the (blue) record hints suggestions.

I am with Leroy in really hoping this feature will be (re)introduced, as it will help me so much in finding a common factor (possible duplicates, in this case) that I could easily miss, unless I undertake the very time-consuming process of going back to examine the IDs of every individual I have added (to a branch), to check for possible duplicate suggestions on their Person pages.

LegacyUser

Paul said: Leroy

As you will see in my comments to Jeff Wiseman (above) I would wish to see this feature back in Family Tree, too. However, FS employee Jeff Hawkins already explained the current situation in his post ("Unfortunately, the service that computes duplicates can not support the demand of the pedigree views. We had to remove it from that presentation. We hope to be able to offer that capability in the future "). Maybe Jeff Hawkins is the "next level engineer" and we should accept the situation, as explained, and hope it will be reintroduced at some time - though maybe it won't be soon..

LegacyUser

Jeff Wiseman said: I can see where this could be really useful for some folks, so it should probably be considered by FS.

As I pointed out before, I do not personally need this feature to support the workflows that I use because when I need the information, I am always ALREADY in the details pages for the person. But my real pet peeve is the inconsistent use of terminology. I believe that the inconsistent use of terminology and implementing the same function differently in different places on the site is one of the greatest contributors to confusion.

So If for no other reason than THAT, this should be fixed :-)