Geni merges for dummies ...

Annelise, thanks for your thoughtful description. Your very last paragraph sums up why we allow you to think that you're merging through the entire process -- because you are, you just need a little help from someone who has permission to merge a profile that you do not have permission to merge. The end result is the same.

(There's also a technical reason, which is that determining whether or not you have permission can be computationally expensive; so we wouldn't be able to do it for large sets of profiles / matches at once. Rather, we save that computation until you get to the side-by-side comparison of only two profiles)

AH – Justin explained that by "... I went a different direction" he was referring to choices in Project Statement for Working with the Big Tree. My response / reaction is:

I think using the word "merge" for all three situations will cause at least as much confusion as it eliminates. I definitely agree the terminology in the FAQ I referenced is abysmal.

My suggestion - use "merge" for completing the merge (well, actually - for the user action which triggers the software to merge the profiles). Would definitely use for both situations where there is a 'hanging' or 'pending' merge and your approval causes it to happen, and situations where your approval alone causes it to happen. In either case, the two profiles are now merged. I see no reason for separate words here.

However, I would suggest using 'start a merge' or 'request a merge' or some such for situations where the merge has not happened and can still be cancelled.

As a user, I think it is important for me to realize when my action is just going to create a request (which can be changed or rejected), and when it will accomplish something with no need for more input (especially when it will then not be able to undo it).

Example: On my tree, one relative saw and clicked on "Yes" for a pending merge on a profile I managed - he had no idea that would complete the merge, thought it would result in message being sent to me, then I would approve it or not. By just using "merge" I fear you will make it less likely folks will realize which is which - or is there some other way you are helping them to realize this difference?

Rationale 2: Folks going back and reading the Blogs, etc. will come across the announcement that Curators now have the ability to merge profiles/Public Profiles, later they will come across the announcement that the ability to merge Public Profiles has been extended to all PROS. I believe in the announcement and in most discussions this was simply referred to as "merge" - it was understood there that this meant 'merge without needing anyone else's permission'. Then later it was announced as a Change that if a profile was in a separate Tree, a merge could not be done without the permission of someone on that tree. By using the one term "merge' - how will folks understand these past statements (and discussions about them)?

The FAQ I refer to above is http://help.geni.com/entries/472609-what-is-the-difference-between-...

According to it the photos linked to in it:
when you do not have permission to request/complete the merge, the choices are “Yes, request to merge” and “No, remove match”

BUT when you do have permission to complete the merge, the choices presented to you are “Yes, merge these profiles” and “No, they’re different."

Mike -
1] if I understand your comment above, then you are not in favor of the 'explanation' and terminology given in this FAQ. Have you seen it?

2] if the Program can tell the difference, demonstrated thru the the differences in wording shown above - how about making it a little more explicit - explicitly say in the second case - "If you click “Yes, merge these profiles” then they will be merged - No further approval will be needed."

Lois I'm very much in favor of making the site more descriptive / explanatory. My main point above is that even assuming no technical limitations, it may be easier to understand if users think of this as merging, whether done entirely by yourself or with the help of others, via requested merges.

I agree with Mike. "Merge" consists of several steps. You may not be able to do all the steps yourself, but it is still a merge. It requires two managers to work together. Some give blanket permission up front - some retain control. Perhaps showing the steps (like when I buy something online it shows where I am in the process) would help.

This discussion started (in previous thread) with a reference to the Wiki - http://wiki.geni.com/index.php/Curators where under "Curators have the following privileges:" it includes: "Edit and merge any Public Profiles"

This statement in the Wiki was written before Pros were given the ability to Edit all Public Profiles, which came before Pros were given the ability to merge all Public Profiles, which came before the change to the current policy, where to merge a Pubic Profile in a Separate Tree with one in the Big Tree requires the permission of someone in the Separate Tree.

When this statement in the Wiki was written, it meant Curators could merge Public Profiles without any other permission needed.

When I questioned if it was still true that Curators could “merge any Public Profiles” I was assured the statement was still true with the explanation, “a Curator can merge any two public profiles. If one of the profiles is public but in a stand-alone tree, the merge is not automatic. It requires the other manager to approve the merge.”

To me, it seems unnecessarily confusing when a statement remains true due to the change in meaning of one or more words in it.

We need some way to distinguish ‘you can merge them, no other permission needed’, from whatever you call the other situation – whether it is two terms, or using the longer phrase at times to spell it out, or etc. And when we read statements written in Blogs, Wiki’s and etc., we need – or at least it would be nice to have - a way to tell which meaning is/was being used.

"For a limited time":

http://www.geni.com/blog/todays-release-approving-merges-and-projec...

Approving Merges

We’re making it a little easier to grow your family tree by expanding permissions for approving merges to everyone. For a limited time, all users will be able to approve a merge for free. This means that Basic and Plus users will be able to complete merge requests for private profiles and unconnected trees and finally merge into the World Family Tree!

Remember, this enhancement is only for accepting merge requests. Basic and Plus users will not be able to request merges. The merge permissions for Pro members will remain the same.

Wow! That's a biggie (at least, from a Geni 2012 perspective).

The wording confuses me. Can they accept only one merge, or many?

David - you are interpreting "a merge" as "one merge". That sentence on its own might mean that. In context, I think not. You highlight the importance of good writers, and of testing announcements on a select audience before public release.

Sorry about the confusion - they can accept any requested merge for profiles they can edit.