Use case: As a (busy) headquarters or supervisor user, I want to know two things about each interview:
- Are there any errors that I should investigate?
- Are there any comments I need to review?
If the answer to either is “yes”, I should review the interview more carefully.
Currently, the both the UI and API help me answer the first question, not the second. Without opening the interview (in the case of the UI) or consulting other data sources (in the case of the API), I do not know whether the interview contains comments.
Going forward, it would nice to make two changes:
- Adding a
Commentscolumn to the
- Adding the same info to what’s returned by the
Since adding this column would make the UI rather crowded, here are some ideas of how to make space for a
Received by Interviewer. Put this information into the
Status Historypop-up instead. Valuable information, but not something that needs to be immediately shown in
Assignmentnumber. Put this information in
Status Historyas well, making the assignment number into a link to the corresponding assignment in the assignment view (see feature here
- Decrease width of
ERRORScolumn. This column seems to have a fixed width that is larger than any reasonable number that could appear there. (See below)
- Use icons, if needed, to denote presence of errors and comments. This would echo the graphical design choice in Designer for showing where enablement and validation conditions are present.
There are still ways of knowing whether an interview contains comment, but both require going outside of the UI:
- Looking at the
questions__commentscolumn in the
interview__diagnosticsfile, which is exported along with all microdata files.
- Determining whether there are any comments by looking for them in the
interview__commentsfile, which is also exported along with all other microdata.