You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The idea is to make the process easy for the most commonly used data types and iteratively improve for others as well.
AC:
Person subject type:
For registration create(Edit of an entry will not anymore be possible via CSV. We will support only create-not scope of this card to restrict):
- Instead of 'Id column' add 'Id from previous system' as column with mentioned descriptor in the sample file
- Mention as 'Optional' for the fields that are not marked mandatory. Mention the required default fields like Gender also as mandatory.
- If a registration form is associated with only one subject type, then subject type column should not get displayed.
- Move 'Date Of Registration' and 'Registration Location' to before 'First Name' like available in 'Data Entry App'.
- If 'Lowest Address levels' defined in the subject type, then the hierarchy until lowest 'lowest address level' is sufficient to be mentioned.
- If multiple hierarchies are present, then only the hierarchies to which the defined 'Lowest Address level' belongs to need to be mentioned in the sample file.
- For coded concepts, mention 'Allowed values: {}'
- For coded concepts single select, mention 'Only single value allowed.'
- For coded concepts multiple select, mention 'Format: Separate multiple values by a comma.'
- For date concepts(including registration date) specify the format as 'Format: DD-MM-YYYY'
- For numeric concepts, mention 'Max value allowed:' or 'Min value allowed' if high or low absolute defined. Else mention 'Allowed values: Any number'
- For text and notes concepts, mention 'Any Text'
- Order of descriptions:
1. Optional
2. Allowed values/Max value, Min value/Format
3. Only single value allowed/Separate multiple values by a comma/Default value:
For Subject type of types, Individual, Group, Household - columns, Date Of Birth, Date Of Birth Verified, Gender, First Name, Last Name, should not get exported and instead Name column should get displayed. For Household, 'Total members' column should also get displayed
For registration edit:
- Add Legacy id and UUID as columns instead of Id column. (to prevent incorrect update of existing records)
- 'Mandatory' field descriptor can be removed
- For registration form, 'subject type' column should never get displayed.
Motive:
The idea is to make the process easy for the most commonly used data types and iteratively improve for others as well.
AC:
Person subject type:
- Instead of 'Id column' add 'Id from previous system' as column with mentioned descriptor in the sample file
- Mention as 'Optional' for the fields that are not marked mandatory. Mention the required default fields like Gender also as mandatory.
- If a registration form is associated with only one subject type, then subject type column should not get displayed.
- Move 'Date Of Registration' and 'Registration Location' to before 'First Name' like available in 'Data Entry App'.
- If 'Lowest Address levels' defined in the subject type, then the hierarchy until lowest 'lowest address level' is sufficient to be mentioned.
- If multiple hierarchies are present, then only the hierarchies to which the defined 'Lowest Address level' belongs to need to be mentioned in the sample file.
- For coded concepts, mention 'Allowed values: {}'
- For coded concepts single select, mention 'Only single value allowed.'
- For coded concepts multiple select, mention 'Format: Separate multiple values by a comma.'
- For date concepts(including registration date) specify the format as 'Format: DD-MM-YYYY'
- For numeric concepts, mention 'Max value allowed:' or 'Min value allowed' if high or low absolute defined. Else mention 'Allowed values: Any number'
- For text and notes concepts, mention 'Any Text'
- Order of descriptions:
1. Optional
2. Allowed values/Max value, Min value/Format
3. Only single value allowed/Separate multiple values by a comma/Default value:
Sample file for prerelease, APF Odisha, create mode, individual registration form, Person subject type:
https://docs.google.com/spreadsheets/d/123ZLzB5xZnOSL95YetNVURHn-WZKYpXd1ctti8kr3lk/edit?usp=sharing
Technical:
Refer this pull request for doing this.
Out of scope:
Edit of forms.
- Add Legacy id and UUID as columns instead of Id column. (to prevent incorrect update of existing records)
- 'Mandatory' field descriptor can be removed
- For registration form, 'subject type' column should never get displayed.
https://docs.google.com/spreadsheets/d/15qgMLhA72-ta2ouC2uDDy_OvgDTj6U-tsaUUiys-cPY/edit?usp=sharing
Questions:
Mandatory(might be subject to value in other fields)
Inputs:
The text was updated successfully, but these errors were encountered: