| 8 | | * current pr.person.tags should be sufficient to model this...although it needs the UI to be extended to support this use-case |
| 9 | | * We need UI to filter to just a speciifc Event/Incident |
| | 8 | * current pr.person.tags sufficient to model this? No as we need the status to map to an incident, simple incident/status doesn't allow clarity betwene missing in 1 incident & lost building in another |
| | 9 | * need UI to be extended to support this use-case (currently just 'personal impact of disaster') |
| | 10 | * We need UI to filter to just a specific Event/Incident: but it's the status that needs filtering not the person, so do we have a status table which tracks the event/incident tags? |
