Tree2Tree
I appreciate this is all in the VERY early gestation, but what was offered in the way of the how it might work by @Robert Kehrer got me thinking….
'Users will be alerted when an individual in their tree has a high confidence match vs an individual in another tree.'
Can I take this to mean 'another tree' includes not only CETs but also FamilyTree? Hmm…. what about Genealogies? I admit I tend to forget that Genealogies are a resource to be considered.
'If so, they will be able to create a new "empty" person in their tree and copy all of the person data, notes, source and memories from the matched tree person onto the new person in their tree.'
Sounds like a 'two-step' process. My initial thought is that it should be a 'grab it all' and then sort it out vs a 'pick and choose' after the PID is created in my CET. Either way still gets the job done, depends on how one does these sorts of things as to which approach would be to ones liking…
'This will also put a note on each of the persons in the two trees indicating that a user has determined them to be the same person…..
Long term, these notes may help alert users when meaningful new data is added to one person. ex. If I conclude that "Mike" in treeA is the same as "Michael" in treeB and later someone adds new marriage info and a source to Michael in treeB, I may be alerted and can align and copy that data into my tree….'
If treeA is my CET, I'd be notified of changes to Michael in treeB. The manager of treeB would be aware thru a 'note' that I've established this 'connection'. It would be useful if the manager of treeB could easily navigate to Mike in my CET thru a link of some kind included in the 'note' they've received.
If Tree2Tree was implemented between FamilyTree and CETs, seems like I should be able establish this 'watch' feature with a FamilyTree PID [this would be above and beyond the 'Follow' function].
Either way, these notifications need to be made not only when viewing 'Mike' in my CET, but also in an additional 'global' sense which would show all notifications for any/all PIDs in a particular CET.
Looking forward to watching the CETs evolve. Thanks for making this happen
Comments
-
- Match vs Family Tree: Yes Your CET will be matched vs most other trees on the FamilySearch system including other user's CETs and Family Tree.
- vs Genealogies?: The data in Genealogies will be moved over to the new system and eventually Genealogies will be shut down. Each collection of tree data in the current Genealogies has a different model for how the data will be transitioned, but that process is underway.
- Two Step Process: It's a two step process behind the scenes. I noted that because I wanted you to know what was actually happening. For the user it could be as easy as clicking a button and sliding a person over the same way you do it in SourceLinker today when adding a person from a record. That would bring over all notes and sources, etc. Of course the new tool will allow you to review each person and each life event a little deeper if you choose, evaluate all the sources etc and bring over just those you deem to be accurate.
- Navigate from treeA to treeB through the link: Yes, exactly. Just the same way that you can click the 1950 Census source link on Howard in Family Tree and navigate to the Howard in the census. You may want to go to the other tree and see and navigate the pedigree view -or- you may want to open the two tree people in the new tool to compare Howard and his family and to copy data between the trees. I used the word "note" to not be too techie, but it is actually it is the same kind of referenceLink that we put between a tree person and a record person.
- Watch Feature: Yes. That is the long term vision. If you conclude that your Howard is the same person as my Howard and I add some meaningful new conclusion, data and sources to my Howard…you could be alerted. That feature won't be there initially, but it is on the roadmap.
0 -
I think perhaps this is a related query. This is my first time using the CET, and my main source of data for the tree I am trying to create is, actually, the Family Search Tree. I've run into a couple of things that I'm not sure I understand.
First, I received an error message when trying to add a person to the CET from a source document. The error said the source was already attached to another person in a different tree… which appears to be the Family Search Tree. I was able to create a new person in CET, though I think I had to go back a step and add them to the tree manually, rather than via the source.
I assume that the this is by design (CET people are supposed to have their own (private) ID number, even if they are the same actual human beings that are in the Family Tree).
But I wonder how to connect the CET ID to the family search ID in order to link the information (in both directions — so my CET tree can get info from the Family Tree without recreating it, and so the Family Tree can get information that I obtain elsewhere and add to the CET tree. I'm concerned the CET project creates a whole bunch of duplicate people in the Family Tree (which I have worked diligently on reducing over the years… :-)).
Hopefully this is helpful…
[Error message]
Hiram Houston (Father)
Detach
This source is attached to someone else in Minott-McQuarrie: Hiram Hersey Huston L1GZ-P5N.
Details
Lizzie Halbrook (Mother)
Detach
This source is attached to someone else in Minott-McQuarrie: Elizabeth J Holbrook GS1F-3D7
-
0 -
@Brenda Cummings Thank you very much for agreeing to test drive our early access CET. It is still early in the process of creating the CET and all parts of it are not yet fully functional and supported. The Tree2Tree feature is one of those items. It will indeed let you compare and match persons from CET, FamilyGroup Tree and FamilySearch Family Tree once it is added.
Potentially, one person might be in the FamilySearch system several times while alive. Once in FamilySearch Family Tree, in a FamilyGroup Tree, and in a CET. That is the nature of the beast and must needs be to ensure privacy of living persons.
As far as attaching a single source to more than one person in a tree, I will pass that issue on to our engineers.
0 -
I read your post. It appears that you surface two different issues: 1) Attaching a person is a historical record to a person in your tree. 2) Attaching a person in your tree to a corresponding person in FamilySearch Family Tree.
Issue 1: Attaching a person is a historical record to a person in your tree.
The record attaching feature is built to ignore record person attachment in other trees. IOW: You should be able to attach "Bob" in a census record to Bob in your tree using the SourceLinker tool without any error, even though Bob in the record may already be attached to Bobs in other trees.
I'm assuming that your tree is called Minott-McQuarrie and I checked and confirmed that both Hiram's PID L1GZ-P5N & Lizzie's PID GS1F-3D7 both appear to be in the FamilySearch Family Tree and not in your CET. What that means is that you have identified a potential bug. It would be very helpful to us in diagnosing this error if you could go to the specific record that you were attaching (you can do this by going to the SourceLinker if you wish (it appears that is where you were when you saw the error) and providing us with the URL to the SourceLinker page that has both the record and the tree person in CET loaded.
Issue 2: Attaching a person in your tree to a corresponding person in FamilySearch Family Tree.
This feature is not yet delivered yet. We are actively working on it. When delivered you will be alerted to matching persons between your CET and FamilySearch Family Tree, you will be able to align the person, and surrounding family and evaluate all the data to determine if they are indeed the same, and if so you will be able to copy data, and sources between trees. This will also place a "link" between the two people in each tree documenting your conclusion that they are the same.-Robert Kehrer, sr prod mgr, familysearch
0 -
A portion of this discussion about Adding a person to CET SourceLinker has bee separated to another discussion. Please add additional comments to this discussion:
0
