> For the complete documentation index, see [llms.txt](https://help.datamidsouth.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.datamidsouth.org/data-midsouth-portal/contribute-and-participate/request-or-suggest.md).

# Request or suggest

Need help or have a great idea? Here’s how to reach us.

We review every submission and prioritize based on community impact—thank you for helping us build a better Data Midsouth!

### How to submit feedback

{% stepper %}
{% step %}

### Go to Navigation Bar

This is the header at the top of the page.
{% endstep %}

{% step %}

### Select Requests/Ideas

<figure><img src="https://1095412806-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fe1ApIrdBTGqD08Mi8Gpp%2Fuploads%2FRKZR1m00H9YTkvjrPyzS%2Frequests.jpg?alt=media&amp;token=8747f86b-c70d-497d-995b-3293b1facd14" alt=""><figcaption></figcaption></figure>

Clicking this menu option will take you to an external website where we crowdsource feedback from the public.&#x20;
{% endstep %}

{% step %}

### Select **New Post**

Click New Post to add a new idea or suggestion.&#x20;

<figure><img src="https://1095412806-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fe1ApIrdBTGqD08Mi8Gpp%2Fuploads%2FpwoHZfEUvBvwIEiRjkJE%2FFeaturebase.png?alt=media&amp;token=00826cbe-312d-4b5c-9a74-b78745d58c22" alt="" width="563"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Select a board

<figure><img src="https://1095412806-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fe1ApIrdBTGqD08Mi8Gpp%2Fuploads%2F5wzSkVKAzcGhZU55ilT0%2Fimage.png?alt=media&amp;token=172a0237-ab5f-4c8b-bb1c-9d3bb0431a43" alt=""><figcaption></figcaption></figure>

[**Data**](https://feedback.datamidsouth.org/?b=681397f54c43fb809b7b71bb): Submit ideas for **new datasets** or new ways to interact with one.

[**Features**](http://feedback.datamidsouth.org/)**:** Request actions **you can perform** in a tool like Data Midsouth or the Memphis Property Hub.

[**Bugs**](https://feedback.datamidsouth.org/?b=68139867e57583f1f5451d95)**:** Report a bug or **technical issues**

[**Testimonials**](https://feedback.datamidsouth.org/?b=68139a3301772202f4f46b9b): **Share** how you use Data Midsouth in your work!&#x20;
{% endstep %}

{% step %}

### Upvote ideas using arrows

Click the arrows next to existing posts to upvote them.&#x20;
{% endstep %}
{% endstepper %}

### Contact Us

* **Custom Tools, Datasets, or Partnership Proposals**
  * Email Kira Morin directly at [**kmorin@innovatememphis.com**](mailto:kmorin@innovatememphis.com)
* **Support through Donation:**
  * Help us sustain and grow Data Midsouth by [donating to Innovate Memphis](https://innovatememphis.com/donate/)


---

# 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://help.datamidsouth.org/data-midsouth-portal/contribute-and-participate/request-or-suggest.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.
