Closed bnygren closed 3 months ago
discussed 9 May dev meeting with Yahaya, will follow up with more info.
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
Importing updated population values for a campaign is not ideal.
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.
With the transition to campaign-based population data the default population data file is unnecessary.
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
Proposed solutions:
Notes about proposed import behavior.
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)
Dcode: (integer)
Campaign_ID: (string)
TOTAL_AGE_0_4: (integer)
TOTAL_AGE_5_10 (integer)
modality: (string)
status: (string)
Partial imports: