COD Governance Model
- FIS (Unlicensed)
- FIS
- FIS
Overview
The COD governance is based on a Source, a Contributor and a Guardian. The contributor role may not be required as the source may directly be involved in COD work or a contributor may also fulfill a guardian role.
Source: Provides the original data that is used as a COD
The Source is owner or originator of a dataset. CODs ideally come from national authorities.
In many cases, the Source will maintain a working relationship with the Contributor to ensure that questions about datasets and metadata are answered and updates and improves are shared
Contributor: Is the interface between the data source(s) and the humanitarian community
Replaces the term “Sponsor” as it falls in line with HDX terminology
Responsible for preparing and processing a dataset to meet the quality standards established for CODs
Ensures the dataset goes through the COD cycle so it is endorsed by the IM network in the country and that improvements to the data are provided back to the Source where appropriate.
May be responsible for sharing the dataset on HDX (and/or other platforms) with appropriate metadata when possible. (based on IM network COD strategy)
Maintains awareness of new updates becoming available and known problems in the dataset
Maintains close relationships to Sources and, if data license is not clear, develops data sharing agreement with the Source.
Communicates dataset updates to partners via channels established in the TSP.
Responsible for dealing with multiple data sources if required to merge/process data
Adding expiration date of COD to metadata
Guardian: Coordinator of CODs and ensures that COD process is followed
Overall responsibility for verifying that a dataset shared as CODs meet the quality standards established in this TSP
Overall responsibility for verifying the dataset goes through the COD cycle so it is endorsed by the IM network and the HC
Overall responsibility that a published update cycle is followed.
Maintains close relationships with and provides support to Contributors, provides suggested improvements to the data are provided back to the Contributor and Source where appropriate
May be responsible for sharing the dataset on HDX (and/or other platforms) with appropriate metadata when possible. (based on IM network COD strategy)
Communicates dataset updates to partners via channels established in the TSP.
Coordinate connections among data contributors/ IM network if required,
Examination of expired CODs and tagging on HDX
FAQ
Can an organization hold multiple roles?
Yes an organization can hold multiple roles (e.g. OCHA can be the contributor and guardian for COD-AB) (e.g. WHO can be the contributor and guardian for Health Facilities) (e.g. UNHCR is a source, contributor, and guardian for refugee statistics)
2. Are all partners aware of this governance model?
Yes, it was discussed and agreed to at the global level IMWG but it is possible that partners you are working with are not aware of it. To avoid confusion, the COD governance model should be discussed and agreed to in each country/emergency at the beginning of the COD discussion/ work plan. If the model does not work for the situation the IM network is facing then changes should be made and agreed to by the group. This impacts the COD agreement that is required (suggested COD agreement template)
3. What happens in these scenarios?
1) In a country with an OCHA country office with IM capacity (e.g. Sudan)
All partners share their AB datasets and decide on a COD. OCHA should become the Contributor and the Guardian unless another agency has a better relationship with the data sources
2) In a country with no OCHA presence but is high risk (e.g. Sri Lanka) or in a country with an OCHA HAT with no IM capacity (e.g. DPRK)
The OCHA regional office should check with any agencies or organization already working in the country to identify what they are currently using. The organization that is in the country and already has the relationship with the data source should be the Contributor and OCHA can become the Guardian to ensure it is shared and updated appropriately. A close relationship with the data Contributor is required. If a AB dataset is not being used OCHA should check with the global level for activities related to this dataset. If no one at the global level is working on the datasets or it is not appropriate, then OCHA should contact the government (data source) and become the contributor and guardian.
3) In a country with no OCHA presence but with a partner with strong IM capacity such as UNHCR (e.g. Iran)
The OCHA regional office should check with the partner agency (e.g. UNHCR) already working in the country to identify what they are currently using. The organization that is in the country and already has the relationship with the data source should be the Contributor and OCHA can become the Guardian to ensure it is shared as a COD and updated appropriately. A close relationship with the data Contributor is required. If an AB dataset is not being used OCHA should check with the global level for activities related to this dataset. If no one at the global level is working on the datasets or it is not appropriate, then OCHA should contact the government (data source) and become the contributor and guardian.
Resources
Guidance on CODs: Guidance on CODs in Emergency Preparedness and Response (Draft 2016)
Former Guidance on CODs: IASC Guidelines CODs in Disaster Preparedness and Response (2010)