> 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/register-samples/parent-child-relationships.md).

# Parent-Child Relationships

## **Children Samples - Hierarchical Sample Relationships**

Many objects that are sampled from the Earth yield subsamples. For example, sediment cores may be sampled at regular intervals, creating hundreds of individual samples from one core. This relation among samples is considered a parent-child relationship in the world of data management: sub-samples are children of a parent sample. Subsamples can be sampled themselves, leading to complex hierarchies.&#x20;

SESAR has been designed to record the relationship between samples and sub-samples. Subsamples have their own entry in SESAR and have independent IGSNs. The parent-child relationship is established by recording the IGSN of the parent in the child metadata profile. A parent sample must be registered with an IGSN before it can be listed as the parent of any child samples.

By adding a 'Parent IGSN' to a sample, the metadata profile page of the newly registered sample will show that it is a sub-sample of the sample that was listed in the ‘Parent IGSN’ field. The metadata profile page will also show all other samples (siblings) that share the sample parent. The metadata profile page of the sample whose IGSN was listed in the ‘Parent IGSN’ of the newly registered sample will also show that the newly registered sample is a sub-sample (child) of it.&#x20;

### Minting Children Samples and IGSNs

Now you can mint child IGSNs directly from a registered sample.

1. In your sample management page within your personal, team, and group samples, select the sample you want to mint a child from.
2. Click 'Mint Child'.
3. A popup page with the parent IGSN’s pre-populated metadata fields will show up. You can choose which fields you want to maintain and keep for the child sample.&#x20;
4. Click 'Continue to registration' which will prompt you to the 'Register a child sample' page.&#x20;
5. Follow the steps to register your child. This process is the same as the individual registration process.&#x20;
6. Once you submit, the child sample will be sent to the SESAR curator for review. Until it is approved, your sample will be labeled 'pending'.&#x20;

<img src="https://3999429579-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ftd44sRg81erEWSwelkyG%2Fuploads%2F2ab1e0g76TqjskslDV5l%2Funknown.png?alt=media&amp;token=9ebfb711-74a3-4cde-a7e6-098256548a99" alt="" height="539" width="624">

**For more information on minting children samples, please download our guide below.**&#x20;

{% file src="/files/lAjy3G8Y0BCimKjzPQix" %}


---

# 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/register-samples/parent-child-relationships.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.
