Family Group Trees inviting flow should not put so much on the admin (building out the tree)
I don't think I saw this discussion in here yet, so hopefully this is helpful.
Currently, the invite flow is to essentially build out the tree in order to invite someone into the group tree. The admin must import/create tree persons in the tree in order to send a personal invite for an active user to "claim" that tree person as themselves. This is a bit backwards & puts far more effort on the admin to get people into the group. We should not need to build someone into the tree before we can invite them to it. The relationship building should come from the users who join.
A better flow would be to have a generic join link to share with all family at once or allow admin to lookup contacts/users by username or email & select multiple to send invites to at once. This one-by-one personal invite flow is very tedious. Anyone should be able to click that link & join the group and THEN import/create their own tree person (& import their private living family) & select what relations they have within the tree. The admin won't always know where an invitee fits in the tree beforehand, so they should leave it to the invitee to determine. Relations for new invitees should also be optional so friends or research helpers can access & help with the family group tree without having to have a fake relation in the tree in order for them to join. Tree building should come after users join, not before.
コメント
-
.. I think that is not possble with - especially european - privacy laws .. you wouldn´t need a separate family group tree section .. could be done in the normal familytree of adam and eve without separating the living from the "living that live on the other side of the veil" right now ;-)
0 -
Yes, that's my point. Group admin shouldn't need to add living people to the tree before inviting them. They should be able to invite them first so the new group member can add what personal information they wish.
0 -
Consider what the scope of your tree is. The purpose of Family Group Trees is to share information on living individuals with other living members of the family, privately. It is not meant to be a descendancy tree for all living descendants of an ancestor who was born in 1700. Try out the Together by FamilySearch experiment and see what information it leads you to include. Experiment with the new process of tagging Memories. See how those processes affect your thoughts on the scope or size of your Family Group Tree.
Consider that if you, as admin, don't know where in the tree an invitee should belong, you might be thinking of too large of a tree and you might end up sharing more information than you intend to by building a Family Group and Tree of that size.
0 -
We understand the intent of this comment and for a different model of shared trees that may make sense.
@AnneLoForteWillson provided a very good explanation. Please allow me to expound as the Product Owner
Please Note:
1) The purpose and design of Family Group Trees as a subset or added feature of the Public Family Tree is to provide CLOSE family members to share a living tree and memories. It is not to build a large PRIVATE tree that includes deceased persons. So it is different that other systems that have private trees that can be shared with other users. CLOSE is defined as 2-3 generations in most cases or close enough you know that person and where they fit in your living tree. That is by design and feature requirements.
2) The invite model is designed specifically for 1) inviting close family members and 2) that each person you invite will have an link or associated person in the tree. A single one time invite works well to make sure that users and tree person are linked correctly and that only the users you want in your group are allowed to join. It is a private group and the admin should only invite family members that understand the intent or reason the group admin created the group.
3) We are sorry if this model does not fit the intent of this comment. If that is what is wanted, there are many other products that support a large shared private tree, such as My Heritage, Ancestry and many others that are great and recommended options as partners of FamilySearch.
1
