# Manage datasets

## Create a new dataset

All datasets on Redivis are owned by either an individual user or an [organization](https://docs.redivis.com/reference/organizations).&#x20;

To create a dataset owned by you, navigate to [your workspace](https://docs.redivis.com/reference/your-account/workspace), and under **Datasets**, click the **+ New dataset** button. To create a dataset owned by an organization that you administer, navigate to the organization's [administrator panel](https://docs.redivis.com/reference/organizations/administrator-panel), and under **Datasets**, and click the **+ New dataset** button.

For step-by-step guides for creating and editing datasets, see the accompanying [Create & manage datasets guide](https://docs.redivis.com/guides/create-and-manage-datasets).

## Edit a dataset

To edit a dataset, navigate to your workspace (or organization administrator panel), and click on the dataset that you would like to edit. You will also see an **Edit dataset** link at the top of the page for all datasets that you are an editor of.

From within the dataset editor, you will be able to update data, metadata, and release a new version of the dataset.

On the **Overview** tab, you can populate the [various metadata fields](#overview) of the dataset. Note that any fields that you leave blank will not be shown to users on the dataset's page.

On the **Table** and **Files** tabs, you can [upload](https://docs.redivis.com/reference/datasets/create-and-edit-datasets/import-sources) the various data contents associated with the dataset.

#### Assigning editors

If a dataset is owned by a user, that user has full ability to edit and modify the dataset. If a dataset is owned by an organization, all administrators of the organization will have such rights.

You can also add other editors to the dataset by selecting **Configure access** at the top right of the dataset, and adding the specific individuals as editors. Editors will be able to upload data, modify metadata, and release new versions of the dataset, but they cannot modify any of the dataset's access rules or change the dataset's published status.

Dataset editors will be able to find this dataset in their [workspace](https://docs.redivis.com/reference/your-account/workspace) on the Datasets tab.

## Configure access

A big part of editing a dataset is managing who has access to it. See more about [configuring access](https://docs.redivis.com/reference/data-access/configuring-access) to datasets.

## Upload data

Getting data into Redivis is the first and most important step in making it accessible for your research community. Redivis is designed to make it easy for you to securely ingest data, at scale.&#x20;

Redivis supports a wide variety of data types, sources, and upload methodologies. When beginning to upload data, you should first ask:

**What type of data is it?**&#x20;

* [Tabular data](https://docs.redivis.com/reference/datasets/create-and-edit-datasets/import-tabular-data)
* [Geospatial data](https://docs.redivis.com/reference/datasets/create-and-edit-datasets/import-geospatial-data)
* [Unstructured data](https://docs.redivis.com/reference/datasets/create-and-edit-datasets/import-files)

**Where is the data?**

* A computer
* [Another table on Redivis](https://docs.redivis.com/reference/datasets/import-sources#redivis)
* [An external source](https://docs.redivis.com/reference/datasets/create-and-edit-datasets/import-sources) (Box, Drive, GCS, S3, etc.)

**How do I want to perform the upload?**

* Through the browser
* [Programmatically, via Python or R](https://docs.redivis.com/reference/datasets/create-and-edit-datasets/using-the-api)

{% hint style="info" %}
For a guided walkthrough on uploading data please see the [Creating a dataset](https://docs.redivis.com/guides/create-and-manage-datasets/create-and-populate-a-dataset) guide and the [Cleaning tabular data](https://docs.redivis.com/guides/create-and-manage-datasets/cleaning-tabular-data) guide.
{% endhint %}

## Publish a dataset

When a dataset is first created it will be marked as **unreleased**. You will be able to specify certain [access rules](https://docs.redivis.com/reference/data-access) for the dataset, however, these access rules will only take effect once the dataset is published, and can be modified before the dataset's publication.&#x20;

As you work on the initial [version](https://docs.redivis.com/reference/datasets/versions) of the dataset you can see the changes you make to the data in the version history modal. in this unreleased state you can add it to a workflow and analyze the data it contains. Note that the only people who can see it in the workflow are dataset editors. If you make changes to the data or delete it, your workflow will change instantly to reflect those changes.&#x20;

{% hint style="info" %}
To add an unreleased or unpublished dataset to a workflow, click the **View dataset** tab from the edit interface, and click the **Analyze in workflow** button. Since this dataset is not published it will not appear in the **Add dataset** interface in workflows.
{% endhint %}

Once you are ready to make your data available to non-editors, you will need to publish it by clicking the **Publish** button in the top right. This will simultaneously release your version as well as make your dataset discoverable.&#x20;

Once published, and pursuant to the dataset's access configuration, all other users on Redivis will have one of the following access levels to the dataset: none, overview, metadata, sample, data.&#x20;

## Unpublish a dataset

Datasets owned by organizations can be unpublished at any time. This will "unlist" the dataset so that it will not be listed on your organization home page and even users who meet the access requirements will not be able to see it. Anywhere it is used in a workflow it will instantly be made unavailable.&#x20;

Unpublishing might be used if you need to temporarily halt usage of the dataset but don't want to disrupt all of the access rules. &#x20;

## Additional settings

On the dataset editor page, you will see an additional **Settings** tab that is not visible to the public, where various options for the dataset can be configured:

#### Dataset name

You can rename the dataset here (or by clicking on the dataset title within the dataset editor).

#### Administrator notes

These notes are only visible to editors of the dataset, and may provide helpful documentation for administrative processes around maintaining the dataset.

#### Featured status

\[Organization datasets only]. Whether the dataset should be featured on your organization's landing page.

## Transfer a dataset

On the dataset settings you have the option to transfer the dataset to a new owner.&#x20;

In order to make a transfer you'll need to have permissions to manage dataset. For a user-owned dataset this means being the owner or editor. For an organization-owned dataset this means being an administrator of the organization.&#x20;

You'll also need to transfer the dataset either to yourself or to an organization where you are an administrator.&#x20;

#### Access migration

Anytime you transfer a dataset that has an access restriction assigned to it Redivis will preserve your dataset's access configuration on transfer.&#x20;

* E.g. If you've [configured](https://docs.redivis.com/reference/data-access/configuring-access) the dataset's Metadata access (or any other [access level](https://docs.redivis.com/reference/data-access/access-levels)) to anything other than **Public** (such as **Direct access**, **All members**, or **Requirements)** it will have the same setting when transferred.&#x20;

However, you will need to specify who (if anyone) will continue to have their access approved at the corresponding level as before the transfer.

#### Remove all access

You can choose to end previously granted access for all users. Anyone who previously had gained access to the data through approved requirements or being granted access directly will need to reapply and be reapproved by the new owner or owning organization.&#x20;

With this setting the dataset will arrive to its new owner with no approved access other than for the new owner (or organization administrators).&#x20;

#### Preserve direct access

This option will preserve users' current access when the dataset is transferred.&#x20;

* If a user had been granted direct access at a given access level by the initial owner they will be automatically granted direct access at the corresponding level for the new owner.
* If a user had gained access through a requirement (organization-owned datasets only) they will automatically be granted direct access to the corresponding access level for the new owner.
* When transferring from one organization to another you will need to decide if you will preserve access only for users who are members of both organizations, or if you want to create memberships at the destination organization for all users who were not already members.&#x20;

#### Preserve access system (organizations only)

If a dataset with a permission group is being transferred from one organization to another you can choose to preserve the full access system as well as preserving users' current access.&#x20;

* This option will copy the dataset's permission group and all requirements in the permission group to the new owner organization.&#x20;
* If a permission group or requirement being copied over has an identical name to one in the destination organization, the transfer doesn’t succeed and an error is thrown. You will need to rename one or the other for this to succeed.&#x20;
* All approvals for these requirements will also be transferred in the same status (approved, revoked, etc).&#x20;
* You will need to decide if you will preserve access only for users who are members of both organizations, or if you want to create memberships at the destination organization for all users who were not already members.&#x20;
* If an export environment is assigned to the orginal owning organization's permission group, it will not be copied over to the new owner organization. However if one exists in the new owner organization it will be added to the dataset's permission group. No export approvals will be copied over.

{% hint style="info" %}
Any access or export configuration and approval can be edited by the new owner once the transfer is completed.&#x20;
{% endhint %}
