- I know what the number of cases represents, but what does the "number of records written" represent?
Number of keystrokes is clear, but what determines the number of "bad keystrokes?" I thought it might be the number of times you back up and delete/re-key data, but that appears to not be the case.
Operator Statistics File (.log)
-
BPAnderson
- Posts: 7
- Joined: May 9th, 2013, 11:18 am
Operator Statistics File (.log)
I have the information on what the layout is for this file, but have a question about how some of the numbers are calculated.
-
Guest
Re: Operator Statistics File (.log)
Does anyone know where I can find the explanation of the various fields that are stored in the .log file. I have the column definitions, but no explanation as to what some of them mean or how they are calculated. Any help would be much appreciated.
-
Gregory Martin
- Posts: 1792
- Joined: December 5th, 2011, 11:27 pm
- Location: Washington, DC
Re: Operator Statistics File (.log)
Say that you have a population record that can repeat and a household record that only occurs once. If your file looks like this:
Case 1 Population Record Person 1
Case 1 Population Record Person 2
Case 1 Population Record Person 3
Case 1 Household Record
Case 2 Population Record Person 1
Case 2 Household Record
The first case has three people and the second case has one person. In this scenario, the log file would show that you entered two cases and six records. Looking at the number of records written can be a better approximation of a keyer's workload than the cases, given that one case could have 10 people and another only one person. The case with 10 people would take much longer to enter than the one with one person, something reflected in the number of records written.
The count of bad keystrokes goes up when an invalid value is entered into a field (e.g., something that is not in the value set), or when an invalid character is entered (e.g., an alpha character to a numeric field).
Case 1 Population Record Person 1
Case 1 Population Record Person 2
Case 1 Population Record Person 3
Case 1 Household Record
Case 2 Population Record Person 1
Case 2 Household Record
The first case has three people and the second case has one person. In this scenario, the log file would show that you entered two cases and six records. Looking at the number of records written can be a better approximation of a keyer's workload than the cases, given that one case could have 10 people and another only one person. The case with 10 people would take much longer to enter than the one with one person, something reflected in the number of records written.
The count of bad keystrokes goes up when an invalid value is entered into a field (e.g., something that is not in the value set), or when an invalid character is entered (e.g., an alpha character to a numeric field).