We detected a possible relationship issue in the Family Tree
Originally, my upload to CET was a small test tree of 385 profiles.
Yesterday, I uploaded a GEDCOM of my main personal research tree containing just over 17,000 profiles. It took a while to upload and process, as expected. It seemed to hang at 99% for several hours and eventually completed late last evening.
When I opened it, I was immediately notified of a possible new record for my father. Since that's a profile I've documented thoroughly, I was intrigued. I followed the breadcrumbs and saw my father's post-WWII Navy discharge papers. I have the paper copy.
When I prepared to attach the record to my father's profile, the Source Linker called out an error. I believe that particular error message creates problems rather than helps.
For background, we've discussed the error "We detected a possible relationship issue in the Family Tree" in both the Source Linker group here and in the Family Tree category here. I'm taking the liberty of introducing the question in CET since it has now also surfaced in the CET project.
My father's discharge papers do not mention his parents' names but the error calls out a missing child for my grandfather. The record https://www.familysearch.org/ark:/61903/1:1:6CLN-592M
The error message invites the user to review the names and relationships and attach if sure it is correct. I reviewed everything (again), and I don't understand how the discharge papers could trigger a message about possible unknown siblings of my father.
Could we get some specifics of that error message? What action or absence of information causes it to appear? When it appears, now, it's disruptive to the workflow and, I think, confusing to the user.
Thanks.
Respuestas
-
Áine,
I'm guessing that this is not an issue with SourceLInker, Family Tree or CET. It is most likely a problem with the specific record itself. If you disagree, please let me know.
As such, I will pass this one along to the team that corrects record data to investigate.-Robert Kehrer, sr product manager
0 -
@Robert Kehrer Sorry, but I have to disagree since the error message has popped up on different profiles with different record types as shown on the previous threads I linked.
Still using Windows 10 Pro and Firefox, both fully updated.
0 -
Thanks for pushing back a bit Áine.
It appears that our system has implemented a new feature that attempts to alert users of SourceLinker to spend a little extra time analyzing the situation when oddities are detected by the algorithms. As with any new feature it may have some rough edges given the complexity of tree and record data.
I suspect the team that built this alert is watching these messages, but I'll forward this over to them just in case they are unaware.Robert Kehrer, sr product manager
0 -
Thanks, Robert. You know I'm not shy about speaking up.
It would be great if that team could give us feedback about the new feature. It doesn't show up every time, but at least 3 of us (experienced FS users and frequent Community posters) have encountered it, in very different record sets and locations.It would be helpful to know what triggers the message - especially in those cases when we users can't trace a possible cause.
Thanks.
0 -
We have been told that a ticket was created for this issue, and they hope to have a resolution by the first or second week of December.
0 -
Thank you Stephanie.
0 -
The following duplicate discussion will be merged into this discussion.
1
