# DataCite DOI Monitor - Research Datasets & Metadata Changes

Find dataset DOIs through DataCite and track version, rights and metadata changes. Export stable DOI identities and source links for dataset discovery and provenance reviews.

Canonical product page: https://mayd-it.com/data-tools/actors/datacite-dataset-doi-monitor/

## Example input

```json
{
  "queries": [
    "machine learning"
  ],
  "maxResults": 5,
  "itemsPerQuery": 3
}
```

## Full guide

# DataCite DOI Monitor - Research Datasets & Metadata Changes

<img src="https://apify-image-uploads-prod.s3.us-east-1.amazonaws.com/r4RVqhPKWACJsK9zp-actor-eUqYAdPw8Wi2kg9ff-uWcWdROmVm-datacite.png" alt="DataCite DOI Monitor - Research Datasets & Metadata Changes icon" width="96" height="96">

**Monitor dataset DOI records and version or rights metadata changes with provenance.**

DataCite DOI Monitor with saved field comparisons, source URLs and CSV/JSON exports. Simple inputs, bounded results and readable reports. No source API key.

## Start in under a minute

1. Paste dataset searches into the first input field, or use the included sample.
2. Keep the five-result limit for your first run and choose **Start**.
3. Open **Observations**, **Scope and diagnostics**, or the **Readable run report** in Output. Export CSV or JSON from the dataset.

```json
{
  "queries": [
    "machine learning"
  ],
  "maxResults": 5,
  "itemsPerQuery": 3
}
```

No source account, API key, paid proxy or extra subscription is required for these public endpoints. Source availability and rate limits still apply.

## Who this helps

Data teams discovering citable research datasets.

<!-- B18-REAL-SAMPLE -->
## A real output sample

Captured in a successful bounded Apify run; arrays and long text are shortened for readability. Values are snapshots, not live guarantees.

```json
{
  "recordId": "10.21227/a0we-0f36",
  "title": "\"V2X-PAD: A Physical-Aware Spatio-Temporal Dataset for V2X Misbehavior Detection\"",
  "doi": "10.21227/a0we-0f36",
  "creators": [
    "Lasseni Coulibaly"
  ],
  "publisher": "IEEE DataPort",
  "publicationYear": 2026,
  "resourceType": "Dataset",
  "version": null,
  "rights": [
    {
      "name": "Creative Commons Attribution 4.0 International",
      "uri": "https://creativecommons.org/licenses/by/4.0/legalcode"
    }
  ],
  "url": "https://doi.org/10.21227/a0we-0f36",
  "observedAt": "2026-10-18T03:55:52.611Z",
  "comparisonStatus": "not_requested"
}
```

## What you receive

One row per unique confirmed observation. Every row includes a stable `recordId`, title, source URL and observation time.

| Field | Meaning |
|---|---|
| `doi` | Source-reported doi; missing optional values remain null. |
| `creators` | Source-reported creators; missing optional values remain null. |
| `publisher` | Source-reported publisher; missing optional values remain null. |
| `publicationYear` | Source-reported publication year; missing optional values remain null. |
| `resourceType` | Source-reported resource type; missing optional values remain null. |
| `version` | Source-reported version; missing optional values remain null. |
| `rights` | Source-reported rights; missing optional values remain null. |
| `comparisonStatus` | not_requested, new, changed or unchanged |
| `changedFields` | Fields different from your last saved observation |
| `previous` | Previous saved source values when comparison is enabled |

## Saved comparisons

Enable **Compare with saved observations**, choose a snapshot name, and reuse the same input scope. The first run establishes history; it cannot report changes before that point. Enable **Save only new or changed observations** for later runs if you want a change-only export. An unchanged run can correctly save zero rows.

Only confirmed saved rows advance history. A bounded or failed run never establishes that a missing record was deleted. History is stored in a named key-value store in the running user's account. Use one writer per snapshot: do not overlap runs against the same snapshot. Change the snapshot name when starting a new independent workflow.

## Scope and limitations

Public DataCite search restricted to Dataset records, one page. DOI records are depositor metadata, not proof of data quality or access rights. Does not fetch files.

At most ten input values and five hundred saved rows per run. Results requested per query controls a single source page (1–50, default five); there is no pagination. Each input performs one bounded public source request; NuGet also resolves its service index once per run. Requests are paced. Responses are capped at 8 MiB and share the run deadline. No authentication bypass or code execution is performed. HTTP 429 stops further requests. Source failures appear in SUMMARY and the HTML report, never as paid data rows.

## Pricing

The configured base price is **$0.001 per saved observation**, plus **$0.00005 per start** at the default memory. Five observations cost $0.00505 at that base rate. Applicable plan discounts and the Store pricing panel govern actual charges. Set a maximum charge in Run options. Diagnostics, reports and unchanged skipped rows are not dataset result events.

## A practical workflow

Data teams discovering citable research datasets. Monitor dataset DOI records and version or rights metadata changes with provenance. Start with the included five-result sample, review source links, then save your own scope as an Actor task. Use a named snapshot for repeat runs and keep source metadata with downstream exports.

## Make it recurring

Save an Actor task with your inputs, then attach an Apify Schedule. For change detection, keep the same snapshot and avoid overlapping runs. Add an integration to deliver results to your own spreadsheet or workflow. No external delivery is enabled automatically.

## Frequently asked questions

**Why did a repeat run return zero rows?** With change-only mode enabled, unchanged records are skipped. Check SUMMARY to distinguish this from empty matches, limits, or an upstream error.

**Does a missing record mean it was deleted?** No. Searches cover a bounded source window; a record can move outside it. Missing records never become deletion claims.

**Can I export or integrate the data?** Yes. Use Apify dataset exports for CSV/JSON, or the Actor API and your own integrations. No external message or delivery is enabled by default.

## Examples

1. **Dataset searches: machine learning** — A bounded machine learning observation sample. Review source evidence and export rows or compare them in a later run.
2. **Dataset searches: robotics** — A bounded robotics observation sample. Review source evidence and export rows or compare them in a later run.
3. **Dataset searches: climate** — A bounded climate observation sample. Review source evidence and export rows or compare them in a later run.

## Source and support

[Official source documentation](https://support.datacite.org/docs/api). This independent Mayd IT tool is not affiliated with the source platform. Open an Actor issue with the run ID and expected result, or contact bmay@mayd-it.com. Never include credentials.
