# IPBES ICT documentation ## Introduction This repository holds the public user documentation for IPBES data management and IT services and tools. It is hosted on [ict.ipbes.net](https://ict.ipbes.net) The Intergovernmental Science-Policy Platform on Biodiversity and Ecosystem Services (IPBES) is an independent intergovernmental body, established by member States in 2012. It provides policymakers with objective scientific assessments about the state of knowledge regarding the planet’s biodiversity, ecosystems and the benefits they provide to people, as well as the tools and methods to protect and sustainably use these vital natural assets. Our mission is to strengthen knowledge foundations for better policy through science, for the conservation and sustainable use of biodiversity, long-term human well-being and sustainable development. To some extent IPBES does for biodiversity what the IPCC does for climate change. ## Contributing Our documentation is public because we want your help in improving and maintaining it. The code is hosted on . If you spot a problem, send us a pull request to fix it! If you're not sure how, you can also file an issue and we'll try to get to it ourselves. In order to maintain a consistent style and voice throughout our documentation please try to follow these standards and conventions when filing Pull Requests against our documentation. ### Markdown Our documentation site is built using [GitBook](https://github.com/GitbookIO/gitbook/). GitBook uses Markdown as its file format. * All files should end in `.md`. They should be all-lower-case and match the title of the page, or in some cases an abridged version of it. * All pages should start with a title, denoted with # (first level header). * Subsections within a page are encouraged, and should use ## for a 2nd level and ### for a 3rd level. Do not have more than 3 levels of header. * Inline code statements, file names, and keys that would appear in a file should use backticks like this `` ` ``. * Always use inline links. * Do not hard-wrap prose text. Set your text editor to soft wrapping. * Internal links should be absolute (starting with `/`) and link to a file ending in `.md`, not `.html`. That makes them easier to find when needed to update. ### Language usage * All documentation should be written in English. ### Getting help If you're facing any issues with IPBES IT services and tools, please send an email to . You can also reach us through the relevant technical support units of assessments or task forces ### Address IPBES Secretariat 10th floor Platz der Vereinten, Nationen 1 53113 Bonn (Germany) [![twitter icon](http://i.imgur.com/tXSoThF.png)](https://twitter.com/IPBES) [![facebook icon](http://i.imgur.com/P3YfQoD.png)](https://facebook.com/ipbes) [![github icon](http://i.imgur.com/0o48UoR.png)](https://github.com/ipbes)

## Zenodo --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://ict.ipbes.net/ipbes-ict-guide/readme.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.