> 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/cite-and-credit/cite-igsn-ids-in-publications.md).

# Cite IGSN IDs in Publications

SESAR asks its users to include IGSNs in their manuscripts. This allows publishers to link the IGSN sample metadata profile pages to the manuscript. Tagging IGSNs in manuscripts aligns with the National Science Foundation's [commitment to FAIR data](https://www.nsf.gov/pubs/2019/nsf19069/nsf19069.jsp) as well as publishers such as [AGU](https://www.agu.org/Publish-with-AGU/Publish/Author-Resources/Text-requirements), [GSA](https://www.geosociety.org/gsa/positions/position7.aspx), [Wiley](https://rmets.onlinelibrary.wiley.com/hub/journal/20496060/features/guidelines-for-reviewers), [Elsevier](https://www.elsevier.com/journals/palaeogeography-palaeoclimatology-palaeoecology/00310182/guide-for-authors#89003), [Copernicus](https://www.copernicus.org/news_and_press/2017-05-19-igsn-now-includable-in-article-assets.html).

All data obtained from SESAR should be adequately cited following license-specific requirements and/or the following structure from DataCite's guidelines for citing IGSNs:

**Creator (Year of Registration). Sample Name/Title \[Internet]. Publisher (e.g., SESAR). IGSN: \[identifier].**

**Example:**

Smith, J. (2023). Basalt sample from Kilauea flank \[Internet]. San Diego, CA (USA): System for Earth Sample Registration (SESAR). IGSN: 10.58052/IEJSM0001.

A few notes to include alongside this guidance:

* **Register the IGSN as a resolvable identifier.** Where possible, express the IGSN as an actionable link (e.g., <https://doi.org/10.58052/IEJSM0001> or <https://igsn.org/IEJSM0001>) rather than plain text, so it resolves to the sample's landing page.
* **Follow journal/discipline style where one exists.** Many geoscience journals and repositories now request IGSNs be included in data availability statements or sample tables — check your target journal's author guidelines, since exact placement and formatting can vary.
* **Note that PID citation is not full metadata citation.** The DataCite style citation above supports discovery and attribution; it's not a substitute for describing sample context (collection method, location, etc.) in the body of a publication.
* **Cite the registering repository, not just the sample.** Since SESAR is the "Publisher" of record for the IGSN, it should appear in the citation regardless of who physically collected or curated the sample.


---

# 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/cite-and-credit/cite-igsn-ids-in-publications.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.
