> For the complete documentation index, see [llms.txt](https://c-comp.gitbook.io/data-management-handbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://c-comp.gitbook.io/data-management-handbook/sending-samples-to-other-labs.md).

# Sending samples to other labs

Please follow these guidelines to send samples to other labs for further analysis. 

In addition to sending physical samples to the receiving lab(s), the lab of sample origin is responsible for sharing this completed metadata spreadsheet (see template below) and assigning Sample IDs for each sample. Sample IDs should be assigned by the lab of origin so that all receiving labs use the same Sample IDs to associate files back to their original, physical samples. 

Guidelines for lab of origin (shipping lab):

1. Prior to shipping, assign a sample ID for each physical sample and complete the sample metadata spreadsheet provided below. Please fill out all required fields. If you have questions, please contact the C-CoMP Digital Coordinator.
2. In your shipping notification Slack message (preferred method for C-CoMP members) or email to receiving lab(s), please attach the completed sample metadata spreadsheet and provide receiving lab(s) with shipment tracking information. Please CC the C-CoMP Digital Coordinator on this message or email.

Guidelines for receiving lab(s)

1. Please check that the sample metadata spreadsheet is included in the email from the lab of origin. If the spreadsheet is not filled out, please remind the lab of origin to complete the spreadsheet. Do not run samples until the metadata has been shared. 
2. Please check that an internal C-CoMP Dataset number has been assigned for this dataset. If not, please follow these instructions to [obtain an internal C-CoMP Dataset number](broken://pages/98cmlcUsIyiEFf8NeN2z). 

## Sample Metadata Spreadsheet Template

{% file src="/files/5tLWMamB0DQQPiXagvdB" %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://c-comp.gitbook.io/data-management-handbook/sending-samples-to-other-labs.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.