Can't find Findagrave error that triggered suggestion report

Question

I got a suggestion report for Hopkins-2535. The error is  571 FindAGrave - Link without Grave ID

I can't figure out what is triggering the suggestion.  The Findagrave link is there, and it leads to the correct Findagrave profile.   Was this possibly triggered by the work being done recently at Findagrave, and if so, should I identify it as a false error/ suggestion?

Thanks, Reba

Answer 1

The error wants you to include the memorial number.   74467288 The easiest way to fix that is with the Find a Grave template.  {{FindAGrave| 74467288}} 

Comments

Thanks, J.Crook.  I imagine I'll get a hundred or hundreds of additional errors if I need to put that template into my profiles, since I have never used that.  

Is this a proactive way to prevent future problems?  As I mentioned, there isn't any problem with the link the way it is, and it leads to the current Findagrave profile.

Thanks for taking the time to answer me!  I do appreciate it.

Reba

---

They've changed the URL format so the ID isn't at the end now.  Aleš might need to look at this.

---

The "suggestion"/error wants you to have the memorial ID number.  The template is useful because Ales, the tech guy, is planning to update it as needed using bots in case the URLs change in the future (a possibility, since Find a Grave made so many recent changes).

Personal Preference here:  To me, it's important to include a complete citation for each source I use, so for your Thomas Hopkins, I would include the complete citation from Family Search:

"Find A Grave Index," database, FamilySearch(https://familysearch.org/ark:/61903/1:1:QV2P-TYBW : 13 December 2015), Thomas Hopkins, 1807; Burial, Argyle, Washington, New York, United States of America, Hopkins Cemetery; citing record ID 74467288, Find a Grave, http://www.findagrave.com.  

Then I would replace this bit: Find a Grave, http://www.findagrave.com which is fairly useless with the template.  {{FindAGrave|74467288}}

I pretty much love the template.  

Anyway, if you slap the memorial number on, using your current format, that will work too.  Just make sure you use the memorial number, mark the error corrected, and blissfully continue to add profiles, knowing you have one less suggestion to deal with.

---

Basically, the template is optional--the Find a grave memorial number is not.  That's what I should have said.

---

He has the number in his reference link. It isn't that which has caused the error. Also I have found profiles with the Template that are now showing error 571.

---

Well, then, my favorite thing to do is to mark a ridiculously wrong suggestion as a false error.  And then when it pops up again (which it isn't supposed to do), mark it again. Silly computers.

Answer 2

Yes Something has gone wrong between Wikitree and FindAGrave. The links are correct and work yet there is 4135 new error 571 and 4950 error 572. 

You may need to mark it as False error or corrected and leave it. 

Your link is correct so nothing to worry about.

Comments

Thank you, Darren.  I added the template to the profile in question, but now I know it wasn't an actual error, so I won't worry too much if I get more of them.

Reba

Answer 3

Uh oh.....I think we have a bigger issue. I have 38 suggestions showing up for Suggestion 572 Linked grave not matching profile

I used the template {{ FindAGrave|Memorial Number }} on all of them. All 38 appear to be profiles that I created over the last few days. When clicked they do go to the correct memorial.

Comments

I got a few more suggestions, and it does seem that they were all from profiles I worked on recently.

Reba

---

I'm holding on doing anything with my suggestions on those until we have a resolution just in case there's a tweak I need to make. I don't want to mark as false, because then it goes away forever.

It's strange, because none of my older ones with the same template are creating a suggestion. Does this seem to be the same case with you Reba?

---

I had never used the template before today, so I'm not sure about that. I did mark a couple of the suggestions as false -- hopefully that won't come back to bite me later.  I agree that we probably need to wait and see if there's anything special that needs to be done.

Reba

---

Ignore the recent error as the FindaGrave errors are getting redone as Aleš needs to adjust his program to reflect the recent changes at FindAGrave.com .

---

Thanks again,, Darren.  I'll work on other things and forget about the suggestion report for the time being.

Reba

---

Thanks for the info Darren!