> For the complete documentation index, see [llms.txt](https://docs.redivis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.redivis.com/reference/organizations/settings/advanced-doi-configuration.md).

# Advanced: DOI configuration

Digital Object Identifiers (DOIs) support data citation and reproducibility. Redivis can issue DOIs for an organization's datasets through an institutional membership in [DataCite](https://datacite.org) or [EZID](https://ezid.cdlib.org/). The organization's DOI configuration determines which account Redivis uses to issue them.

The [DOI lifecycle for datasets](https://docs.redivis.com/reference/datasets/overview.md) describes how DOIs are issued and updated for each dataset version.

The **DOI provider** section of an organization's **Advanced** settings shows the configuration that applies to the organization.

<div data-with-frame="true"><figure><img src="https://1672950126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LVodLwUXgJUGcm5Cvso%2Fuploads%2Ff2Ld0aPHg6GPNKvnLIF2%2Fredivis-staging.com_Demo_admin_datasets%20(30).png?alt=media&amp;token=4c1b4bf6-ff93-42ff-8b82-316eb60c8fd1" alt=""><figcaption></figcaption></figure></div>

## Configuration

An organization administrator can set the DOI configuration to one of three options.

#### None

Redivis does not issue DOIs for the organization's datasets.

#### Custom

Redivis issues DOIs through the organization's own DataCite or EZID account. A custom configuration requires the following fields:

* **Provider:** The registration agency, which is DataCite or EZID.
* **Repository account ID:** The account ID, or username, registered with the provider.
* **Repository account password:** The password for the account. Redivis does not display a saved password. When editing the configuration, an empty password keeps the saved one, unless the provider changes.
* **DOI prefix:** The prefix assigned to the repository, such as `10.82053`.

#### Inherit from institution

Redivis issues DOIs through the DOI configuration of the organization's [institution](https://docs.redivis.com/reference/institutions.md). Organization administrators can see the institution's provider and DOI prefix, but not its credentials. If the institution has not configured a provider, Redivis does not issue DOIs until it does. This option is available only to organizations within an institution.

An organization within an institution that has not set its own DOI configuration inherits the institution's. To opt out of the institution's configuration, an organization administrator can choose **None** or **Custom**.

The **DOI provider** modal shows the selected option and its settings.

<div data-with-frame="true"><figure><img src="https://1672950126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LVodLwUXgJUGcm5Cvso%2Fuploads%2FAxblCK5ibL8pussKxJkx%2Fredivis-staging.com_Demo_admin_datasets%20(31).png?alt=media&amp;token=916d0522-2be4-4d0a-9cf5-d841bdb1241d" alt=""><figcaption></figcaption></figure></div>

## Default DOI behavior

With a custom or inherited configuration, the **Default all future datasets to issue DOIs** setting determines whether new datasets issue DOIs by default. It does not change existing datasets, and each dataset's settings can override it.

## Back-issuing DOIs

When an organization administrator saves a configuration that can issue DOIs, Redivis asks whether to issue DOIs for the organization's existing datasets. A configuration can issue DOIs when it is custom, or when it is inherited from an institution that has configured a provider.

If the administrator selects **Issue DOIs for existing datasets**, Redivis turns on DOI issuance for every existing dataset and issues a DOI for each of its released versions. Like other DOIs on Redivis, these DOIs become permanent after 7 days.

To back-issue DOIs for datasets individually, leave the option unselected and turn on DOI issuance in each dataset's settings.

<div data-with-frame="true"><figure><img src="https://1672950126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LVodLwUXgJUGcm5Cvso%2Fuploads%2FcJ11Ss8AA4xiqC4xf93V%2Fapp.gitbook.com_o_-LAzxbDPgjEGJfV0tvZu_s_-LVodLwUXgJUGcm5Cvso_~_edit_~_changes_540_reference_organizations_settings_advanced-doi-configuration.png?alt=media&amp;token=febdf26f-9aa4-45de-a14a-c878286549e0" alt=""><figcaption></figcaption></figure></div>


---

# 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://docs.redivis.com/reference/organizations/settings/advanced-doi-configuration.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.
