DataCite verifies the metadata registered for a dataset DOI, while DOI resolution verifies the current destination the registrant supplies for that DOI, commonly a landing page. The two routes answer different questions, so compare their outputs field by field and record which route supports each fact in your source map.
What DataCite metadata can verify
The DataCite REST API exposes DOI metadata and supports queries and filters for works, repositories, providers, clients, and related entities. Use it to confirm that a DOI is registered and to read the descriptive fields attached to that registration, such as creator, repository, and related-entity information. Treat these as registered metadata: they describe what the registrant recorded, and the API output is the evidence for that record.
What DOI resolution can verify
A DOI name resolves through the Handle System to current information supplied for the identified object, commonly a landing page maintained by the registrant. Resolution therefore shows where the DOI currently points. Use it to confirm the present destination and to read what that destination states about the dataset.
Compare field by field
- Pull the DataCite record for the DOI and list its registered fields: creators, repository or client, and related entities. Expected result: a metadata profile of the registration.
- Resolve the DOI and open the destination it returns. Expected result: the current landing page or object location supplied by the registrant.
- Match each registered field against the corresponding statement at the destination. Expected result: a per-field note showing whether the two routes agree, and which route supplies the evidence for each fact.
- Mark any field that appears in only one route as verified by that route alone, and record the unresolved item with the next check you will run.
Reading the source map
A field present in DataCite metadata is supported by the registration record. A statement found at the resolved destination is supported by that destination. When the two disagree, describe what each route shows and keep the discrepancy open until you check the original source. ICMJE recommends verifying references against original sources and identifying retractions, so use the resolved landing page and the original dataset documentation to confirm facts that matter to a decision.
