-
Notifications
You must be signed in to change notification settings - Fork 8
Closed
Labels
TCTC implements/leads the implementationTC implements/leads the implementation
Description
Hide Fields from the endpoint of dref
Note: Do not remove the field from the endpoint if it is being used in different DREF types and exclude if it's not in use in other types.
Hide the following fields
- Emergency appeal planned: Hide this field
emergency_appeal_planned - Upload map: Hide this field
event_map - Disaster Category: Hide this field
disaster_category - If available please upload Crisis categorization Analysis: Hide this field
- Previous Operations: Hide the whole section
- Description of the Event: Hide the whole section, only Total people at risk and Sources of information will remain visible
event_description - Glide Number
glide_code
Add the following fields
- Add new space to attach documents: Upload any additional support document (Optional)
- Add new text field: Explain the underlying vulnerabilities and risks the hazard poses for at-risk communities? : Text. Guidance: Based on comparison of past events, what humanitarian impacts do you expect? Of what magnitude? (e.g. last time there was a cyclone making landfall with this windspeed, XX houses were destroyed, and we had to launch a DREF/emergency appeal for CHF xxx)
- Add new text field: When and where is the hazard expected to happen? : Guidance: Narrative including Date and geographical areas
- Add new text field: Which of the expected severe humanitarian impacts of the hazard are your actions addressing? Why were these impacts chosen? --> Guidance: Prioritized impact of the foreseen disaster
- Add new field surge deployment ( Also add a validation check for the field)
- add new field Indirect cost ( Also add a validation check for the field)
- Create a model for the Early action with activities and budget.
Metadata
Metadata
Assignees
Labels
TCTC implements/leads the implementationTC implements/leads the implementation