Code | Variable | Codes/Description | Comments/Description |
RBO | Code of the RBO | RBO Code | each RBO has a 4-letter code (if necessary, followed by X); they are based on the general abbreviations of these RBOS, most often on the basis of their acronyms |
RIV | Code of the river | River Code | compliant with TFDD river codes (in some cases, the river is a sub-basin of a TFDD river, then the code refers to the main basin while the river name - next variable - captures the sub-basin itself) |
RIV_NAME | Name of the river | Name | if an RBO covers more than 1 river, the RBO is listed separately for each river one after another (building on the assumption that there are RBO-RIV-pairs) |
RBO_NAME | Name of the RBO | Name | full name of the RBO |
AGREEMENT_NAME | Name of the agreement on which the RBO is based | Name | Name of the agreement in original language/language in which the agreement was analyzed; additionally, English translation is provided (not official translation) |
AGREEMENT_DATE | Year in which the RBO was established | year | in some cases, the RBO relies on an agreement signed earlier then the actual establishment of the RBO, therefore, in some cases 2 years are given (this might, however, pose problems when using the data for analysis and needs to be adjusted for those cases) |
RIP_NAMES | Names of riparian states | Name | Names of riparian states to the watercourse (watercourse the RBO refers to, not main watercourse - e.g. for the Lake Victoria it would refer to the riparians to the lake, not all Nile riparians with the Lake Victoria being a sub-basin to the Nile) |
RIP_NO | Number of riparian states | number | Number of riparian states to the watercourse (watercourse the RBO refers to, not main watercourse - e.g. for the Lake Victoria it would refer to the riparians to the lake, not all Nile riparians with the Lake Victoria being a sub-basin to the Nile) |
MEMB_NAMES | Names of member states of the RBO | Name | Names of member states of the RBO (signatories to the agreement, either from beginning or through joining later) |
MEMB_NO | Number of member states of the RBO | number | Number of member states of the RBO (signatories to the agreement, either from beginning or through joining later) |
LATERALITY | Laterality of the RBO | bilateral; multilateral | an RBO is bilateral if it has 2 members and multilateral if it has more than 2 members (independent of the number of riparian states to the basin) |
INCLUSIVENESS | Inclusiveness of the RBO | inclusive; non-inclusive | an RBO is inclusive, if it includes all riparian states to the basin as its members, it is non-inclusive if at least one riparian state to the basin is not a member to the RBO |
ISSUES_NAMES | Description of functional issues | Name | lists functional issues and scope of the work/mandate of the RBO in descriptive form |
ISSUE_TYPES | Types of functional issues | QUAL (water quality); QUAN (water quantity); ENVP (environmental protection); FISH (fisheries); HYDR (hydropowe); TIMB (timber issues and forestry); NAV (navigation); AGRI (agriculture and irrigation); SOCD (socioeconomic development); TOUR (tourism); FMGT (flood management); DMGT (drought management); EROS (erosion); CLIM (climate change); DRIN (drinking water); GROU (groundwater); COMM (communication infrastructure); IND (industry); MIN (mining); BIOD (biodiversity protection); INVSP (invasive species); ENGY (energy); TRAN (transport); TRAD (trade); HRDV (human resources development); INVES (investments); DISA (disaster management); RES (scientific research);HEAL (health protection/sanitary measures); RINT (regional integration); INFR (infrastructure) | captures the types of functional issues an RBO deals with |
ISSUE_NO | Number of functional issues | number | |
ISSUE_SCOPE | Functional scope of the RBO | 1 = SIN (single); 2-4 = FEW (few); >5 = MUL (multi) | distinguishes between single-, few- and multi-issue RBOs depending on number of functional issues the RBO is mandated to deal with |
ISSUE_BROAD | River-relatedness of functional issues | TRV (to the river); BRV (beyond the river); TBR (to and beyond the river) | captures the river-relatedness of the functional scope of the RBO, distinguishing between functional issues that concern water resources management in the narrow sense/are related to the river and those that are related to issues other that water resources management in the narrow sense/go beyond the river |
WAT_LAW_REF | Reference to water law principles | yes; no | captures whether the RBO is based on formal water law principles that are mentioned in its underlying agreement or other legally relevant documents |
WAT_LAW_PRINC | Type of water law principles | OBCOOP (obligation to cooperate); FREENAV (freedom of navigation); EQUSE (equitable and reasonable use); SIGHARM (obligation not to cause significant harm); RIPCOM (principle of riparian community); DISPSET (obligation to seek peaceful dispute settlement); NOTIF (obligation of prior notification); CONSULT (obligation of prior consultation); AGREE (prior agreement); POLLPAY (polluter pays principle); PRECAU (principle of precaution); SUSDEV (principle of sustainable development); UNCONV (1997 Convention); HELRU (Helsinki Rules) | categorizes different water law principles, relying on the most common water law principles and the most prominent ones (those codified in international conventions); also captures if an RBO relies not only on specific principles but refers to an international convention (which itself then contains certain principles) such as the 1997 UN Convention or the Helsinki Rules |
LEG_PERS | Legal personality of the RBO | yes; no | distinguishes between RBOs equipped with legal personaly according to international law (defined in underlying treaty) and RBOs without legal personality |
ORG_TYPE | Type of organization | Committee; Commission; Authority | captures the type of organization of the RBO (Committee, Commission, Authority) and thus the level of institutionalization of the RBO |
ORG_BOD_NAMES | Name of organizational bodies | Name | lists organizational bodies of the RBO |
ORG_BOD_TYPES | Types of organizational bodies | MHS (Meeting of Heads of State/Gov); COM (Commission); CON (Council); TEC (Technical Committee); SEC (Secretariat); WEG (Working/Expert Groups); NAC (National Coordination Bodies); DON (Donor Relations Body); ADTEC )additional Technical Committees); OTH (others/non-specified) | captures the different types of organizational bodies in categories |
ORG_BOD_NO | Number of organizational bodies | number | number of organizational bodies in total (this does not necessarily correspond with the type of organizational bodies since an RBO can, for example, have two or more Technical Committees); however, Expert and Working Groups are summarized under WEG without listing their total amount (e.g. 4 Expert and 3 Working Groups) given the flexible nature of this type of organizational body, often changing over time due to changes in the RBO's functional scope and mandate |
ORG_BOD_QUAN | Organizational body scope of the RBO | 1 = SIN (single); 2-4 = FEW (few); >4 = MUL (multi) | distinguishes between RBOs with one (single), few or many (multi) organizational bodies |
SEC_EX | Existence of a Secretariat | yes; no | captures whether the RBO has Secretariat in place |
SEC_FUNC_NAMES | Name of functions of the Secretariat | Name | lists the functions of the Secretariat of the RBO |
SEC_FUNC_CLASS | Type of functions of the Secretariat | DATA (data and information management); AGEN (agenda setting); EXFUN (acquisition of funding); DONRE (donor relations); COOR (coordination of projects/programs); IMPL (implementation); PROP (project operation); MON (monitoring); CAPB (capacity building); BDGT (budget preparation); MORG (meeting organization); ADSERV (administrative services); FINSERV (financial services); REP (reporting on meetings); EXREL (external relations); RES (reserach); OTH (others) | captures different categories of RBO Secretariat functions |
SEC_FUNC_NO | Number of functions of the Secretariat | number | number of Secretariat functions |
SEC_FUNC_QUAN | Secretarial functions scope | 1 = SIN (single); 2-4 = FEW (few); >5 = MUL (multi) | distinguishes between Secretariats with one function (single), few functions and many functions |
DEC_MAK_SPEC | Specification of decision-making mechanisms | yes; no | captures whether decision-making mechanisms are defined for the RBO |
DEC_MAK_NAMES | Description of decision-making mechanisms | Name | describes the decision-making mechanisms of the RBO |
DEC_MAK_MEC | Type of decision-making mechanism | COS (consensus); UNA (unanimity); MAJ (majority); MIX (mixed); OTH (other) | describes the type of decision-making mechanism along 3 categories - consensus, unanimity, majority (and other mechanisms or combination of any of the 3 categories) |
DEC_MAK_BIND | Bindingness of decisions taken | yes; no | refers to the bindingness of decisions by capturing whether the agreement or other legal documents on which the RBO is based clearly determine that decisions are to be binding |
INF_SHAR_EX | Existence of information-sharing mechanisms | yes; no | captures whether mechanisms for sharing information are established at the RBO/defined for the RBO |
INF_SHAR_MEC | Description of information-sharing mechanisms | Name | describes information-sharing mechanism of the RBO |
INF_SHAR_ISSUE | Functional issue on which information is shared | QUAL (water quality); QUAN (water quantity); ENVP (environmental protection); FISH (fisheries); HYDR (hydropower); NAV (navigation); AGRI (agriculture and irrigation); SOCD (socioeconomic development); TOUR (tourism); FMGT (flood management); DMGT (drought management); CLIM (climate change); DRIN (drinking water); GROU (groundwater); SEDS (sediments); HYDRO (hydrology); METEO (meteorology); GEO (geophysical); INF (infrastructure schemes) | captures the issues an RBO is collecting information on; often, though not always, overlapping with the functional scope of the RBO |
INF_SHAR_LEV | Level of information-sharing | INS (institution); BIL (bilateral); EXT (external) | captures level of information-sharing by differentiating between information-sharing by the RBO (institutional), between the member states bilaterally/state-to-state (bilateral) or by other external actors (external) |
INF_SHAR_RIV | River-relatedness of information-sharing | TRV (to the river); BRV (beyond the river); TBR (to and beyond the river) | captures whether information shared through RBO is related to the river/water resources governance in the narrow sense (to the river), to issues other than river basin management (beyond the river) or a combination of both (to and beyond the river) |
DISP_RES_EX | Existence of dispute resolution mechanisms | yes; no | captures whether dispute-resolution mechanisms are defined for the RBO |
DISP_RES_MEC | Description of dispute resolution mechanisms | Name | describes the dispute-resolution mechanisms |
DISP_RES_TYPE_1 | Type of dispute resolution mechanism at first instance of dispute resolution | RBOTRIB (RBO-internal mechanism); EXTRIB (external mechanism involving third parties); NEG (negotiation directly between disputing parties without RBO involvement) | describes the first instance of dispute resolution, differentiating between RBO-internal solution/mitigation (RBOTRIB), external mitigation or arbitration (EXTRIB) and direct negotiation between parties involved (NEG) |
DISP_RES_TYPE_2 | Type of dispute resolution mechanism at second instance of dispute resolution | RBOTRIB (RBO-internal mechanism); EXTRIB (external mechanism involving third parties); NEG (negotiation directly between disputing parties without RBO involvement) | describes the second instance of dispute resolution, differentiating between RBO-internal solution/mitigation (RBOTRIB), external mitigation or arbitration (EXTRIB) and direct negotiation between parties involved (NEG) |
DISP_RES_LEV_1 | Level of dispute resolution mechanism at first instance of dispute resolution | BIL (bilaterally between disputing parties); INS (institutional by RBO); EXT (externally by other party) | describes level of first instance of dispute resolution, differentiating between institutional (by the RBO), bilateral (between disputing parties) and external (by any third party outside of RBO) |
DISP_RES_LEV_2 | Level of dispute resolution mechanism at second instance of dispute resolution | BIL (bilaterally between disputing parties); INS (institutional by RBO); EXT (externally by other party) | describes level of second instance of dispute resolution, differentiating between institutional (by the RBO), bilateral (between disputing parties) and external (by any third party outside of RBO) |
MON_EX | Existence of monitoring mechanisms | yes; no | |
MON_MEC | Description of monitoring mechanism | Name | describes the monitoring mechanisms of the RBO |
MON_ISSUE | Issues that are concerned by monitoring activities | QUAL (water quality); QUAN (water quantity); ENVP (environmental protection); FISH (fisheries); HYDR (hydropowe); TIMB (timber issues and forestry); NAV (navigation); AGRI (agriculture and irrigation); SOCD (socioeconomic development); TOUR (tourism); FMGT (flood management); DMGT (drought management); EROS (erosion); CLIM (climate change); DRIN (drinking water); GROU (groundwater); COMM (communication infrastructure); IND (industry); MIN (mining); BIOD (biodiversity protection); INVSP (invasive species); ENGY (energy); TRAN (transport); TRAD (trade); HRDV (human resources development); INVES (investments); DISA (disaster management); RES (scientific research);HEAL (health protection/sanitary measures); RINT (regional integration); INFR (infrastructure) | captures the different issues that can be monitored by the RBO, often overlapping with the RBOs functional scope; however, in case of compliance monitoring, monitoring does not necessarily cover functional issues but rather the compliance with the agreement and RBO decisions (captured with n/a) |
MON_SCOPE | Scope of monitoring | COMPL (compliance monitoring); ENVMON (environmental monitoring) | captures whether monitoring focuses on the environment and the state of the basin (environmental monitoring) or on compliance of members with the underlying agreement and the RBO's decisions (compliance monitoring) |
MON_LEV | Level of monitoring | INS (institution); BIL (bilateral); EXT (external) | captures the level of monitoring, that is, whether the monitoring is done by the RBO in an institutionalized manner (INS) or bilaterally by member states (BIL) or by a third party (EXT) |
ADAP_EX | Existence of adaptation mechanisms | yes; no | captures the existence or non-existence of mechanisms for adapting to changes/changing the RBO's underlying documents in case needed |
ADAP_MEC | Description of adaptation mechanisms | Name | describes adaptation mechanisms of the RBO |
FUND_SPEC | Specification of funding mechanisms | yes; no | captures whether funding mechanisms are defined for the RBO |
FUND_MEC | Description of funding mechanisms | Name | describes the RBOs funding mechanisms/where RBO funds come from |
BUD_MEC | Description of budget procedure of the RBO | Name | describes the RBOs budget mechanisms/how the budget of the RBO is set-up and decided on |
CST_SHAR_EX | Specification of cost-sharing mechanisms | yes; no | captures whether specific mechanisms for sharing financial costs among RBO members are defined |
CST_SHAR_MEC | Description of cost-sharing mechanisms | Name | description of the cost-sharing mechanism of the RBO |
CST_SHAR_TYPE | Type of cost-sharing mechanism | EQL (equal); KEY (key-based); OTH (other) | captures whether members of the RBO share costs equally (EQL), on the basis of a specific cost-sharing mechanism or key (KEY) or through other means (OTH) |
DON_INV_EX | Donor involvement | yes; no | captures whether donors/development partners are involved in financing the RBO (through financial or technical assistance) |
DON_ID | Name of key donors involved in financing the RBO | Name | captures the main donors; does not provide complete list of all donors to the RBO but provides insights into who are the most important donors for this RBO; donors mentioned are listed in an alphabetical order, not implying any reference to their respective importance |
BEN_SHAR_EX | Existence of benefit-sharing mechanisms | yes; no | captures whether specific mechanisms for sharing benefits exist for the RBO/have been defined in the agreement or other underlying documents of the RBO |
BEN_SHAR_MEC | Description of benefit-sharing mechanisms | Name | describes the benefit-sharing mechanisms of the RBO |
PUB_PART_EX | Existence of public participation mechanisms | yes; no | captures whether mechanisms exist for public participation and the inclusion of civil society and NGOs in river basin management |
PUB_PART_MEC | Description of public participation mechanisms | Name | describes the RBO's public participation mechanisms |
PUB_PART_TYPE | Type of public participation mechanisms | INF (information-sharing); CONS (consultation); DECP (inclusion in decision-making); MON (monitoring); OBS (observer to meetings); PART (participation in projects) | categorizes public participation into information-sharing (INF) - referring to the RBO sharing information with stakeholders through reports, websites, communication, etc., consultation (CONS) - referring to RBOs that hold consultations with stakeholders on specific issues, the participation in decisions (DECP) - capturing the possibilities of stakeholders to take part in decisions made by the RBO, the granting of observer status (OBS) to civil society organizations and NGOs, and the participation in projects (PART) |
EX_COOP_EX | Existence of mechanisms for cooperating with external actors and third parties | yes; no | captures whether there are mechanisms for the RBO to cooperate with third parties |
EX_COOP_MEC | Descriptions of mechanisms for cooperating with external actors and third parties | Name | describes mechanisms for cooperation with third parties |
EX_COOP_PART | Cooperation partners | Name | lists partners for cooperation, such as other international organizations, other states (non-members), representatives of the scientific/epistemic community |