/
Inactive Structure Marking
Inactive Structure Marking
NOTE: Ineligible Structure Marking for Family Module IS A SEPARATE SCOPING DOCUMENT
Status
# | Step | Status |
---|---|---|
1 | Responsible prepares rough business analysis/reqs doc | IN PROGRESS: Pierre Dane |
2 | Get CHAI review | |
3 | Get Akros Review | |
4 | Get Ona feedback | |
5 | Responsible - 1 iteration for feedback | |
6 | Ona sign off | |
7 | Ona tech spec scoping | |
8 | Ona LOE | |
9 | Ona scheduling |
Definitions
- Inactive structure: a non-valid structure that was created erroneously and should be removed from play completely (e.g., duplicate residential structure record created by accident)
- This is effectively soft deleting the structure
- Ineligible structure: a valid structure that is ineligible to participate in an intervention for a valid reason (e.g., a residential structure where the inhabitants are not currently residing but may return in the future)
- This is a form field specific to the activity
Requirements
- A user in the field should be able to select a structure displayed in the Reveal map and mark it as inactive
A user on the WebUI should be able to select a structure displayed in the Reveal map and mark it as inactive- The user should be asked to confirm this process before the operation is completed
- Tasks associated with this structure should also be marked as inactive
- Any structures that have been marked as inactive should be removed from the target denominator for all interventions
- Any historical data for that structure should no longer be measured as part of any indicators.
- Inactivity is not intervention-specific and applies to all interventions.
- We need to think about the downstream management of this 'inactive' structure with regards to potential CGR integration as well
- Lifecycle: a structure marked as inactive is inactive indefinitely. If another structure is built in that same exact GPS position, a new location would have to be added.
Workflow
- Structure created erroneously in one of two ways:
- Incorrectly enumerated
- Added in field accidentally (e.g. duplicates of other structures, inaccurate locations of existing structures, other user-error additions, etc.).
- The user navigates to the physical location of the structure as guided by the map view of the mobile client and confirms that this structure does not exist.
- Tap the structure.
- If no household has been registered:
- Structure Registration form/task presented to user before household registration:
- New field: Select type of structure (similar to IRS view)
- Residential structure
- Non-residential structure
- Non-existent structure - mark as inactive
- If non-residential A follow on question should ask "What type of structure is this?"
- "Kitchen", "Animal shelter", "Food storage", "School", "Lodge", "Shop", "Office", "Hospital", "Clinic", "No structure here", "Not habitable", "Other"
- If residential, next screen proceeds to ask questions about eligibility, see Ineligible Structure Marking for Family Module
- New field: Select type of structure (similar to IRS view)
- Structure Registration form/task presented to user before household registration:
- If household has been registered: We assume that a family has been incorrectly registered to this structure and should be moved to a correct structure
- Tap the three dots in the upper right-hand corner
- Select 'Move family registration'
- Search & select the relevant structure from the displayed map view or list view OR add a new structure for that family
- Recommend having a radius of selection, i.e. can only move family registration to a structure within 100m
- What to do for structures outside of this radius? Is it possible to create a holding table for registered families without a structure?
- If no family already registered to new structure - Save
- If family already registered to the structure:
- New form: Is this a multi-structure household?
- Recommend having a radius of selection, i.e. can only move family registration to a structure within 100m
- Tap the SAME structure that has been identified as inactive
- Follow steps 3.a.i.
- If no household has been registered:
Suggested MVP
Workflow: 1- 3a:
- User can mark inactive structure that do not have any family registration information already collected.
Views:
- Android - Structure registration form
- Android - Maps - Add colour coding for ineligible (grey) & inactive structures (black)
- Android - Maps - Add a card view for inactive structures
Suggested not in MVP
Workflow: 3b
- Ability to mark a structure inactive if it already has family registration. This includes functionality to:
- Register a multi-structure household
- Move a family from one household to another
Views:
- Android - New options in family view to:
- Mark as ineligible for current intervention
- Move registered household to new structure
- Android - New form in family view to move registered household to new structure
Views
We anticipate the following views to be impacted on with the creation of this feature:
Justification
Dependencies
Notes
- No structures are ever deleted from Reveal, they can only be marked as inactive.
- Data will never be deleted from Reveal, only removed from tables being queried for indicators.
Questions
Test Case
# | Step | Pass / Fail | Comment |
---|---|---|---|
1 | |||
2 | |||
3 | |||
4 | |||
5 | |||
6 | |||
7 | |||
8 | |||
Additional tester comments: |
, multiple selections available,
Related content
Ineligible Structure Marking for Family Module
Ineligible Structure Marking for Family Module
More like this
Release 5 Android Task Changes
Release 5 Android Task Changes
More like this
Reveal Focus Investigation Workflow test scripts
Reveal Focus Investigation Workflow test scripts
More like this
<Name/Date> Reveal 3.0.0 Test Script
<Name/Date> Reveal 3.0.0 Test Script
More like this
NTD Community Workflow
NTD Community Workflow
More like this
Dynamic Task Generation and Entity Persistence
Dynamic Task Generation and Entity Persistence
More like this