---
name: 'Feature Request'
about: 'This is a feature request issue'
labels: 'type:feature, status:incoming'
---

<!-- Provide a general summary of your changes in the Title above. -->
<!-- You can erase any parts of this template not applicable to your Issue. -->
<!-- Show that you have done a step, by checking the checkboxes. -->

Thank you for your contribution!

It's great, that you want contribute to pyDataverse.

First, start by reading the [Bug reports, enhancement requests and other issues](https://pydataverse.readthedocs.io/en/master/contributing/contributing.html) section.

### Before we can start

Before moving on, please check some things first:

* [ ] Your issue may already be reported! Please search on the [issue tracker](https://github.com/gdcc/pyDataverse/issues) before creating one.
* [ ] Is this something you can **debug and fix**? Send a pull request! For more information, see the [Contributor Guide](https://pydataverse.readthedocs.io/en/master/contributing/contributing.html).
* [ ] We as maintainers foster an open and welcoming environment. Be respectfull, supportive and nice to each other! :)

### Prerequisites

* [ ] Are you running the latest version?

### Feature Request

We will consider your request but it may be closed if it's something we're not actively planning to work on.

**Please note: By far the quickest way to get a new feature is to file a [Pull Request](https://github.com/gdcc/pyDataverse/pulls).**
