> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dataerai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Import from DataONE

> Search DataONE's federation of environmental- and earth-science repositories and import records into a project as metadata-first assets — without copying the bytes into Dataerai. Downloads stream straight from DataONE.

Dataerai can pull public records from [DataONE](https://www.dataone.org) into one of your projects as **metadata-first assets**. DataONE is the Data Observation Network for Earth — a federation of around 60 environmental- and earth-science repositories (KNB, PANGAEA, the LTER network, and more) searchable through a single index. The record's metadata — title, type, authors, abstract, publication date, and DOI where present — is copied into Dataerai so it's searchable and shareable alongside your own data. The **file is not copied**: clicking **Download** on an imported asset streams directly from DataONE.

<Note>
  Imported assets are [metadata-first](/data/metadata-first-assets): they describe and link to data that lives on DataONE. Nothing is stored in your Dataerai allocation, so importing doesn't consume your quota.
</Note>

## Search DataONE

Open the **Import from DataONE** page and enter a query, then **Search**.

* The query uses DataONE's own search syntax. Enter a plain keyword (`water quality`, `salmon`) or a fielded clause (`title:soil`, `abstract:salmon`).
* Results are biased toward **science-metadata records** — the datasets that carry a title, author, and abstract — so you see describable datasets rather than raw data files.
* Results show **Title**, **Type**, and **Files**, with the record identifier and publication date under each title.
* Use **Per page** (25, 100, 500, or 1000) to trade clicks for latency. Result counts and page totals come straight from DataONE's index, so paging is exact.

<Note>
  Each DataONE record imports as a **single asset** with one linked file. DataONE's unit of identity is a persistent identifier (PID) — which may be a DOI (`doi:10.6073/pasta/…`), a URN, a UUID, or a repository-specific id like `knb.11.1` — and each PID names exactly one object.
</Note>

## Select and import

<Steps>
  <Step title="Select records">
    Tick the records you want — click a row, or press Space or Enter on it, to toggle its checkbox. The header checkbox selects or clears everything on the current page; your selection is kept as you page through results.
  </Step>

  <Step title="Choose the destination project">
    Paste the UUID of the project that should own the new assets into the **Import into project** field.
  </Step>

  <Step title="Import">
    Click **Import**. Large selections are sent in batches automatically, and a single **Import result** panel summarizes how many records were imported (and how many new assets were created), plus any that failed and why.
  </Step>
</Steps>

<Warning>
  Because imported assets point at DataONE rather than your own storage, their files are only available while the DataONE record is. If you need a durable copy under your control, download the file and [upload it](/data/upload) as a regular asset instead.
</Warning>

## Next steps

<CardGroup cols={2}>
  <Card title="Metadata-first assets" icon="file-plus" href="/data/metadata-first-assets">
    How records that describe data elsewhere work in Dataerai.
  </Card>

  <Card title="Organize into collections" icon="folder-tree" href="/organize/collections">
    Group imported records alongside your own data.
  </Card>

  <Card title="Search & discover" icon="search" href="/discover/search">
    Find imported records by title, type, creator, and metadata.
  </Card>

  <Card title="Sharing & permissions" icon="share-2" href="/sharing/permissions">
    Decide who can see the records you import.
  </Card>
</CardGroup>