G2G: Shouldn't this be corrected?

Question

We've had discussions about the use of a certain acronym for Findagrave, and the agreement that was reached was that we would use FG and not FAG, because the latter can be offensive to some.

I was surprised to find the following when working on suggestions about problems with Findagrave disagreeing with Wikitree. "FAG is estimate".

It appears that some work needs to be done to remove these last vestiges of the offensive acronym.

Comments

I am on Wikitree regularly and do try to spend some time reading in G2G, but did not catch this. I just recently used FAG as an abbreviation for Find a Grave in some research notes... and would certainly not have if I had been aware. 

Perhaps when something this important for the whole community is decided it should go out in the weekly newsletter that arrives in my email box under "Important Notifications" or some such header. The posts on G2G are almost impossible to keep up with, they drop down quickly and unless I am on G2G every day, all day, I will not catch them all. 

Just my 2cents for what its worth, from now on it will be FG. 

---

I apologize. I should have included a link to the discussion: Find a Grave Acronym is FG - Officially.

---

No apology necessary. Thanks for the link!

Answer 1

Paul, Lorraine is right in that it is hard to reach everyone with something like this. Even the weekly email may not be read consistently by everyone.

I do a lot of category correcting, and I find a quick message to people often works better, especially with a link to the relevant G2G discussion.

Comments

Who would be responsible for changing strings used in the program? The acronym is being used in hints given regarding the resolution of a suggestion triggered by the software.

---

I would guess it'd be Aleš, so if you edit your question and add the tag ales, you should get his attention.

---

Thanks Melanie.

Answer 2

The suggested "replies" is a list created for the most popular replies that have already been loaded against suggestions in WikiTree+.  I'm not sure how often Aleš refresh's these lists. But it shouldn't be an issue just to adjust it in the lists. I know Aleš has been tagged and he will see this.

Answer 3

The WikiTree guidelines on this page discuss the acronym: Help: FindAGrave Acronym.

The Data Doctors Project includes a warning about using the acronym and citation instructions on the group page: FindAGrave Suggestions.

An easy, consistent tip is to use an auto-text extension - you can type in any shortcut, and that shortcut can spell out the entire word.

Ales is the one to change parameters in WikiTree+.  

Where do you see the acronym used in hints?  We'll correct these, but I can't locate any in the group or suggestion pages.

Comments

I saw them for notes like this: "Notified FindAGrave of its error" or this "Findagrave has same birth date; they must have changed it earlier".

Previously it read; "Notified FAG of its error" and "FAG has same birth date; they must have changed it earlier", but apparently someone has already gone in and fixed them.

Answer 4

As I understand, FG is a new guideline from Findagrave site.

And I personally started to use the FG. I think I also checked the wikitree plus code and I didn't use FAG anywhere. If I did please let me know where.

The suggested hints are based on all comments for each suggestion and status made in the past. I display 10 most often used. Since the hints are a result of a database query, I can't change what is returned unless I would correct each comment. But that is a lot of work.

Comments

Thanks for looking at this, Aleš. I seem to remember you developed a method whereby we could contribute to the set of suggestion comments offered, including removing unwanted ones. Was it a spreadsheet or something? If this is still available, maybe we could crowdsource the cleanup.

---

Could you code the return to change FAG to FG? Or FindAGrave. If (results of query=FAG), then substitute FG.

I went back and view the hints from previously cleared suggestions, and it appears someone has changed all instances of FAG to FIndagrave already.

---

Those hints can be defined in calendar template for a challenge.

That doesn't work for suggestions.

Doing such replaces on each string slows things down.

If it seems so important, I can have a look at changing all comments. It might be complicated sinček some are also stored on wikitree sever.

I will look into it when I return from Rootstech.

---

It's not that important to me. I thought it was important to Wikitree. Perhaps another approach would be to weight all comments containing FAG such that they don't appear in the results of the top ten.

---

I updated the FAG to FindAGrave on all statuses. It should be ok now.