Expressing frustration with FindAGrave corrections.

Question

My apologies in advance.

I appreciate the time and effort invested by our marvelous contributors and members of the tech team to improve WikiTree. That said, I have found myself uncomfortably at odds with the  "Warnings" and "Errors" (*) that generate when the system believes our profile data does not match a FindAGrave memorial that is cited on a profile. 

Finding I am even more at odds now as well meaning folks are editing profiles to add the "sameas=no" and "sameas=yes" FindAGrave templates, and I'm hoping folks can find a better solution.  

I do not use the FindAGrave template. Rather, I write a citation, something along the lines of the example below. 

Susie Smith Jones (1758-1810), memorial 1234567 and gravestone images; web content, FindAGrave, reporting burial at ABC cemetery; memorial maintained by Thankyou Joe; gravestone images added by photographer 1 and photographer 2; additional comments as appropriate.  

The work by well-meaning WikiTreers to address the errors and warnings by editing those citations with "sameas" elements, embeds a mini citation within the existing reference--so we have duplicated information and a second hyperlink. Rather than the citation example above, we find, 

Susie Smith Jones (1758-1810), memorial 1234567 FindAGrave Memorial 1234567 and gravestone images; web content, FindAGrave, reporting burial at ABC cemetery; memorial maintained by Thankyou Joe; gravestone images added by photographer 1 and photographer 2; additional comments as appropriate.  

(*) I still think the terms "Warning" and "Error" are both over the top and send the wrong message. Why can't these all be just "Hints," or "Hint-1," "Hint-2," and "Hint-3."

