> For the complete documentation index, see [llms.txt](https://help.researchgate.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.researchgate.net/research-and-publications/researchgate-dois.md).

# ResearchGate DOIs

#### Page contents

* [Generating a ResearchGate DOI for unpublished research](#generating-a-researchgate-doi-for-unpublished-research)
* [What kind of research can get a ResearchGate DOI?](#what-kind-of-research-can-get-a-researchgate-doi)
* [Why are DOIs helpful?](#why-are-dois-helpful)
* [How to generate a ResearchGate DOI for your research](#how-to-generate-a-researchgate-doi-for-your-research)
* [What if my research already has a DOI from another source?](#what-if-my-research-already-has-a-doi-from-another-source)

#### Generating a ResearchGate DOI for unpublished research

A Digital Object Identifier (DOI) is a unique, permanent link for your research, making it easy to find and cite.

**This article only applies if you want to generate a DOI for unpublished work — such as a thesis, preprint, or dataset — that doesn't already have one.**

**Important:** If your research has already been published (as a journal article, book, chapter, conference paper, patent, poster, etc.), it already has a DOI issued by the publisher. ResearchGate DOIs don't apply to it; see [What if my research already has a DOI from another source?](#what-if-my-research-already-has-a-doi-from-another-source) below.

#### What kind of research can get a ResearchGate DOI?

ResearchGate DOIs (with the format `10.13140/RG...`) are only for **unpublished** work with a public full-text, such as theses, preprints, and datasets.

You **cannot** generate a ResearchGate DOI for:

* Articles
* Books
* Chapters
* Patents
* Cover pages
* Posters
* Conference papers

These research types are typically published elsewhere and already have a DOI issued by their publisher.

#### Why are DOIs helpful?

* **Make your research citable:** DOIs provide a stable, unchanging link to your work online.
* **Date your discovery:** DOIs include the publishing date of your research, ensuring proper attribution.

You can quickly find any publication using its DOI in the search bar at the top of every ResearchGate page.

#### How to generate a ResearchGate DOI for your research

If your research type supports it and has a public full-text, follow these steps:

1. Go to your [Research tab](https://www.researchgate.net/go.Profile.contributions.html).
2. Click on the title of the research item you want to add a DOI to.
3. On the right-hand side, click the **More** button and select **Generate a DOI**.
   1. If **Generate a DOI** is not visible, this research item type does not support it.
4. Review the details of your research item to ensure they are correct.
5. Click **Generate a DOI**.

**Please note:** Once a ResearchGate DOI is generated, you cannot edit that research item. If you need to make changes, you must remove the research, re-upload the corrected version, and then generate a new DOI.

#### What if my research already has a DOI from another source?

You should not generate a new DOI for work that already has one. To add an existing publisher-issued DOI instead:

1. Go to your [Research tab](https://www.researchgate.net/go.Profile.contributions.html).
2. Scroll to the research item you want to add the DOI to.
3. Click the **More** button below the research item's title and select **Edit**.
4. Enter the DOI number in the DOI field.
5. Click **Save** to confirm your changes.

Researchers will then be able to cite your work using its existing DOI.


---

# 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.researchgate.net/research-and-publications/researchgate-dois.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.