Error Report Project - Members have to know D/B coding?

Question

70 yr old member with college degree but not in computer science nor Data Base structure coding.  Why all of a sudden do I have 100 errors concerning ?  well concerning codes like 822 / 811 / 821 ?   

The error report is a useful tool to identify correctable people errors like (no gender)  (right town with wrong state)  (dates between parent and child to far out of  sync)   BUT how in the world are average folks going to understand  technical symbols or technical punctuation.  Furthermore was unable to define several of the codes given to try to understand how to correct a now huge error report.  Has the intent of the 'Error Report Project' gone amuck.

Trying to keep this all a simple as possible. If we have to take a 6 month data base coding course ...won;t that harm the WikiTree interest and particitation.

I would say many like to check and clear any errors they might cause doing simple family history ...but if it's to technical to fill in Bio and comment and sources ...seems like your Error Report Project might explode .

Comments

I am feeling a bit the same I try to keep up with error report.  This week I had about 45 error 831 which is not even documented in Project: Database Errors.  

I have made a quite a few errors and the error report has served as a wonderful tool in repairing  no gender, dates between parent and child etc 

I just went in and used the false error tab,  my profiles I am trying to make consistent through out, using multi Census data, or two marriage certificates or bonds or two different death documents.  I actually prefer two good sources with matching documents rather then none.       

I still work, and have spent a good bit of time with the boring stuff "looking up coding, or trying to understand coding.  I much rather be searching for ancestors.   

 

 

 

---

Hey Greg ... hang in there ... it will be getting better and better ... this from another 70+ year old member ... ah, but, I do have a computer science degree ...

These guys are doing a great job at a task that is just unimaginable ... trying to find somewhat hidden errors in a pretty big data base.

Like this week I had a bunch of improper date errors because the profile was locked down a bit ... ie not 'open' ... they'll fix that up but we have to be patient.

I have a pretty big error page but I just look at things I know might be my problem ... like Mom died before birth and others ...

Bottom line ... this is all good stuff that they're doing.

---

Thank you for good input. You have reminded me this is a huge overall data base that works thousands of things very well.  I will try to keep up.

I guess I was also concerned about scarring people away from using WikiTree ...if it's to complicated or not very user friendly.  Thanks for your thoughts, very helpful,  Greg

---

Julia  Thank you.  I will keep working on learning .. I guess I may have failed to understand how big the overall WikiTree data base might be.  I'm very watchful for duplicates in my family but I see all errors may goof things up for others.    Thanks again  Greg

---

Greg ,  I don't bother with it anymore.  I have no clue.  My watchlist is so small I pretty much know what's wrong with my watchist.  Getting the time to fix is another issue.  I do agree it is a wonderful tool .  I am a dinosaur and I yield to the moderns.

---

I find it interesting that there are typos in the releases from the leaders of this project when they are asking us to improve on such minor things as the absence of a = in a heading.

Answer 1

Here is a link  https://www.wikitree.com/wiki/Project:Database_Errors#Description_of_errors  to the db_errors project page with description of each one - hope that helps :)

Answer 2

Hello, Gregory!

If you (or any of our fellow profile managers) need help with db-errors, you can contact me or one of my fellow Data Doctors (https://www.wikitree.com/index.php?title=Special:Badges&b=data_doctor).

We are here to help fix those pesky errors!!