Understanding Accuracy
We’ve received a lot of feedback regarding accuracy and wanted to let you know a little more about why we started showing the accuracy rating and about how accuracy is counted.
As more contributors joined the project we were asked many times for an indicator of how well they were doing – since we all want to know if our contributions are making a difference. Based on this feedback we looked for a way to show you how well you were doing with your keying efforts and this is where the accuracy rating came in. We are grateful for your feedback as we are always looking at ways we can clarify and improve both this feature and other features.
In regard to whether your contributions are making a difference that cannot be measured. During this stage of beta testing your contributions have been incredibly beneficial – we would not be where we are today without you, the many contributors who give of your time keying, providing feedback, assisting us with bug testing, testing arbitration, and the list goes on. Your accuracy rating does not reflect your value to the project and the value that you are providing to people who will view the indexes free because of your efforts.
There have been some speculations on how accuracy is counted and what types of records are counted and we want to clarify this for you. Accuracy is counted based on the number of fields that were accepted in the arbitration process.
- If an image set has not reached arbitration it does not reflect in your accuracy.
- If all of the fields for Keyer A and Keyer B match in an image set that image set is counted as 100% accurate. (Each image set goes through arbitration whether the fields all match or not.)
- When Keyer A and Keyer B have fields that do not match the arbitrator chooses which, or neither, record is correctly recorded from the image. Each of the fields that are accepted as correct positively impact accuracy and each field that is not accepted negatively affects accuracy. With the accuracy rating being based on the field level it is clear to see how small mistypes or not keying all of the available fields will affect your accuracy negatively.
Our hope is that you won’t be discouraged by your accuracy score. The beta process has been a learning process for everyone and we acknowledge that at times the instructions and directions have not been as detailed as we need them to be. We appreciate your contributions to the project and for being patient and willing to continue on as we learn the best ways to set up the projects and communicate with you.
As you see your accuracy rating going up or down – at least mine does – we want you to be aware of the resources that are available to assist you in keying and I hope that you will recognize your very important role as a contributor no matter what your accuracy rating is.
Tutorial (English Version)
Project pages (access these via your dashboard or by choosing “View More About This Project”)
I have been Keying and Abitrating for a while now. Lately my Accuracy score dropped to 63% and then to Nill% Quite alarming really with no feed back as to why. I wonder if this has happened to any one else. or if anyone knows the reason behind this.