[CSV] Registration form data upload enhancements

[mahalakshme]

Context:

• Frequently questions arise from data entry person of NGOs regarding the format of the fields. And, previously using CSV upload in unexpected way has also led to loss of data. Hence overall as part of this epic we are trying to improve the user experience of CSV uploads.
• To confidently suggest CSV upload related improvements to clients.

Some previous tickets faced:

https://avni.freshdesk.com/a/tickets/2463 - may be case sensitive address comparison was made - for user the case doesn't matter
https://avni.freshdesk.com/a/tickets/2655 - spaces in fields, with spelling mistakes may be we should add this in the error message

https://avni.freshdesk.com/a/tickets/3110 - newline in data

https://avni.freshdesk.com/a/tickets/4765 - edit - id optional

erasing of Power data, date format?

When some identifier assigned, update in db that it is used. Currently it is not updated when done via CSV upload.

AC:

• Start with integration tests to make sure nothing already working breaks. Will also help in getting confidence for CSV upload. Currently the confidence is low.
• Remove Id column from the sample file or have different columns for uuid and legacy Id so that validation can be done
• case insensitive headers
• trim trailing and starting space in headers
• mark 'mandatory' for the columns in description field
• specify date format
• for coded concepts mention the allowed values, and single or multi-select
• two modes - create and edit
• If lowest address level is mentioned on 'subject type' show that hierarchy alone
• should not have the need to specify SubjectType
• When written rule that violates form element rule of 'Age at marriage', doesn't show error: 'Age at marriage cannot be greater than current age.' in the uploaded CSV
• When visibility for an entry is false and if value for it is entered(if Unmarried and Age entered), show error for that row as
  'Based on values entered for other rows' - no need to handle
• Low and High Absolute not respected in execution of rules
• in create if an entry with a legacy id already exists do not create and show error 'Entry with legacy id, 5 already present in Avni'

Already handled:

• When visibility for an entry is true and the field is mandatory and if value not entered shows error as 'Column: Age at marriage Error message: Empty value not allowed.'
• When visibility for an entry is false and if value for it is entered(if Unmarried and Age entered), value for that not saved
• When Mandatory column not entered, then shows error message: "Column: Mother's Name Error message: Empty value not allowed."
• Hiding form element group dynamically also works by not saving the observations to the db
• Simple decision rule getting executed.

Questions:

Showing/Hiding form elements how to handle?
convert JS rules to excel rules

Tasks

Preview Give feedback

1. [CSV] Registration form sample file #1394
   +0
2. [CSV] Registration forms data upload and validations avni-server#833
   +0
3. [CSV] Enrolment and Encounter sample file avni-server#838
   +0
4. [CSV] Enrolment and Encounter data upload avni-server#839
   +0