> 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/update-sample-metadata.md).

# Updating Sample Metadata

## Individual Sample Update

Individual edits can be made on 'Samples'. Scroll to the 'Edit' button on the right side of your sample list. Update the metadata and then click 'Update sample'.

**For more information on editing individual records, please download our guide below.**

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

## Batch (Bulk) Sample Update

Batch update for your samples is accessible by going to your 'Your Samples' or 'Team Samples' page. Navigate to this page under 'Samples' on the left hand panel. 

1. Select the samples that you want to batch update.
2. Click the 'Bulk Update' tool on top of the page.
3. On the 'Bulk update samples' popup, choose a field to update under 'Field to update'.
4. The left side, 'Before' will show the current metadata associated with the field you want to update. The right side, 'After' presents two options, the first to update the values and the other to clear any current values.
5. Under 'After', input the new value.
   1. Most fields will be free text. Certain fields such as 'Object type', 'General material type', and 'Material types' will be a drop down menu. 
   2. Other fields such as 'Age (min/ma/unit)' will have multiple fields. For 'Collector(s)', 'Launch platform', 'Cruise/field program' and 'Original archive', you will need to add an existing value pre-saved during registration or be asked to add a new 'collector', 'launch', 'archive' etc. 
6. Click ‘Update x samples’ (x represents the number of samples you choose to update).
7. Confirm your update is successful by reviewing your samples.

You can also bulk update samples for 'Sample Groups' by accessing the group you created and following the same process listed above. 

**For more information on batch update, please download our guide below.** 

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

### Updating Initiative, Platform, and Launch Platform

1. Navigate to 'Your Samples'.
2. Click the samples you wish to add 'Initiative', 'Platform', and 'Launch Platform'.
3. Click 'Bulk Update'.
4. Select 'Field to update' and find 'Cruise/field program'.
5. Select 'Add cruise/field program' which is your specific 'Initiative' or 'Clear field instead' if you want to remove the current 'Initiative' instead.
6. 'Add new initiative' or choose an existing one and click 'Done'.
7. If you added the wrong one, select 'Clear selection' and try again.
8. Click 'Update X samples' (x is the number of samples you selected) when you are finished to save your changes


---

# 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/update-sample-metadata.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.