Page Comparison

 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.

Listen to stakeholders at coordination meetings - they may have unpredictable requirements or unanticipated resources.

 Collect

Reach out to partners to see what is already in use or data sources from past disasters

Check HDX what is already tagged as COD other than the Core CODs

Select the best COD source and commit to it.  

 Process

Bring what is collected to IMWG to discuss

Verify and correct data 
Core CODs:  the P-code logic and completeness of COD-AB and COD-PS, then look at the spatial side of COD-AB

 Endorse Let FIS know about datasets so they can review Core CODs

 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 information about the dataset available through existing networks:
 your IM network, OCHA - FIS,  HQ agency,  Emergency coordinator, HCT, Cluster coordinators, Head of Office,  checked-in responders on humanitarian.idetc.

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.

Consider creating 'CODs to GO' to hand out to people leaving going into the deep field, 

Advocate immediately and firmly for the use of P-codes throughout the humanitarian response.  

Some responders may not know about CODs, share basic information about CODs, their purpose, value, and where to find them.

 Maintain 

 Make COD-CS part of your COD cycle