> 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/for-researchers/manage-samples/embargo-samples.md).

# Embargo Samples

SESAR follows the [National Science Foundation’s guidelines](https://www.nsf.gov/geo/geo-data-policies/ear/ear-data-policy-apr2018.pdf) of allowing sample metadata to be embargoed for up to 2 years from the date of registration. 1 month before your embargo period ends, you will receive an email from SESAR notifying you that the embargo on your sample metadata will soon end.  

In both individual and batch registrations, the system will only allow a release date up to two years from registration date. 

If you embargo your sample metadata, we recommend that you use a release date that matches the publication date of a related manuscript.


---

# 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/for-researchers/manage-samples/embargo-samples.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.