Table of contents by first letter of term:
| Table of Contents |
|---|
| maxLevel | 1 |
|---|
| type | flat |
|---|
| separator | | |
|---|
|
...
...
| Table of Contents |
|---|
| maxLevel | 1 |
|---|
| type | flat |
|---|
| separator | | |
|---|
|
...
| Term | Definition |
|---|
Candidate COD | Candidate COD: COD with improved quality and standardization. ('created in the Process' phase in COD Cycle). Rationale for terms: common terminology in country/region, describe the state of the COD (phase in cycle), used in tagging on HDX. See COD Cycle. |
COD | See Common Operational DatasetS (CODs) |
COD-AB | An administrative Boundary COD is a spatial dataset that identifies the various administrative level boundaries, names and unique codes (P-codes) in a country. It is a core COD, and provides a spatial/visual way to view and analyse data as well as a common way of referring to places allowing datasets to be aggregated and analysed more easily. See Common Operational Datasets (CODs). |
COD-PS | Population Statistics COD is a tabular baseline demographic dataset that s (ideally) disaggregated by age and sex and presented at various levels of administrative levels in a country (includes P-codes). It is a core COD that is used to identify initial affected numbers and understand the pre-emergency situation. See: See Common Operational Datasets (CODs). |
COD-CS | See Country-Specific COD |
COD-HP | Humanitarian Profile COD that provides the number of people affected, including when relevant: displaced, missing, injured, dead, as well as people in need. It is a Core COD that is only available post crisis. It is used to make programmatic decisions. See the |
COD Cycle | Effective COD development is composed of six COD cycle functions: 1) plan, 2) collect, 3) process, 4) endorse, 5) communicate and 6) maintain. See Common Operational Dataset cycle. |
Common Operational Dataset (COD) | Authoritative reference datasets needed to support operations and decision-making for all actors in a humanitarian response. They provide essential baseline data and data standards that allow humanitarian actors to collaborate, coordinate and exchange information. CODs provide the basis for a common operational picture and a shared situational awareness. . |
Core Common Operatioanal Datasets | Core CODs are required in all countries with ongoing humanitarian operations or in which emergency response preparedness (ERP) activities are underway. They provide a critical data standard and support initial analysis in the first 48 hours of a new emergency of impact, scope and scale and thus inform decisions on any subsequent response. There are three Core themes: Administrative Boundaries, Population Statistics, and Humanitarian Profile. See Core Common Operational Datatsets: Administrative Boundary (COD-AB), Population Statistics (COD-PS), and Humanitarian Profile (COD-HP). |
...
| Table of Contents |
|---|
| maxLevel | 1 |
|---|
| type | flat |
|---|
| separator | | |
|---|
|
D
...
...
| Table of Contents |
|---|
| maxLevel | 1 |
|---|
| type | flat |
|---|
| separator | | |
|---|
|
E| Term | Definition |
|---|
| Endorsed COD | COD which has been accepted as the reference dataset to be used by the IM network in country. See Common Operational Dataset cycle. |
| ERP | Emergency Response Preparedness. To improve the humanitarian system's readiness to respond to breaking crises, the Inter-Agency Standing Committee (IASC) developed the Emergency Response Preparedness (ERP) approach. The aim is to increase the speed and volume of life-saving assistance delivered in the first four to six weeks of an emergency. For more information see: The ERP approach |
...
| Table of Contents |
|---|
| maxLevel | 1 |
|---|
| type | flat |
|---|
| separator | | |
|---|
|
...