I'm interested in feedback on this. I mentioned that yesterday I had some issues syncing data and hinted that I thought the whole feature needs an update. As I continued down this path, I'm pretty convinced that for me, this feature is unusable.
I started by downloading my current ancestry tree and then doing cleanup before sharing a family tree with others. I used RM to a) update the "living flag" (which doesn't work - see my other thread) and merge locations. Unfortunately, even the location merge doesn't seem to register unless I give each person focus. So I started at the first "Conrad" and then down arrowed through all 1200 of them, which registered the updates for them (but not non-Conrads).
Now, when I go to do the sync function, I have to do *5* clicks per difference. So if a person had 5 diffs, that's 4*5 +1= 21 clicks to sync them (only need to do the update click once when multiple things change). But really? I had hundreds of manual updates and spent two days clicking. I felt like hiring someone to just work my mouse button and do clicks for me. Never again. I didn't want to stop in the middle though with things so out-of-sync.
There are only a few tasks required in doing any sync. Think of doing merges in a version control system, doing a file backup sync, or doing an ftp upload. All of these common "sync" systems use rules to avoid all this clicking.
For me, the rule should come down to pushing data to ancestry, or pulling data from ancestry. Then you
enable what to do:
- if it's a new place/date event, add it
- if it's dropped, user enables whether to force drop these (or leave alone)
- if the data/place change, change it
- if the flag changes, change it
- if a new person, add them
This would cover 99% of the operations. An executive summary would say "these things will change". That report of changes would be one line per change (right now I have to click to even see each change!). You approve what it plans to do and hit "synchronize".
Yes, it's a risky thing. Yes, people will go "oh no!". This is the way with computers. Backup and backup often. But requiring 5 clicks per change offers little value over just doing edits in two places at once (which I gave up a long time ago).
Or... did I miss something and this is operator error? I watched the video and read the man page, and poked around on the panels and I just can't find a way to do a batch "sync" operation.
Such an improved method might even be useful in the future on say FamilySearch or any future supported online tree system.
Thoughts? Do other people have a different way to keep their ancestry and RM in sync? I love the concept, just not the implementation.