> For the complete documentation index, see [llms.txt](https://docs.geosamples.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geosamples.org/getting-help.md). # Getting help ### Email reaches the SESAR curators. It's the right address for essentially everything: registration problems, metadata questions, vocabulary requests, access requests, and anything you can't find here. ### What to include You'll get a faster answer if you include: * Your **SESAR Code** and **ORCiD** * Specific **IGSN IDs**, if the question is about particular samples * What you tried, and what happened instead ### Common requests, and where they go | I want to… | Go to | | ------------------------------------- | ------------------------------------------------------------------------------------------------------ | | Add a term to a controlled vocabulary | [**Request a term**](/vocabularies/request-a-term.md) | | Get API access | [**Request web services access**](/for-researchers/accounts-and-access/request-web-services-access.md) | | Remove a sample | [**Deactivate samples**](/for-researchers/manage-samples/deactivate-samples.md) | | Hand samples to someone else | [**Transfer ownership**](/for-researchers/manage-samples/transfer-ownership.md) | | Onboard an institutional collection | **For Institutions & Repositories** \[COMING SOON] | | Report a problem with these docs | | ### Suggesting a metadata field If your community needs a field SESAR doesn't have, we want to hear about it. SESAR's schema has grown in response to community need, and it continues to. Email us with what you need and why. ### Collaborating with SESAR We work with communities on software improvements, tool development, and discipline-specific sample metadata profiles. If SESAR could help solve a problem you have, email . --- # 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.geosamples.org/getting-help.md?ask=&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.