Table of Contents |
---|
...
- Components
- Question name: CSV roster
- Upload button
- Download template button
- Help text - reads "You may upload a CSV with the roster of the children in the school. You must include all required fields in the template."
- View current roster
- Workflow first roster upload .
- Click Download template (template will be laid out per CSV requirements, below) –> CSV file downloads to desktop
- Complete template and save
- Select Upload, select CSV file
- Validation checks of CSV
- Required fields
- Check schools against OAs in Reveal
- Check that fields with dropdown select type, boolean type, numeric type and Yes/No type have valid entries
- Error message if failed:
- "Upload failed. Check your CSV to make sure all required fields are filled in".
- "Upload failed. Check field (field name) in your CSV to make sure it is a valid entry type
- Message if successful: "x out of y individuals were successfully uploaded"
- View/download current roster hyperlink
- This appears as a hyperlink "View current roster <file name>
- Can click on this and see the assigned ids of students, student list with attributes
- There should be a way to download this information as a CSV that looks identical to what was uploaded
- Must include the Reveal operational area id and student identifiers (all fields from the Registration dictionary)
- Workflow to replace roster
- A roster can only be replaced if they have not started to collect data in that plan (plan!=draft). Once they start to collect data, any changes must be made through the client.
- Select Upload, select CSV file
- Confirmation message: "This upload will replace the current roster. You will not be able to recover the previous roster. Are you sure you want to proceed?"
- Restrictions
- Once a plan status is not in 'draft' the roster may not be uploaded/replaced.
- If a plan has data collected against it, the roster may not be uploaded/replaced.
- Cannot edit individuals rows or parts of the roster on web, must edit CSV and replace if changes needed, or can edit on client later
...
- Registration info is incorrect
- Child has moved classrooms. Classroom will be stored as a free text attribute on the child, we do not need to manage a classroom list or a separate classroom entity. It is understood that this means we will not be able to disaggregate on classroom.
- Other reason
Suggested WorkfloWorkflow
- Access the list view
- Select a child
- Access child-specific view
- Access edit view for the registration info
- Selecting that button takes you to the Register child form where you can make edits
...
Drill down levels
- Region
- Inkhundla (comparable to a district in size)
- School (32 schools)
- Age Group
- Individual List View of Children
...
- We need to define what are the key values we need to build in tables in Superset
- Disaggregation would be by any other items from data dictionary mentioned like gender, classroom, precise age, dose given, drugs taken etc.
On app indicators to be defined. See Data collection data dictionary
...