...
Steps | Step details | Tips |
Plan | Focus on Core CODs before COD-CS datasets. | Coordinate: One cluster's information resources may fit another cluster's information requirements. For instance, the Nutrition cluster may have data the Health cluster requires. Use meetings/Skype etc. to communicate data needs and availability. |
Collect | Reach out to partners to see what is already in use or data sources from past disasters Start by reviewing (if there is any) what is tagged as COD on HDX (other than COD-AB & COD-PS) Select the best COD source and commit to it | |
Process | Bring what is collected to IMWG to discuss Evaluate dataset (in case multiple data), verify Consider adding P-codes to your COD-CS (consider the return on investment) | Generic PowerPoint presentation to start COD-CS discussion with IMWG |
Endorse | Make collaborative decision on which data should continue as COD-CS. Use the COD identification chart to guide your decision Let FIS know if you need support to review standard and quality of COD-CS |
|
Communicate | Share data on HDX (include metadata and identify any issues with data and the estimated time it will be corrected) | Share data ASAP even if not in perfect condition, include metadata. If there is nothing on HDX then people will start using what they can find which can lead to significant mistakes. |
Maintain | Follow the COD cycle and do yearly revision Review and revise the list of COD-CS |
|
...
1. At this writing, the most recent (2010) official guidance for sudden-onset emergencies is the IASC Guidelines - Common Operational Datasets (CODs) in - Disaster Preparedness and Response which specifies 48 hours.
More to come: INFORM is doing work on rapid analysis and will be able to provide more details about this.