Is anything going to be done to improve the TreeShare interface - specifically where, on an individual, all the changes are to be made in the same direction. Example:
I see what your all thinking basically Select ALL changes LEFT to RIGHT or Select ALL RIGHT to LEFT (or check boxes on each item) – might depend a bit on the API connections beind the scenes but might be possible with RM
Kevin
As someone that’s requested this feature several times before I know it’s possible, since for example you can add a person, RM → Ancestry via TreeShare, then add Mom, Dad, spouse, a couple kids, etc, then do a simple update on the person and add all the relations via one click each and a single submit.
I see the logic of not having a “sync” like FTM all the time, as often it’s helpful to review the changes as you share them. That said, not having bulk confirmation on all the time isn’t the same as being able to use it when desired. Like before, I’m not suggesting RM move to an FTM style sync, simply allow those of us that do periodic volume changes has options other that one fact at a time.
I would not like a FTM sync – that problems with that sync is why I left FTM
I would like to be able to select all “items” for a particular person and then be able to check / uncheck what I want to “share”
Yea, that’s pretty much what I’ve been asking for. I would like it two ways, while I personally do nearly all my maintenance in RM and push to Ancestry it would be nice to say on this person select all the Ancestry changes with a single click and pull them as well as select all from RM to push.
It would be nice to have a “global” push and/or pull for changes, for example when you correct a lot of names and/or places, but once per person would be a huge help.
I should note I use FTM once a month or so on the same tree. I do this for a couple reasons. FTM does better job at finding duplicates than RM, and also TreeShare will occasionally add a duplicate on it’s own. Note sure why this happens, but periodically the gender on a spouse will get flipped during TreeSHare, and the next time you TreeShare you’ll get a duplicate spouse as well as duplicate kids. THey’re not duped in RM, but they are in Ancestry, and FTM will find them.
I agree with @kevync1985 that an automatic sync between Rootsmagic and Ancestry would introduce serious problems. However, I also agree with @jelv that the current user-interface requires enormously too many unnecessary clicks.
In a serious attempt to propose a practical way forward, I set myself the objective of cutting out 90% of the clicks and tried to work out how to do it. I posted the results here. That was some time ago, and a few small things have changed since, but I remain absolutely convinced that some change along these lines is throughly desirable and not too difficult. It is also designed as a series of different initiatives that complement each other but could be implemented separately, reducing the complexity and risk of development.
I would be more than willing to work with Rootsmagic development on the details and on testing, as I am sure would others. All it requires is priority from the RM team.
