The Sync Report will summarize the total number of cases uploaded to CSWeb for a particular geography. The report can be run on all dictionaries uploaded to CSWeb. The dictionaries will appear in the order they were uploaded to CSWeb. By default the first dictionary will be displayed and grouped by its first dictionary id.
- Click on a dictionary from the sidebar under Sync Report
- Select the dictionary id from the dropdown above the report
The column filters allow further filtering on values that are currently displayed. While search ids allows for a global search across all dictionary id rows (the final column, totals will not be searched).
By default only codes will be shown in the report. However, a CSV file can be imported that defines code and label pairs, so a label can be displayed in its place. The rules for defining these pairs are as follows:
- The first pair in the CSV file must define the first dictionary id
- Each following pair must correspond to a dictionary id in consecutive order
- Dictionary ids do not require a corresponding pair. However, once a dictionary id has been ignored no more can be defined. The code will be displayed.
The first row of the CSV file is either an optional header or pairs. If the header is included then tic "CSV file has a header row" when importing the CSV file.
If a header row is included and the dictionary ids for the dictionary are province, district, and enumeration area then the format of the first five rows is:
| Province Code | Province Label | District Code | District Label |
| 1 | Artesia | 1 | Dongo |
| 1 | Artesia | 2 | Idfu |
| 2 | Copal | 1 | Baja |
| 2 | Copal | 2 | Bassac |
Notice the enumeration area is ignored in this example. The province and district will display labels, while the enumeration area will display a code.
To create useful reports it is important to understand how the design of the dictionary affects the report. Each dictionary id will become a column in the report. Typically, each dictionary id is a unique geography and the report summarizes the information by geography.
| Province | District | Enumeration Area | Total |
| Artesia | Dongo | EA 001 | 56 |
| Artesia | Idfu | EA 007 | 33 |
| Copal | Baja | EA 001 | 0 |
| Copal | Bassac | EA 005 | 74 |
If the enumerator id is added as a dictionary id item consider how its position affects the report.
| Province | District | Enumeration Area | Enumerator | Total |
| Artesia | Dongo | EA 001 | Enum001 | 56 |
| Artesia | Idfu | EA 007 | Enum002 | 33 |
| Copal | Baja | EA 001 | Enum003 | 0 |
| Copal | Bassac | EA 005 | Enum004 | 74 |
Above the enumerator id is the last dictionary id. The report summarizes the information by geography, but also allows the analyst to see which enumerator is working there. Additionally, if the province, district, or enumeration area is selected from the dropdown the enumerator will be ignored.
| Enumerator | Province | District | Enumeration Area | Total |
| Enum001 | Artesia | Dongo | EA 001 | 56 |
| Enum002 | Artesia | Idfu | EA 007 | 33 |
| Enum003 | Copal | Baja | EA 001 | 0 |
| Enum004 | Copal | Bassac | EA 005 | 74 |
Alternatively, if the enumerator id is the first dictionary id then the emphasis will be on the enumerator. All information is summarized by enumerator and then by geography.
- Urban/rural do not make the key unique, so they do not need to be id items. However, if used they will double the number of rows in the report. Further, at what position will they be added?
- Longitude/latitude will likely be unique on their own. Making the report nothing more than a list.