News on Database errors project (March 19th 2017)

Question

Analysis was done on data from March 19th 2017

Comments

Thank you Aleš !

---

...also Thanks!

---

Thank you, Aleš!

Answer 1

I think it is not so good that the check box for Manager Notified activates  Hide for 30 Days. The way I first notify managers (unless I have already a working relationship with them) is usually to write a public comment on the erring profile saying: "Have you noticed the error report?" and then a link to the error report for that particular profile, so they can see for themselves (and perhaps also notice other errors). But if there's a Temp Hide, they will not see the error I'm trying to alert them to.

Comments

In such case use Not corrected with comment Posted Message.

Maybe we should rethink the need for Hide for 30 days. now with Error status it is a bit obsolete.

---

Yes, please: rethink.

But we should of course hear from other Data Doctors, who may still have a use for the function.

---

Well, Hide for 30 days is convenient when the correction is a Proposed Merge. For profiles with no longer active (or no longer interested in the profile) managers, 30 days is the time it takes to get a default approval and complete the merge. So in that case, hide the error for 30 days is the most useful option.

For other cases, which are the majority, I agree with Eva.

---

True, about the 30-day merges.

I have mostly been working the db-errors from a spreadsheet shared between the two of us who work error 912 (accessible from the Swedish Wikitree group at FaceBook). So I have not had a great need for hiding the ones I've decided to do by a merge.

I guess I may change my routines somewhat now with the status button.

Although with managers with 100+ errors of the same kind it has been useful to have them on their own page for chipping away at, little by little.

---

I changed the fourth option to Proposed merge (hide for 30 days)

For notifying the manager, it is better to use first option (Not corrected) and write as a comment, Message posted on PM to manager or similar.

---

Simple and elegant.

Answer 2

I prepared report of entered comments by error and status. In a week or two, I will prepare hints for error comments based on entered comments. Have a look.

http://www.softdata.si/osebe_staro/ales/wikitree/Status%20comments.htm

Here is also a Top list of users claiming their corrections. They are counted only if error is really corrected. I still have to decide if this will be regular thing.

http://www.softdata.si/osebe_staro/ales/wikitree/Top%20DD.htm

Comments

Thanks Aleš

---

I like it. Some of the corrections I've done have been quite odd.  Joseph Smith, head of LDS, married many women ceremonially after death. Blanne Harper - often misspelled in the Bible in an in-law branch of tree - actually Blaney.  Suggestion - a better (any) way to deal with poly marriages.

---

Very nice work! Looks like you have recruited some hard working Data Doctors!

Thank you!

---

I like your list of users claiming their corrections, except it leaves out the 901 db_e, because we cannot correct them due to the privacy level.  Kind of leaves us out in the cold.

---

I know. Also some errors are easy to correct, and some are hard. That is why I don't like scoring who is the best. Maybe if I count all comments it would show who are active DD.

---

That sounds like a plan. By the way, you are doing an awesome job!

---

Here are new reports, that might be final.

Used comments by error: http://www.softdata.si/osebe_staro/ales/wikitree/Status%20comments.htm

Number of status entries by DD and Error: http://www.softdata.si/osebe_staro/ales/wikitree/Error%20State%20by%20DD%20and%20Err.htm

Number of status entries by Error: http://www.softdata.si/osebe_staro/ales/wikitree/Error%20State%20by%20DD.htm

Number of status entries by DD: http://www.softdata.si/osebe_staro/ales/wikitree/Error%20State%20by%20Err.htm

Answer 3

Here is another report for all status changes for last 6 hours.

http://wikitree.sdms.si/function/WTStatusReview/Status.htm