population import UI/feature refinements

[bnygren]

Importing updated population values for a campaign is not ideal.

1. The population export from within the import popup lacks Dcodes and includes a bunch of inherited fields from SORMAS that aren't used in APMIS campaigns.

2. With the transition to campaign-based population data the default population data file is unnecessary.

3. There is also a "Download Import Template". This includes two rows of comment variables prefaced by ## which, if left in the import file, caused an error.

"Region" is incorrectly appearing as a header/variable in this file when in fact it is Province

region	district	campaign	TOTAL_AGE_0_4	TOTAL_AGE_5_10	modality	districtstatus
##Province	District	campaign	TOTAL_AGE_0_4	TOTAL_AGE_5_10	modality	districtstatus
##Code of Region	Code of District	UUID of Campaign	Number	Number	Text	Text

Proposed solutions:

1. Update the campaign population export file to include the correct headers for APMIS, with Region, Rcode, Province, Pcode, District, Dcode, Campaign_ID, TOTAL_AGE_0_4, TOTAL_AGE_5_10, modality, and districtstatus. This exported file could be modified and used as an import file to update the campaign population. If there are no population/modality/status values for the campaign yet (e.g., the campaign is new, and not a duplicate), then the file would contain no population/modality/status values.
2. Remove default population data export button.
3. Import Template: Allow imports to ignore the ## commented rows. Drop Region column as it is not necessary. Include Dcode, Campaign_ID, TOTAL_AGE_0_4., TOTAL_AGE_5_10, modality and status, as these should be the fields that are actionable during import.

Notes about proposed import behavior.

• The population export file would contain Region, Rcode, Province, Pcode, District. These fields provide a complete, human-readable population file that would be useful to export. However, Dcode would be the UID for the row. Thus, if these, or other fields (except those described below) are included in the import, they should be ignored.

The import fields the system should recognize are Pcode (added 23-May, per discussion), Dcode, Campaign_ID, TOTAL_AGE_0_4. TOTAL_AGE_5_10, modality, and districtstatus,) and should be handled as such during import:

PCode: (Integer)

• Required column
• Should match with existing database Pcode + Dcode for that district

Dcode: (integer)

• Required column
• Required value for all rows in import.
• UID for the row.
• Use this value to match to existing Dcode in system and update district's population, modality or status.

Campaign_ID: (string)

• Required column
• Required value for all rows in import.
• Must be single value for all rows that matches the current campaign the user is trying to modify

TOTAL_AGE_0_4: (integer)

• Required column
• Required value for all rows in import.
• (is population under 5)

TOTAL_AGE_5_10 (integer)

• Optional column
• Optional value in rows
• (is population 5-10, but not all places use this)

modality: (string)

• Optional column
• If modality column is included in the import file, value for modality must be included

status: (string)

• Optional column
• If column is included in the import file, value for status must be included

Partial imports:

• Optional columns: if TOTAL_AGE_5_10, modality, or districtstatus columns are not included, then any values for these fields in the database are unchanged
• Incomplete number of rows (not all dcodes included): Typically, the population is carried over from the previously duplicated campaign. Then updated values are made available in a file potetnially for one area, and the admin user wishes to update these values only. e.g., If there are 400 districts and the user wishes to update 37 age 0-4 values, they can prepare the file with Dcode, Campaign_ID, and TOTAL_AGE_0_4 columns, check the overwrite box, upload 37 new population 0-4 values for these districts, but the rest of the districts population values should be unaffected. This worked on Test.

[bnygren]

discussed 9 May dev meeting with Yahaya, will follow up with more info.

[bnygren]

Per 22-May discussion with @DevSeg we agreed that PCODE is required for import; DCODE column should be titled 'DCode' not 'district'. Export column order should match import. Thanks