Anything missing?

Do you want this to be a "resource project" or a "work project"?
I've got a couple of tree fragments that are not in the Big Tree; when I saw the description, I thought perhaps this could be a project where I add profiles from such fragments and ask for help in connecting them.

But the project page so far sounds like a "resource project" - somewhere I go to get advice.

Somewhere to get advice (resource project). Would using discussions in this project be helpful for "help connect this fragment?"

I see there was a project - http://www.geni.com/projects/Isolated-trees-Isoleeritud-puud/3473 - but it looks suspended.

I know I definitely read -- if someone on a Stand-alone Tree sees suggested match to a profile in their Tree which they manage and/or is part of their Max Extended Family to a Public Profile in the Big Tree - then they can simply click "Accept" and the merge will go thru - nobody on the World Tree needs to say "okay" - tho I think may need to be Pro to see the suggested merge - not sure about that.

So no, there are not "two steps to connecting a standalone tree to the Big Tree" --- To say one of the steps needed to be part of the World Tree is to " Send / accept a collaboration request" is just plain wrong.

Or did you mean that they if they did that, then their collaborator might to the rest of the work to connect the Trees? Which is very different from needing to do both steps. In other words - doing one or the other step may be sufficient.

I would have to walk through a case to clarify. Maybe next week.

As far as I know the standalone tree merge DOES need to be approved by a member of the world family tree.

If both members are in standalone trees, their trees will be merged, but the tree is still standalone.

If the standalone tree members "then" merge an ancestral profile into a match that is in the world family tree, "then" (both members) connect to the world family tree.

Merging does NOT have anything to do with the PRO permission structure. That point needs to be very clear.

Lois, your questions focus around clarifying the "collaboration" permission, and I am taking that off my plate to work through. As a curator I will never be able to answer adequately from my personal experience with Geni, and that's where I write from.

Re: "Merging does NOT have anything to do with the PRO permission structure. That point needs to be very clear. " -

The point below, quoted from a Dec 2012 Help Comment posted by Geni Support Team Admin also needs to be clear (or if no longer true, that clearly documented) -

"Please know that merging duplicate profiles and tree matches are two different features. Merging duplicate profiles is now free. Tree matches which shows a list of profile matches in other trees is still a Pro user feature. " [found in comments here:http://help.geni.com/entries/22503176-Merge-Trees ]

Yes, Lois: the intent, as I understand it, is that Basic members can "respond" (if you will, by accepting) to proposed merges (i.e.: the side-by-side comparison panel).

However, the more extensive tools for "cleaning up" a branch of the tree (e.g.: lists of potential matching profiles) are Pro features.

Mike Stangel - I hate to see a Project firmly stating something that I believe is not true - so would you please clarify -

If you are in a standalone Tree – and want to join the World Tree -
1) Is "Collaboration" actually needed to join the standalone tree to the Big Tree?
and
2) if you see where one of your Profiles matches a Public Profile on the World Tree - Does the standalone tree merge need to be approved by a member of the world family tree?

It is unnecessary to collaborate with anyone in order to join the World Tree. You can collaborate first, and then do step 2 - "Send / accept a merge request" - OR you can just do what is listed as step 2 without ever collaborating - ie just "Send / accept a merge request"

http://www.geni.com/blog/todays-release-approving-merges-and-projec...
the blog they link to is: http://www.geni.com/blog/todays-release-approving-merges-and-projec...

"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!" - this was back in August 2012 - since then they have made it permanent. And, from what I have read, not as limited. But even then - you may notice that no collaboration is necessary.

On the other hand, whether separate Tree or World Tree, this is extra reason for Basic Users to want to Collaborate:

http://help.geni.com/entries/22033178-September-17-Search-enhanceme... - "Basic users may now access profiles they are collaborating on from the Search results"

Again - no collaboration necessary to merge in to World Tree -

http://help.geni.com/entries/469660-how-can-i-merge-my-tree-with-a-...
. #3 - explicitly mentions merging of profiles outside your tree --
"3. You may also manually merge duplicate profiles within your tree and also any duplicate public profile outside of your tree by using the "Merge This Profile" feature under the "Actions" tab. (Tip: View the other profile first to ensure that it appears on your list of recently viewed profiles.)"
and which includes update to prior link, where free merges were temporary - with comment -
"Note: As of November 28, 2012, merging is free! Please note Tree Matches are still a Pro feature."

This gets tough, in part because we've been playing around with permissions to get the best experience for everyone, when trying to get new users into the big tree.

Merge permissions are the same as "edit basics" permissions. Everyone except curators can merge/edit basics if:

1. You are the manager OR there is no manager and you can take over management, OR
2. The profile is public and within your max family, OR
3. The profile is managed and has been tagged in a project that you have joined, OR
4. The profile is private and a manager is in your family group, OR
5. The profile is public and a manager is in your collaborators, OR
6. The profile is public and in the same tree as you, OR
7. The profile is public and in the big tree AND YOU ARE A PRO

Note that the last condition does allow Pro users to merge into public profiles in the World Family Tree, even if they themselves are not in the big tree.

Saying "Merging is free" is not the same as saying no merge request is necessary -- just that you don't have to be a Pro to merge (if you have permission) or request a merge (if you do not).

Mike Stangel - for some reason, this part confuses me - could you confirm if I have understood it correctly:
"7. The profile is public and in the big tree AND YOU ARE A PRO

Note that the last condition does allow Pro users to merge into public profiles in the World Family Tree, even if they themselves are not in the big tree." -

Is it saying - a PRO on a Separate Tree can merge any Profile that is in their Max Family and/or that they manage and/or that is both Public and in Their Tree - they can merge any and all of these into a Public Profile on the Big Tree - without its needing to be approved by anyone else - and without needing any Collaboration?

Is it also saying that a PRO on a Separate Tree can merge two Public Profiles in the Big Tree (again, no approval needed from anyone else, no Collaboration needed)?

Lois, yes that's what I'm saying.

That last condition puts paid to any hope I had of preserving my timelines.

Erica - collaboration is different for Pros - that's the part I missed also.

... and which is why the idealized 'future state' could be that all valid historical profiles are Master Profiles (MPs) and (not implemented yet) have locked relationships between them -- because MPs can't be merged with each other. Additional connections can be made to them, but the "MP'd lineages" couldn't be tangled up themselves.