When 'Hide jurisdiction fields' featuretype is enabled, imports and exports should consider the fact that the jurisdiction fields are not displayed in the UI

[adinaflorea9]

Problem Description

When the featuretype 'Hide jurisdiction fields' is enabled, imports and exports do not take it into account.

Proposed Change

Make sure that imports and exports take into account whether the 'Hide jurisdiction fields' is enabled or not.

Added Value/Benefit

Consistency between the data displayed in the SORMAS UI and the imports and exports done.

Acceptance Criteria

• [ ] in the grids persons, cases, contacts, events, event participants, samples (human and environmental), immunizations, entries and campaigns the import and export should take into account whether the 'Hide jurisdiction fields' feature is enabled;
• [ ] if enabled, the exports should not include columns related to the region, district or community of the entities;
• [ ] if enabled, the imports should take into account whether the data from columns for region, district and community match those that are set as default for the hide jurisdiction fields feature; if the entries do not match, display an error message when the import is attempted and in the 'Error report' that can be generated for failed imports;
• [ ] the error message should be similar in display, text and style to the other possible error messages received for imports; the text can say something along the lines of 'The data for region, district or community can not be found in the database' (we have a similar message when trying to do merge duplicate cases while the hide jurisdiction feature is enabled, and we have potential duplicates from outside the default region, district and community).

Implementation Details

No response

Mockups

No response

Additional Information

No response