3. 3
Database
Content-wide criteria
Priority
(1-5)
Scope of the database
The hosting database of best practices is relevant to thematic topics of UNCCD best practices1
.
Indicators:
- Scope of the database
Values: Yes (1 to 7):
- Sustainable land management (SLM) technologies, including adaptation;
- Capacity-building and awareness-raising;
- Desertification, land degradation and drought (DLDD), and SLM monitoring and assessment/research;
- Knowledge management and decision support;
- The policy, legislative and institutional framework;
- Financing and resource mobilization;
- Participation, collaboration and networking.
Reference values: one theme; > 3 themes; > 7 themes.
5
Management of record property rights
The hosting database of best practices is able to manage property rights related to the technology, at record level like description of the
property rights, usage of the content of the record, etc.
Indicators:
- Management of property rights
Values: Yes/No
Reference values: Yes
5
Source of data and metadata management
The source of information stored in the database is clearly identified. Relevant Metadata is provided.
5
1
As contained in document ICCD/COP/(9)/18/Add.1 and decision 13/COP.9, annex V.
6. 6
Possible values:
- Scale out: an integer between 0 and 100
- Scale up: an integer between 0 and 100
Reference values:
- Scale out: > 2
- Scale up: = 0
Explanation: the hosting provider will merge existing best practices records with UNCCD records. The themes associated to UNCCD
records can be implemented in the DBMS as additional tables linked to the table of best practices or can be stored in a separate
database. In the latter, the costs of accessing records dispersed in different databases will be higher. The first case considers a
normalized database where a primary key of the best practice records table can be associated to one theme in a specific separate table.
- Scalability of the application:
- Level of coupling for these web interfaces:
- Search mask
- Detailed mask
- Modification mask
Possible values:
- Loose coupling: categories like themes will be managed in existing web interfaces
- Tight coupling: categories will be managed in separate web interfaces, separately developed and maintained.
Reference values:
- Loose coupling
Explanation: Coupling refers to the ways in which and degrees to which one part of the system relies on the details of another part.
The tighter the coupling, the more changes in one part of the system will ripple throughout the system. With loose coupling, the
interfaces between subsystems are well defined and restricted. What lies beyond those interfaces can change without any changes
needed in the client sub systems. For UNCCD, it is required that the web interfaces used to display, collect, modify best practices
records will support categories like the Themes and any future categorization required by the Governing Body with low impact on
existing web interfaces and low costs of development and maintenance.