> 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/redivis-for-open-science/citations.md).

# Provenance and citation

## Provenance and research linkages

Redivis automatically creates and updates links among research artifacts as researchers work. When datasets or other workflows are added to a workflow or project, or an existing analysis is forked, these relationships are recorded in that item's provenance. Contributor information is also updated as researchers collaborate on the work.

Researchers can supplement these automatically generated records with related outputs created outside Redivis. Research articles, data management plans, and other resources can be added to the provenance section of a dataset, workflow, or project using a DOI or URL. This helps keep data, methods, and resulting research outputs connected throughout the research lifecycle.

## Citing Redivis

Publications and other outputs should cite Redivis as research software, using the appropriate conventions for your publication medium.

* The Digital Object Identifier (DOI) for Redivis is: [https://doi.org/10.71778/V2DW-7A53](https://doi.org/10.71778/v2dw-7a53)
* The canonical URL for Redivis is: [https://redivis.com](https://redivis.com/)

If referencing Redivis inline, the abbreviated citation can be used:

> Redivis \[<https://doi.org/10.71778/V2DW-7A53>]

The following BibTeX entry can be used:

```
@misc{https://doi.org/10.71778/V2DW-7A53,
  doi = {10.71778/V2DW-7A53},
  url = {https://redivis.com},
  author = {Redivis},
  keywords = {FOS: Software},
  language = {en},
  title = {Redivis},
  publisher = {Redivis},
  year = {2025}
}
```

These identifiers are also associated with Redivis, though do not need to be included in all citations:

* Re3data identifier: <https://www.re3data.org/repository/r3d100014398>
* RRID: [RRID:SCR\_023111](https://scicrunch.org/resolver/RRID:SCR_023111)

## Citing datasets

It's important to make sure that you fully cite any datasets used in your work. Each dataset page includes citation information in the provenance section in multiple format options.

For example the [Global Historical Climatology Network dataset](https://redivis.com/datasets/mg94-6t8b2j4pk) hosted by the Stanford Center for Population Health Sciences would be cited in the APA format as:

> Stanford Center for Population Health Sciences. (2022). GHCN Daily Weather Data (Version 1.2) \[Data set]. Redivis. <https://doi.org/10.57761/h9ff-vy04>

<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%2FWogYMOBnmGiq1toeWKuW%2FScreenshot%202025-01-23%20at%2012.30.37%E2%80%AFPM_out.png?alt=media&amp;token=fd9865c7-7c92-4108-a486-7e620a1f1c85" alt=""><figcaption></figcaption></figure></div>

## Citing workflows

Workflows across Redivis also include citation information in the provenance section in multiple format options.

<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%2F4S30O2XT1jupYjiHTas7%2FScreenshot%202026-06-23%20at%2011.38.39%E2%80%AFPM.png?alt=media&amp;token=49751d5d-7cab-4c3b-a77f-a29887a574bb" alt=""><figcaption></figcaption></figure></div>

## Citing projects

Like datasets and workflows, projects include citation information in the provenance section in multiple format options.

<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%2F0QwIcdRMvBPF6B4NodMM%2Fredivis.com_projects_hgy3-2zw1x6tab.png?alt=media&amp;token=c630c3a4-b828-4f35-81e7-0e8596e9ba90" alt=""><figcaption></figcaption></figure></div>

## Bibliography

Datasets, workflows, and projects on Redivis can be supplemented with **related identifiers** that situate a resource in its broader context. You can view the bibliography for a dataset or workflow from the corresponding provenance section.

<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%2FGwVEyJ4YrFSgiDfHUqEQ%2FScreenshot%202025-01-23%20at%2012.32.24%E2%80%AFPM_out.png?alt=media&amp;token=b57a667c-6a8f-4a3a-bcf4-93c833e03947" 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/redivis-for-open-science/citations.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.