> For the complete documentation index, see [llms.txt](https://das-metadata.gitbook.io/das-metadata-standard-by-das-rcn/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://das-metadata.gitbook.io/das-metadata-standard-by-das-rcn/contribute.md).

# Contribute

Here's how you can contribute to DAS-RCN's proposed DAS metadata reporting format:

* Want to make a change to the reporting format? Copy and paste one of the **issue templates** below and [submit a new issue](https://github.com/vhlai-seis/DAS_metadata/issues/new).
* Have a question? Contact us at voonhui.lai @ anu.edu.au ; rmellors @ ucsd.edu .

***

## Citation

These issue templates were modeled from that provided by Darwin Core:

Darwin Core maintenance group, Biodiversity Information Standards (TDWG) (2014). Darwin Core. Zenodo. <https://doi.org/10.5281/zenodo.592792>

***

## Issue templates

### New term

Copy and paste this template into your [new issue](https://github.com/DAS-RCN/DAS_metadata/issues/new) if you want to create a term that does not exist yet.

```
## New term

* Submitter:
* Justification (why is this term necessary?):

Proposed definition of the new term:

* Term name (in lowerCamelCase):
* Definition of the term:
* Format of the term: 
* Additional Instructions (recommendations regarding content, etc.):
* Examples: 
* Refines (name of the broader term this term refines, if applicable):
* Replaces (name of the existing term that would be replaced by this term, if applicable):
```

### Change term

Copy and paste this template into your [new issue](https://github.com/vhlai-seis/DAS_metadata/issues/new) if you want to make a change to a term.

```
## Change term

* Term to change:
* Submitter:
* Justification (why is this change necessary?):

I suggest the following changes (leave blank whatever would not change):

* Term name (in lowerCamelCase):
* Definition of the term:
* Format of the term: 
* Additional Instructions (recommendations regarding content, etc.):
* Examples: 
* Refines (name of the broader term this term refines, if applicable):
* Replaces (name of the existing term that would be replaced by this term, if applicable):
```

### Change documentation

Copy and paste this template into your [new issue](https://github.com/vhlai-seis/DAS_metadata/issues/new) if you want to make a change to the documentation.

```
## Change documentation

* Documentation reference (URL):
* Submitter:
* Justification (why is this change necessary?):

I suggest the following changes:
```

### Request new feature

Copy and paste this template into your [new issue](https://github.com/vhlai-seis/DAS_metadata/issues/new) if you want to request a new feature.

```
## Request new feature

* Short description of new feature:
* Submitter:

Feature request (reason, suggestion to implement):
```

### Report bug

Copy and paste this template into your [new issue](https://github.com/vhlai-seis/DAS_metadata/issues/new) if you want to report a bug.

```
## Report bug

* Short description of bug:
* Submitter:

Bug description (behavior and how to reproduce):
```


---

# 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://das-metadata.gitbook.io/das-metadata-standard-by-das-rcn/contribute.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.