Versions Compared

Old Version 21

changes.mady.by.user Sameen Babur

Saved on

compared with

New Version 22

changes.mady.by.user Matt Berg

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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 communities schools against OAs in Reveal 
      • Check that fields with dropdown select type, boolean type, numeric type and Yes/No type have valid entries
      • Other? <What other validation checks are necessary?>
      • 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
        • <Other error messages depending on validation checks>
      • 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 (name all fields from the Registration dictionary)
  • Workflow to replace amend roster
    • 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?"   MB: This is a bit more complex in that we have to delete all the registered children and the tasks associated with them.  AM: Ah, I didn't consider that and thought this would be simpler. Can you suggest how we should handle this instead if they want to make changes?  MB:  It might be easiest if this is a replace.  We can also support a delete roster and then they just upload a new roster with the amended data to replace it.  The challenge more is what do they do if they want to amend things once they've started to collect data.  We probably should just not allow that as they can have the ability to add children once data collection has started.
  • Restrictions
    • Once a plan status is not in 'draft' 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 

...

  • 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

...