Reporting

Handy features

Automatic charting

You can make helpful charts with simple reports; for example, see the biomarker status report which just has a few fields on it. If you go to the stats & charts view linked at the top, you can view a breakdown by each field in the report.

However, note that the box at the top of the display is slightly confusing:

This means you have N = 149 records with data and 114 records without data. So the report's total N = 149 + 114. And the "Unique" count is how many different values there are for that field.

Then the counts and percentage details after that table are for the records with data only. If you want to get accurate percentages and there is missing data, you will have to do that math yourself unfortunately.

But look, charts!

Common problems

Why is my report super slow to view?

The most likely cause is that you have a repeating instrument field (like "assignment") in your fields or filters.

This can be maybe be fixed by using the flat reporting fields like "current_assignment". We also provide fields like "current_has_been_assigned_to_diary" (and biomarker and neuro) to simplify asking the question of "has the respondent been assigned, at any point in this wave, to X?"

Why do I get blank data when I add fields to the report?

Most often, this is because you have not selected the correct event in the "Additional Filters" box:

If you have fields in more than one event (usually, this would be something like date_of_birth in the "Info" event and something like saq_status in a wave event) you will then get more than one row per respondent, and the report will look confusing and ugly: continue reading the next section.

Why do I get more than one row per respondent in a report?

This can happen if you are selecting more than one event. It can also happen if you are displaying repeating fields (like assignment) but there's nothing that can fix that, that's unfortunately just how repeating instruments work.

If you have selected more than one event in "Additional Filters" and have selected fields from more than one event, that info comes back in multiple rows instead of helpfully collapsing into a single row.

You can get around this problem by using only fields from the "info" arm in "Additional Filters" and using the flat reporting fields like "current_assignment", "current_has_been_assigned_to_diary", and all the other "current_*" fields. Those fields are in the "Info" event instead of the wave events, like M4.

Please note that the "current_* flat reporting" fields are only updated nightly, so if you change the value in a "source" field in the wave event, that change will not propagate to the "current_*" field in flat reporting until that evening. This is the current workaround to make reporting less bad, and if anyone has better proposals, please let us know.

Admin Core folks can help you with all this if this info is not helpful; get in touch.