Changes made in FamilySearch

In order to preserve the promise of transparency and open communication, the change log records changes to topics made by both customers and employees. Anyone can dispute a change by clicking the "Dispute" link and entering additional details.


  • May 27, 2016 02:44
    Loretta Storey, the poster:
    Reason: removed by the poster
  • May 26, 2016 21:46
    Don Martin Thomas, the poster:
    Reason: removed by the poster
  • May 23, 2016 02:37
    Don Martin Thomas, the poster:
    Reason: removed by the poster
  • May 22, 2016 12:23
    Jessie Hearle, the poster:
    Reason: removed by the poster
  • May 22, 2016 12:23
    Jessie Hearle, the poster:
    Reason: removed by the poster
  • May 18, 2016 16:43
    joe martel
    Changed reply in topic of How to handle incorrect records by joe martel to My example above is correct. The short answer, is put your correction in the Notes field of the Source.<br /><br />This next part is going to get technical so you can ignore this if you desire.<br /><br />Make sure you don't conceptually equate the Source URL of the Source to the Source object itself. The Source object is independent and a user can operate on its data (Title, URL, Citation, Notes). That Source object can be Attached to other objects like Person and Relationships.That does not alter the Source object data. That Source's data does not replicate to other Source objects. An Attach&nbsp; is done by making a SrcRef that related the PID of the Person to the SourceId of the Source. BTW: the Reason and tagged fields are kept in that SrcRef. When you Detach the Source that SrcRef is deleted. <br /><br />The SourceLinker does some magic and constraining so that a Search hit to a Persona in a record has a unique URL. It plunks that URL into the Source field of the Source it creates. It will create a new Source for each Persona that shows up in a family of Personas like in a Census record if you let it. SrcLinker obscures the Source creation. Then after it creates that Source it will Attach by creating the SrcRef, Only the Attach Reason is seen by the user. You go to the Sources for that Person and at the top of the Source list is the most recently created Source. There you can edit that Source's Notes field. <br /><br />Personally I like images as Sources, so I tend to create my own Source to the image, type in the metadata in the Notes field of the Source, along with corrections. I attach that Source to every person in that image (family members). This way I'm closer to the original evidence, as opposed to an index which is derived.<br /><br />Here is the example of the Source I created, modified the Note and attached to multiple Persons. Note the sourceId parm in the URL<br /><a href="https://familysearch.org/links-gadget/linkpage.jsp?&amp;entityId=LD5X-QJT&amp;sourceId=9F9R-LQ3&amp;edit=false#esp" rel="nofollow" target="_blank" title="Link https//familysearchorg/links-gadget/linkpagejspsourceId9F9R-LQ3editfalseesp">https://familysearch.org/links-gadget/linkpage.jsp?&amp;entityId=LD5X-QJT&amp;sourceId=9F9R-LQ3&amp;edit=false#esp</a>.
  • May 18, 2016 16:40
    joe martel
    Changed reply in topic of How to handle incorrect records by joe martel to My example above is correct. The short answer, is put your correction in the Notes field of the Source.<br /><br />This next part is going to get technical so you can ignore this if you desire.<br /><br />Make sure you don't conceptually equate the Source URL of the Source to the Source object itself. The Source object is independent and a user can operate on its data (Title, URL, Citation, Notes). That Source object can be Attached to other objects like Person and Relationships.That does not alter the Source object data. That Source's data does not replicate to other Source objects. An Attach&nbsp; is done by making a SrcRef that related the PID of the Person to the SourceId of the Source. BTW: the Reason and tagged fields are kept in that SrcRef. When you Detach the Source that SrcRef is deleted. <br /><br />The SourceLinker does some magic and constraining so that a Search hit to a Persona in a record has a unique URL. It plunks that URL into the Source field of the Source it creates. It will create a new Source for each Persona that shows up in a family of Personas like in a Census record if you let it. SrcLinker obscures the Source creation. Then after it creates that Source it will Attach by creating the SrcRef, Only the Attach Reason is seen by the user. You go to the Sources for that Person and at the top of the Source list is the most recently created Source. There you can edit that Source's Notes field. <br /><br />Personally I like images as Sources, so I tend to create my own Source to the image, type in the metadata in the Notes field of the Source, along with corrections. I attach that Source to every person in that image (family members). This way I'm closer to the original evidence, as opposed to an index which is derived.<br /><br />Here is the example of the Source I created, modified the Note and attached to multiple Persons. Note the sourceId parm in the URL<br /><a href="https://familysearch.org/links-gadget/linkpage.jsp?&amp;sourceId=9F9R-LQ3&amp;edit=false#esp" rel="nofollow">https://familysearch.org/links-gadget/linkpage.jsp?&amp;sourceId=9F9R-LQ3&amp;edit=false#esp</a>.
  • May 16, 2016 19:20
    joe martel
    Changed reply in topic of Replace information from source to individual record using source linker by joe martel to oops, here's the right thread:<br /><a href="https://getsatisfaction.com/familysearch/topics/add-ability-to-edit-event-on-source-linker-page" rel="nofollow" target="_blank" title="Link https//getsatisfactioncom/familysearch/topics/add-ability-to-edit-event-on-source-linker-page">https://getsatisfaction.com/familysearch/topics/add-ability-to-edit-event-on-source-linker-page</a>.
  • May 16, 2016 19:20
    joe martel, the poster:
    Reason: incorrect info
  • May 16, 2016 17:03
    joe martel
    Changed reply in topic of Incorrect ship attributed to passenger record. by joe martel to Tom, Here's how this work. A Source has the 4 fields, Title, URL, Citation and Notes. THose are seen whereever that Source is viewed. That Source can be attached to multiple Persons or Relationships. The Reason is specific between that Source and one Person. So here is the Source on Gustave <br /><img src="https://d2r1vs3d9006ap.cloudfront.net/s3_images/1416897/4323-1t3z8z_inline.png?1463418146" title="Image https//d2r1vs3d9006apcloudfrontnet/s3_images/1416897/4323-1t3z8z_inlinepng1463418146" /><br />followed by the Source viewed from Mary. <br /><br /><img src="https://d2r1vs3d9006ap.cloudfront.net/s3_images/1416898/4325-1vns93f_inline.png?1463418159" title="Image https//d2r1vs3d9006apcloudfrontnet/s3_images/1416898/4325-1vns93f_inlinepng1463418159" /><br />And then the Source view in isolation:<br /><img src="https://d2r1vs3d9006ap.cloudfront.net/s3_images/1416900/4323-1qzzihw_inline.png?1463418188" title="Image https//d2r1vs3d9006apcloudfrontnet/s3_images/1416900/4323-1qzzihw_inlinepng1463418188" />.
  • May 16, 2016 15:13
    Ron Tanner
    Reason: spam
    Dispute this change
  • May 08, 2016 13:02
    joe martel
    Reason: Dup
    Dispute this change
  • May 08, 2016 12:59
    joe martel
    Reason: Dup
    Dispute this change
  • May 05, 2016 07:54
    Tom Huber, the poster:
    Removed a reply by Tom Huber in Partner websites
    Reason: removed by the poster
  • May 04, 2016 15:09
    Roy F Hunt, the poster:
    Reason: removed by the poster
  • May 03, 2016 16:12
    Ron Tanner
    Changed reply in topic of Bic does not show when it should. by Ron Tanner to This is not a simple fix Family Tree. These are ordinances and BIC comes from membership so there must be corrected or added membership records and validation that sealings were done before births. This is done by the membership department and we have sent 1000s to them for fixing. Please be patient..
  • May 02, 2016 14:33
    Ron Tanner
    Changed reply in topic of We need more automation! Computers could generate suggestions and then people can verify to speed up the process. by Ron Tanner to We actually do a significant amount of automation. There is one principle of Family Tree that the user contributes the data. So the computer can assist, suggest, and provide information but the user must make the conclusion. This is because the data is owned by the users and not the machine.<br /><br />That being said we do analyze records and persons in the tree and show hints of records about that person. We assist in lining up persons in the records with persons in the tree. We show duplicates, we identify data problems and research suggestions, etc.<br /><br />What specifically are you suggesting to be automated?.
  • May 01, 2016 22:07
    joe martel
    Reason: dup
    Dispute this change
  • May 01, 2016 22:06
    joe martel
    Reason: dup
    Dispute this change
  • May 01, 2016 22:06
    joe martel
    Reason: dup
    Dispute this change
next » « previous