Edited to note--The underlined elements in the citation example represent links created by embedding the memorial URL--ala, it's a "hyperlink." (See Help:Adding Links.) If this were not a made up example, Susie's memorial URL would be "https://www.findagrave.com/memorial/1234567/susie-smith-jones"; the Wikicoding used to create the embedded link (hyperlink) would be   [https://www.findagrave.com/memorial/1234567/susie-smith-jones ''FindAGrave'']. 

Comments

I have a serious problem not just with the "template" Find A Grave source citations (which I despise; they're unnecessarily lengthy and imprecise to boot), but the fact that the memorials seem are taken as gospel, when they are, in fact, riddled with errors. 

For example, the names and locations of cemeteries memorialized on Find A Grave are often incorrect. I created a WikiTree category for a certain cemetery and included the full and proper name (XYZ Baptist Church Cemetery) and the proper location (XYZ [community] , RST County, State). The WT bot came behind me and changed the locality based *solely* on Find A Grave's entry for the cemetery, which is very, very wrong. Then someone else came behind them and changed the cemetery's name to "XYZ Baptist Cemetery," which is also incorrect. And the justification I was given for both was, "This is what Find a Grave says and if we don't use that, then someone may come behind us and change it anyway."

And, of course, that is aside from the many "warnings" WikiTree generates by comparing WT profiles to Find A Grave memorials; and keeps generating them even when multiple explanations are generated in the "status" field and the "false warning" status is used, and also when a note is dropped on the WT profile explaining why the dates used are the correct ones.

As genealogists, it is incumbent upon us to use facts to reassemble our ancestors' lives, not disseminate incorrect information. By prioritizing Find A Grave's many, many errors over actual, verifiable research, we are doing a grave (pardon the pun) disservice to our ancestors and the legacies we're trying to preserve through our efforts on WT.

Answer 1

Another point of view:

The inclusion of source citations enables Wiki Q-numbers to link data and generate the warnings you mentioned below. This practice is fundamentally about collaboration and the dissemination of knowledge. It's not merely about generating warnings for WikiTree users; it also serves other applications that may contain inaccuracies.

This process contributes significantly to improving the quality of available data on the internet. While the volume of messages, including warnings, generated by WikiTree might seem daunting, it plays a crucial role in rectifying erroneous data across various websites. Though it's a gradual process, the long-term benefits are substantial.

Additionally, proper source citation facilitates quicker access to our data during searches.

Comments

Thank you for your comment. I just take exception to a notion that what I have written is anything but a "proper source citation."

---

Elaborating ...

The data in both FindAGrave and WikiTree is user generated.

When there is a difference in the data comparison, it isn't possible for a simple system data check to know whether the data on FindAGrave is superior or inferior to that which is found on WikiTree.

Since we are only trying to point out differences, why can't all of these suggestions be considered Hints, or for the purpose of further categorization, Hint-1, Hint-2, Hint-3, etc.

P.S. I'm all for collaborating across platforms, and routinely communicate with FindAGrave memorial managers. FindAGrave doesn't have a comment feature or a comparable G2G-like system, and too often the wonderful assigned mangers do not accept messages.

---

I didn't mean to imply it was unacceptable or not proper. I was just pointing out the purpose and benefit of the formatting to link the two.

---

You're good, Jimmy ... Thank you.

Answer 2

I too have another point of view.

As a researcher, I would much rather have a source with a link that directly takes me to the actual memorial than a link that takes me to the website and a memorial number that I would have to copy and paste in a blank on the website to take me to the actual memorial.

Comments

Sorry if this was not clear, but the links in my "real" citations do go directly to the memorial page.

(Have edited the post in an effort to make this clear.)

Answer 3

FWIW, the recommended format for the citation includes both the profile's URL and the template: https://www.wikitree.com/wiki/Help:Find_A_Grave#Links_in_source_citations Using the template ensures that a link will work even if Find a Grave changes their URL structure, but of course the template isn't a complete citation by itself. So the duplication is actually recommended.

Comments

While using a template is an option, I have never considered this to be the  "recommended format."

From "Help:Find A Grave" (quoting)--There is a handy {{FindAGrave}} "link template" for creating links to memorial pages.

You are welcome to disagree, however, I believe the reference notes I write provide a far more complete record of the source's evidentiary value than does a link and the memorial number. 

---

I don’t think it is the issue how you present it, it is the fact that you don’t use sameas=no when you (and others) put links for individuals other than the individual of that WT profile.

Many WT’rs devote a lot of time putting sameas=no on to profiles that are missing it to stop system suggestions.

Many WT’rs rely on the FindAGrave suggestions to help locate potential connections. By not having the sameas=no, it means other WT’rs have to spend more time sifting thru 585, 591-593 suggestions determining if they are accurate. We already have to find supporting evidence but then we have to figure out which profile the suggestion actually relates to when there are many FindAGrave links on one profile.

Either you (and others) are slowed down a bit when setting up the profile (/sourcing a profile) or others are slowed down fixing suggestions or trying to make connections.

---

Hi S. Stevenson,

Thank you, but wow!  I don't think those who are familiar with my work would think I feel "slowed down" by adding sources!

Again, my objection is not that we are trying to tell the system whether or not the memorial is about a profile person, it's that the mechanism for doing that then re-writes an existing, reasonably developed reference note.

---

Sorry, then i still don’t understand what you are trying to say after reading question and all answers.

---

Thank you ...

I'm just hoping they will come up with a solution that doesn't involve re-writing an existing reference note.

Does that make sense? --GeneJ

Answer 4

The suggestion should recognize the https://www.findagrave.com/memorial/1234567/susie-smith-jones format and extract the memorial number from it. If the data (name and dates) on WikiTree are similar to FindaGrave data the connection is established automatically.

If the data differs a lot, then a connection is not established (you will get 571: FindAGrave - Link without Grave ID Warning), since often there are links to a relative placed on the profile. And only in such case you must use the template {{FindAGrave|1234567|sameas=yes}} In other cases it is not necessary.

And in case of a wrong established connection (you can get a date mismatch suggestion or 572: FindAGrave - Linked grave not matching profile) you should use |sameas=no template parameter to prevent linking to those profiles.

Comments

Hi Ales,

As always, thank you for all you do to support of WikiTree. Where would we be without Ales.

You are rather pointing out the issue that I have.

The template suggestion for sameas=yes or sameas=no doesn't just send information to the system, it re-populates/re-writes my reference note. Why can't we have coding that notifies the system that it is or is not the same profile and be silent as to editing the reference note?

Even if it were silent, it would still be a burden for me. See, I pretty routinely add sourced spouse(s) and child lists to the profiles I narrate, so my narrative might cover folks other than the principal--maybe as many as a dozen others. Even if it was silent, the notion that all those reference notes must be edited to add "no" one one profile then "yes" in another ... and doing it over and over again is taking heavy toll on me.

Said another way, I'm all for the intent, but it has backfired for me to the point where I regret including FindAGrave references.

---

The only stored data (besides profile fields) on wikitree is the bio. So the bio must contain all information about sources. We established years ago that template with sameas parameter is the best solution to resolve the problem of linking and it is in use ever since. As you can see here https://www.softdata.si/wt/Templ_20240317/Template_FindAGrave_Param2.htm on 2,492,076 templates  2,266,049 nave no sameas parameter, 110,697 times is used no and 115,330 yes is used. In total there are links to 6,628,891 unique FG memorials. So one third use template and two thirds of the links are extracted form URL (old and new format) and from FamillySearch citation.

Can you provide an example profile. Algorithms should recognize the correct matching memorial in most cases.

I checked your suggestions and I guess The suggestion 572: FindAGrave - Linked grave not matching profile is the problem. As long as you use template with sameas=yes for the correct memorial all other FG links are ignored. And in case there is no memorial for the profile, you must use sameas=no for all memorials. But that is a rare case.

---

Hi Ales,

As earlier, where would we be without you.

I don't use the template to create the reference note, so the "correction" (sameas=yes or =no) triggers an unwanted edit to my already reasonable reference note--adding duplicative information (unformatted) and a second link.

I don't have a good work around. I could put all the FindAGrave reference notes on a family free space page, but since I often will include items about FindAGrave in research notes, I'd have to move those also to the free space page, which seems self defeating.

---

The suggestions about FindAGrave do not just use the Template to decide which of the various Hints/Suggestions/Warnings get triggered. It uses the links as well.

However if the Template is used then it will tell the suggestion bot checker to ignore the Hint/Suggestion/Warning if it is a FindAGrave profile for a family member and sameas=no is used or Sameas=yes is used on the actual Wikitree persons FindaGrave link.

So using the templates helps prevent Hints/Suggestions/Warnings from happening when people do add links for people that isn't for the actual Wikitree profile. Therefore they are useful and it is possible that the people editing your watchlist profiles where doing it to prevent suggestions being generated or fixing generated suggestions before you were aware of them.

---

Hi Ales ...

I think the fifteen (15) profiles below were edited yesterday to add the template to memorials. If I have the chance later, will add another note with a few profiles that reference numerous memorials, but haven't had the templates added yet.

*[[Herbert-1451|Richard Herbert (1729-1823)]], https://www.wikitree.com/wiki/Herbert-1451 --at least 11 memorials referenced on the profile that were edited to add the template.

*[[Schleppi-1|Daniel Schleppi (1755-abt.1799)]], https://www.wikitree.com/wiki/Schleppi-1 --believe there are five different FindAGrave memorials used as reference notes. At least one has been All were edited to add the template.

*[[Drummond-4713|Thomas Drummond (abt.1765-bef.1815)]], https://www.wikitree.com/wiki/Drummond-4713 -- only one FindAGrave memorial, but it is of his wife, and it has been edited to add the template.

*[[Haughton-752|Joel Haughton (1749-)]], https://www.wikitree.com/wiki/Haughton-752 --one FindAGrave memorial is reported in the Research Notes--even though it wasn't an inline citation, it was edited using the template.

*[[Keyser-1758|Lemuel Keyser (abt.1787-bef.1816)]], https://www.wikitree.com/wiki/Keyser-1758 --I think five FindAGrave memorials ... edited to add the template.

*[[Preston-2983|Worcester Preston (1797-1880)]], https://www.wikitree.com/wiki/Preston-2983 --there are three reference to FindAGrave, two were edited to add the template.

*[[Stombaugh-17|Magdalena (Stombaugh) Kemberling (1798-abt.1821)]], https://www.wikitree.com/wiki/Stombaugh-17. Only one memorial, but it has been edited.

*[[Bagley-2353|Sarah (Bagley) Minard (1805-1878)]], https://www.wikitree.com/wiki/Bagley-2353 --two memorials reported on the profile, the reference note was edited to add the template.  

*[[Firestone-168|David Roller Firestone (1809-1851)]], https://www.wikitree.com/wiki/Firestone-168 --three memorials in reference notes edited to add the template.

*[[Minard-375|Thomas Hazen A. J. Minard (1815-bef.1901)]], https://www.wikitree.com/wiki/Minard-375 --two memorial on the profile, one memorial in research notes was was edited yesterday to add the template.

*[[Firestone-343|Harriet (Firestone) Knight (1820-1909)]], https://www.wikitree.com/wiki/Firestone-343 --two references on the profile, the citation to her daughter's obituary on FindAGrave is cited, and it was edited to add the template.

*[[Merrill-6861|Martha (Merrill) Detterich (abt.1826-bef.1882)]], https://www.wikitree.com/wiki/Merrill-6861 --one reference to FindAGrave, edited yesterday to add the template.

*[[Hart-23091|Emma Hart (abt.1854-bef.1870)]], https://www.wikitree.com/wiki/Hart-23091 --one memorial in "see also" sources; edited yesterday to add the template.

*[[Gibson-29254|Elizabeth (Gibson) Miller (1861-1906)]], https://www.wikitree.com/wiki/Gibson-29254 --one memorial in reference note, edited to add the template.

*[[Gibson-29257|Lavina (Gibson) Vowinkel (abt.1867-aft.1940)]], https://www.wikitree.com/wiki/Gibson-29257 --one memorial on the profile in Research Notes, to cite her brother's obituary. Even though it isn't an inline citation, it was edited to add the template.

And another seven edited today. Onwards toward a zillion. 

---

Thank you for your comment. I'm sure well meaning folks are indeed working to reduce the errors and warnings.

My issue is not with the work to tell the system whether it is or is not the person being profiled, it's that such work involves adding a "template" that also edits the existing reference note.

---

Looking at the list that you just added every one has a warning or an error on it because there is FindaGrave links on the various profiles that are for other related people. The work that was done on those 15 profiles will remove the suggestions from showing (Once the Suggestion Bot checks those suggestions again).

There is no other way that will completely remove the warnings or errors that are happening because you have added the raw links to the family members on a related persons profile other than doing an edit that adds the template. It doesn't matter if the links are in an Inline citation or not the suggestions are still generated because it is entered on the profile.

---

Hi Darren,

Thank you for your comment.

I'm not objecting to the work any of us might do to tell the system that the memorial is, or is not, about the person who is the subject of our profile. (Ala, to address the Suggestions.)

It's that such work is re-writing my already reasonably developed reference note to add unnecessary information.  

Hope that helps. --GeneJ

---

Wouldn't it be possible to use coding along the lines of {{findagrave=yes}} or {{findagrave=no}} to communicate the same information to the system?

---

Your citation is fine, except for one small thing. In short and simply, the "sameas" is necessary for WikiTree's data-matching system to work properly. You do NOT have to use "sameas=yes" for the citation for the profiled person but you do have to use "sameas=no" when you add a FindAGrave source citation for someone other than the profiled individual. If you do not want "warnings" to be generated which influence others (who are adhering to WikiTree best practice--not just being "well-meaning" but doing work to make WikiTree work better for all of us) to change your citations, then you need to add those parameters. It is 10 characters if you include the pipe. You can store it on your computer and just do a copy/paste to make the process even quicker. I bet you already have the template for your source citation already stored so all you have to do is make small edits to it. If you don't then you are making a lot of work for yourself already. Anyway, just add that little bit to it. Problem solved--no warnings generated, therefore no one making corrections you don't want made.

---

The coding for the FindAGrave Template does two main things. It provides a link to the profile that will still stay valid if FindAGrave changes their links again.

The second thing is provide a way by the sameas=no or sameas=yes parameters if there are multiple FindAGrave links on a profile so the data checking systems (suggestion reports) ignore the links that are not for the profile in question. The suggestion of using {{findagrave=yes}} or {{findagrave=no}} would only result in unnecessary edits and would only do part of what the current template does for no real improvement.

The easiest solution if you add FindAGrave links of family members to a profile is to use the template with the parameters as this will reduce the chance of other people coming along and editing your work. Ignoring this option won't prevent the profiles from being listed as potential suggestions that are needed to be changed.

---

I thought that's what I was saying, Darren (if you were replying to me.)

Anyway, none of us should have to be saying this, but sometimes we have to do things on WikiTree (and in other aspects of our lives) which aren't necessarily how we prefer to do things but in a way which conforms with a standard which works best for the community as a whole. Use of the FindAGrave template and the "sameas" parameters (as illustrated on the help pages) is what works best for WikiTree as a community. Not doing so burdens the community and causes it not to function in the way it's designed. I'm no programming guru but I don't think the system could even be changed technically to adapt to GeneJ's personal preference of doing this (not using the template and "sameas" parameters.)

---

Nelda my comment after yours was in reply to GeneJ X. The perils of the G2G format is that all comments in response to another comment are not placed under the right comment.

---

Actually, I have a reasonable understanding of the importance of genealogical data standards (those who know me well, probably know that), and I have a decent understanding of general genealogical writing and citation standards.

In this case, these are not rowing in the same direction. --GeneJ

Time for me to stop, for me to Stop, Drop and Roll.

---

GeneJ, this is not about genealogical standards. No one will fault you on your genealogical standards. As I said earlier, your source citations are terrific for print work. Or even if you were working on a website which didn't need to or want to compare data with another website. This is about adapting the format of your source citations so they will do that. There was another discussion recently about formatting source citations and someone said that WikiTree's recommended source citations were not compliant with Chicago Manual of Style. Not true, in my opinion. Things we do for print citations or even for some websites do not necessarily work here on WikiTree. We still want well-structured source citations. But in this case with the FindAGrave source citations, they need to be formatted for the system to know which data on WikiTree to compare to which data on FindAGrave. The source citation format you prefer just doesn't work to do that. I'm sorry this frustrates you. No one means to make you frustrated unnecessarily. I--and I think others--have just been trying to help you understand why FindAGrave source citations on WikiTree need to include the template and the "sameas" parameters. I know I was thinking if you understood the purpose, you might feel less frustrated.

---

Perhaps it was not intended, but I now have the impression that having our data comparable to FindAGrave is more important than having our profiles well done.

Need to take a break.

---

Aleš, question for you: Will the suggestions report be able to recognize the Find-a-Grave template if it is imbedded in an HTML comment using <!-- .... /> (not sure that's the exactly correct coding)?

---

@Jillaine: I think it will ignore the template but so will it ignore the sameas in the comment.

@GeneJ: After looking at your suggestions and examples, I slightly adjusted the matching recognition. As a result matching changed on slightly over 2000 profiles and prevented the some date/location suggestions on them. But this will not have the effect on 572 suggestion, which bothers you the most.

BTW: You know that you can simply set the suggestion as false suggestion and it will no longer be displayed. It is good to write a meaningful comment like "There is no FG memorial for the person".

---

GeneJ, inclusion of the FindAGrave template in the FindAGrave source citation does not make anyone's profiles less well-done. And it does not prioritize matching data with FindAGrave over a well-done profile. There are hundreds, if not more, of WikiTreers which have produced thousands, if not more, of well-done profiles which include the FindAGrave template in the FindAGrave source citation.

---

Hi Nelda,

Thank you for your comment. 

You wrote, "...inclusion of the FindAGrave template in the FindAGrave source citation does not make anyone's profiles less well-done." 

Below is a comparison for the memorial of [[Houghton-1202|Ebenezer Houghton Jr. (1732-)]], https://www.wikitree.com/index.php?title=Houghton-1202 . Profile reports about say six (6) memorials, with further detail given as part of a FindAGrave Research note. 

** Template format is fine; WikiTree happy, and "sameas" does not change the original output, which appears as, 

Find A Grave: Memorial #35955304. 

**Alternative format is not fine; WikiTree not happy, and "sameas" will change the output, originally as, 

Ebenezer Haughton (1732-1814), memorial 35955304 and gravestone photographs; web content, FindAGrave, reports burial at Godfrey Hill Cemetery, Hebron, Tolland County, Connecticut; memorial created by KC, maintained by James Bianco; gravestone images added by KC; GeneJ note--dates on Ebenezer's gravestone images not readable.

---

Would this be workable for you?

Ebenezer Haughton (1732-1814), {{Find A Grave|35955304|sameas=no}} and gravestone photographs; web content, reports burial at Godfrey Hill Cemetery, Hebron, Tolland County, Connecticut; memorial created by KC, maintained by James Bianco; gravestone images added by KC; GeneJ note--dates on Ebenezer's gravestone images not readable.

The FindAGrave template was inserted after the first comma. A couple of words were moved. Your comments were not removed or changed.

I think you would be able to work this out so all these FindAGrave suggestions would not be generated and others would not be making changes with which you are unhappy.

P.S. If you paste what I presented here into the profile and look at the preview, you can see that the finished product will look very much like your original...

Ebenezer Haughton (1732-1814), Find A Grave: Memorial #35955304, and gravestone photographs; web content, reports burial at Godfrey Hill Cemetery, Hebron, Tolland County, Connecticut; memorial created by KC, maintained by James Bianco; gravestone images added by KC; GeneJ note--dates on Ebenezer's gravestone images not readable.

---

GeneJ, did you consider using WikiTree Sourcer extension. It automatically formats the citation from FindaGrave to a WikiTree format including the template and you just paste it. 

<ref>
'''Memorial''': Find a Grave (has image)<br/>
{{FindAGrave|35955304}} (accessed 22 March 2024)<br/>
Memorial page for Ebenezer Haughton (27 Sep 1732-1814), citing Godfrey Hill Cemetery, Hebron, Tolland County, Connecticut, USA; Maintained by James Bianco (contributor 47745493).
</ref>

It has also some formatting options and the result looks like this:

↑ Memorial: Find a Grave (has image)
Find A Grave: Memorial #35955304 (accessed 22 March 2024)
Memorial page for Ebenezer Haughton (27 Sep 1732-1814), citing Godfrey Hill Cemetery, Hebron, Tolland County, Connecticut, USA; Maintained by James Bianco (contributor 47745493).

---

Hi Nelda,

I appreciate your efforts. 

As earlier, except for saying that terms like "Warning" and "Error" seem over the top (ala, they are hints), this post isn't so much about "Suggestions." 

My issue is that, as implemented, the "sameas" technology is seems invasive. 

Pardon if my ignorance shows, but it seems the template was designed so that WikiTree could capitalize on a cool opportunity, and it became implemented as a source citation that is used and appreciated by many among us. 

Although the template is busy doing a lot of good things behind the scenes, as a source citation it's pretty much just an unformatted link. Other than the site name ("Find A Grave"), I don't think it was ever intended that the template address additional citation elements that would have evidentiary value (my term). 

Your much welcome suggestion is that I should jumble the citation elements I have been using to accommodate that so-to-speak unformatted link. 

Either way, the template is invasive to those reference notes that are better developed, no?   

Our wonderful tech team came up with a non-invasive way to associate WikiTree and FamilySearch FamilyTree profiles. While the template does a lot more than just link profiles, why can't our WikiTree-FindAGrave approach be equally non-invasive.

(Sorry if my responses are choppy ... it is a work day for me.)

---

Hi Ales,

I'm working on a reply ... but may not post until tonight when I am off work.

Thank you. --GeneJ

---

GeneJ, jumbled??? No. In display, the term "FindAGrave" is moved but the two citations are almost identical otherwise. Basically, all I did to re-format the citation was replace your use of a URL in angled brackets with the "FindAGrave" template. That required a slight positional movement. Otherwise, everything in your original citation is there and in the exact order you have them. That is not my definition of "jumbled."

I tried my best to help you.

---

On a profile that has many links to relatives, only one template needs to be added to the one matching the main person with samesas=yes. All of the others would be ignored without having to add templatexto them, 'assuming' there is on Find  grave matching the profile person. You could also put that one template down in your Sources section, not in the citation, if you wanted the citation untouched.

Remember that the Find a Grave suggestions are also making sure that merged or deleted citations are being notified, as well as duplicate profiles are found, possible parents, possible spouse. The suggestions are not just checking dates or names.

Answer 5

I like how you compress the full URL into a link. You have a nicely formatted source reference.

I generally replace the ID with the template following the guidance as noted in your help link above when I work on a profile.

But my main goal is to replace the FamilySearch refs with FindAGrave citations similar to yours produced by the WikiTree Sourcer (https://www.wikitree.com/wiki/Space:WikiTree_Sourcer) (yeah I am lazy). Also I replace the minimalist {{FindAGrave  }} entries that people leave often as the sole source reference with a full citation.

Comments

Thank you for your comment. 

WikiTree, FamilyTree and FindAGrave are all user generated sources, so the quality of the work may vary greatly. For this WikiTreer, FamilyTree and FindAGrave are great finding aids. When the information from those sites is used in conjunction with an array of other sources, we can do a pretty good job of developing a profile. 

Hoping only to be helpful, I don't very often add a FamilySearch FamilyTree link as a source anymore. More often now, I use WikiTree's FamilyTree linker at "FamilySearch Connections." That tool adds a cool link to the "Research" section toward the bottom of the right panel on a WikiTree profile ... See the Research section on the profile of Ashbel Beach, for "Here is a likely matching profile for Ashbel on the FamilySearch Tree: MPPN-CTM." 

---

Thanks, did not realize that existed.

A profile's sources sometimes include a link to a FamilySearch  source for a FindAGrave link like::

https://www.familysearch.org/ark:/61903/1:1:QV28-4GZ8

I replace those.

Answer 6

This might be slightly off what you are getting at, but let me give it a try.

In the main I add both the FamilySearch template and FindAGrave template at the bottom under "see also." I do this so it's easy to flick back and forwards between the different collaborative sites to make sure they are saying the same thing. (And from that perspective, I quite like the suggestions list, but then generally, for the profiles I am interested in, I'm often the person maintaining all three).

If, and only, if I am using an image of a gravestone as a major source (ie if I can't find a burial record, or prove a relationship or date another way than on the memorial inscription), then I will add a fuller FindAGrave source citation into an inline reference.

Maybe this is a distinction that could work for you, as you could write a source citation without the link, add the template at the bottom, and then if it gets "corrected" with the sameas addition, it doesn't change your source citation?

Comments

Thank you for the suggestion.

All sources may contain errors, so I try to rely on an array of different records for information that is consistent or in conflict with other information ... then work to find other sources, hopefully a variety of historical records, to resolve the conflicts.

Dropping the hyperlinks runs counter to my notion of a reasonable reference note, but your idea might work more times than not.

---

I also think we could put all the FindAGrave references in a profile comment, and then cite the comment.

---

I, too, share Gene's impression that commitment to the existing way the FindaGrave template is used conveys that "having our data comparable to FindAGrave is more important than having our profiles well done."

AND I think that Natasha's suggestion might be a good compromise that would leave Gene's (and others') beautifully written and complete citations intact while at the same time attending to the data-comparisons that are so important to other (but not all) Wikitreers. Until now, I have always deleted a Find-a-Grave template from under "See also:" if Find-a-Grave was already referenced in an inline citation. But I'm now seeing the advantage of leaving it there.

Gene, the potential / likely problem with putting your beautiful Find-a-Grave citations into a comment and then referencing the comment is that comments get archived and even deleted.  So I don't think that's such a great solution.

---

Hi Jillaine,

Thanks for your thoughtful comments.  --GeneJ