> For the complete documentation index, see [llms.txt](https://docs.pacificdata.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pacificdata.org/catalogue/user-guide.md).

# User Guide

For an introduction on how to use the Data Catalogue see this video:

{% embed url="<https://youtu.be/H1KBLkZUR2s>" %}

### How to get started with the Data Catalogue

Go to the Pacific Data Hub home page <https://pacificdata.org/>

You will be redirected to the Data Catalogue when you make your data search either using the **Search bar** or the **Shortcuts** located below.

![](https://3496061366-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MDSpD50SdXxsYnU7P9D%2F-MKb6SSXXODRbzH6vl_n%2F-MKb7y0tlNAE-SO34QvT%2Fimage.png?alt=media\&token=7c6cd5d1-e3d9-47f4-88b3-2f13970d6efa)

### Search data

In this example we have typed "cyclone" in the search bar and redirected to the Data Catalogue

![](https://3496061366-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MDSpD50SdXxsYnU7P9D%2F-MKb7zUvKou1NOvN6h2n%2F-MKb8zIp3Kzi9Okjhh_h%2Fimage.png?alt=media\&token=e7085d48-5fe3-453a-88db-dc642f8ebf94)

We can order our results by relevance, popularity, name or last modification using the **Order by** button

To narrow down the data search we can use the filtering tools located on the left. The filters available are **Topic, Member countries, Organisations, Tags, Formats, Dataset type and Licenses.**

![](https://3496061366-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MDSpD50SdXxsYnU7P9D%2F-MKb7zUvKou1NOvN6h2n%2F-MKbAhcCowzj6_wavqNQ%2Fimage.png?alt=media\&token=b442846a-82e2-46c7-a3ba-b27e5a1bfb78)

### Explore inside the dataset

Once you have found the dataset you are looking for, click on it to open the Dataset screen.

* On top of the screen you will find the dataset's title and description.&#x20;
* You can export the metadata by clicking on the **Export Metadata** button located below the description.
* Metadata can be accessed on the bottom of the page.
* A number of different data resources with various formats can be linked to the dataset.&#x20;
* Click on the resources to access the resource page where you will find the description, a preview pane and a download link.
* Different preview screens are available depending on the format of the file.&#x20;

![](https://3496061366-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MDSpD50SdXxsYnU7P9D%2F-MKb7zUvKou1NOvN6h2n%2F-MKbDApdv1Gk6SKcjCm9%2Fimage.png?alt=media\&token=93dc2d30-805e-4fd0-823a-29cc2aed47ce)

* At the bottom of the file you will find shortcuts to access the other resources linked to the dataset.

![](https://3496061366-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MDSpD50SdXxsYnU7P9D%2F-MKb7zUvKou1NOvN6h2n%2F-MKbFwxck9hbEE_fYlfz%2Fimage.png?alt=media\&token=bd7d9bca-4ad9-42d1-9be8-ad732a54ae48)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pacificdata.org/catalogue/user-guide.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
