True Shared Facts
Posted 11 October 2017 - 08:44 AM
Posted 11 October 2017 - 09:35 AM
Shared facts have caused me no end of problems. My issues with this topic have been exasperated greatly since I started using the new RM - Ancestry tools, WebHints and TreeShare.
Basically, I did not understand the true nature of shared facts when I first started using RM. Then, when I tried to load my tree to Ancestry, I discovered the whole host of issues discussed previously in this forum. Anyway, now the problem is how to fix the mess. As I understand it, I need to convert all shared facts to "stand a lone" facts for each person. Obviously, that is a big task. I've also changed to that practice going forward.
I've read in this forum about "drag and drop" methods, etc. but that also takes quite a while to do. Currently, I'm using the following method to "copy facts".
1) share a fact from person A to person B
2) go to person B add new fact for person B with same date
3) copy data including sources from shared fact to new fact (they will appear one above the other)
4) tag any media to Person B and the event for the new fact
5) remove person B from the share for the original fact for person A [this removes the share from person B and leaves the new fact for person B]
This seems to work fine with no issues, but obviously takes time to repeat for all the persons for whom you are setting up the same fact.
One tool that would really help with the conversion of shared to individual facts would be a "fact copy" utility. For example, if a person has a wife and thirteen children, a census fact could be created for the head of the household, and then copied to each member of the family as individual facts. To retype all this data takes forever.
Posted 11 October 2017 - 10:55 AM
I'm currently in the process of re-entering an astounding number of events because of this problem. I assumed the shared facts in RM would work as they did in TMG.
Please take Jerry's suggestions to heart and make some serious improvements to this functionality.
Posted 11 October 2017 - 03:39 PM
We've wrestled with the shared events incompatibility with other systems and the absence of any mechanism to post the same fact/event to multiple people. Enhancements have been on the wishlist for many years. And 'temporary', user-developed outboard SQLite workarounds have been available for almost the same length of time.
Posted 12 October 2017 - 11:13 AM
As a former TMG user, I too fully support this request for true fact sharing.
Posted 13 October 2017 - 10:21 AM
As I have previously stated here, I would like to see a "copy fact" utility development given a high priority.
Posted 14 October 2017 - 12:04 PM
Because I'm somewhat adept with SQLite, I would explore the potential and drawbacks of a couple of scripts I developed long before Ancestry TreeShare came along. One copies an event to a group. The other converts shared events to individual ones.
Posted 14 October 2017 - 12:22 PM
The purpose of the Shared Facts message was more for me than anyone else viewing my tree in Ancestry. My Ancestry tree is private anyway. I see your point. It may be actually be less work to create individual facts to start with, than to try and fix shared facts later.
I have tested the SQLite script for converting shared events and it does handle that OK. However, I'm somewhat reluctant to use shared facts and keep having to use a 3rd party software to change them after the fact. For just me, in RM, it It is certainly easier and faster to use shared facts, but then you have all the drawbacks for sharing the tree with someone else on another platform.
Best thing to do I guess is probably to wait for the fact copy utility, and just create individual facts in the mean time. (Oh, why does my Tree have so many families with 12 or 13 children .... )
Thanks for the comments.