from Paul, January 26 2018
Yesterday, I added a new source from WebHints into RootsMagic 7, and today, I will add the same source into Ancestry and link it to the burial event and as a general source.
I found Richard Peter Young in my tree and from his profile, I clicked Add Source (see image below).

Then I clicked the create a new source (see image below).

Create the new source with the title being London, England, Church of England Deaths and Burials, 1813-2003 about Richard Peter Young, author being Ancestry.com, original data note being London Metropolitan Archives; London, England; Board of Guardian Records, 1834-1906/Church of England Parish Register, 1813-1906 (not required), publisher being Ancestry.com Operations, Inc., publisher date being 2010, publisher location (or place) being Provo, Utah, USA, and reference number REFN being Reference Number: P70/MRY2/077. The Ancestry repository is selected from the drop-down list and the Save Source button is clicked (see image below).

Next, the citation detail of the reference number being Reference Number: P70/MRY2/077 is added (see image below).

Lastly, any events the source is linked to can be checked, for example, the burial event (see image below).

To create a general source, click add a new source and then select the existing source (in this case if is London, England, Church of England Deaths and…d Young), enter the detail as the reference number being Reference Number: P70/MRY2/077 and click the Submit button (see image below). As it is a general source, there is no events that this source citation is related to.

The last activity in Ancestry is to change the burial event place (see image below).

After saving the changes, back in RootsMagic a TreeShare can be started to validate that the changes in RootsMagic (from yesterday) match the changes made in Ancestry today (see image below) and click as Marked as Not Changed button (shown outlined in red box).

The green background on the even date, place and sources indicates that the RootsMagic and Ancestry tree information agrees (nice!).
The last step is to update the research log in GedGap shown outlined in orange (see image below) where I have indicated that I still need to add the URL and image of the source document (but I will do this when I access Ancestry on an access free weekend).

Note: If a vital event had changed (e.g. birth or death), the GEDCOM could be exported from RootsMagic (or Ancestry) and re-imported in GedGap. The scores would be updated based on the relevancy of the new source(s) added, any confidence level would be recalculated and unchanged priorities updated.
Please note; As author of the GedGap tool, this review is factual on the functionality of the GedGap tool but may contain bias given the relationship of the author of this blog entry and the tool being reviewed.