DataCite metadata establishes the identifier record and its declared relationships, while the repository landing page confirms the exact downloadable object and version you used; check both, because they answer different questions. The DOI itself resolves through the Handle System to current information supplied for the identified object, commonly a landing page maintained by the registrant, so resolution takes you to the repository's current description rather than freezing a version.
What DataCite metadata establishes
The DataCite REST API exposes DOI metadata and supports queries and filters for works, repositories, providers, clients, and related entities. Use it to capture the registered identifier, the repository or provider behind it, and the related-entity links recorded for that DOI. This is the route that establishes identifier metadata: which DOI exists, who registered it, and what relationships the record declares.
What the landing page confirms
Open the resolved landing page and compare its version field, file listing, and release notes against the DataCite record. The landing page is where you confirm the exact downloadable object: the file name, the version label, and the release notes describing what changed. Record the file you downloaded and the version shown at download time.
A practical sequence
- Query the DataCite REST API for the dataset DOI and note the repository, provider, and related entities. Result: the identifier record you will compare against.
- Resolve the DOI and open the landing page it points to. Result: the registrant's current description of the object.
- Compare the version field and release notes on the landing page with the DataCite record. Result: agreement confirms the version; a mismatch leaves the version unresolved.
- Download the file and record its name and the version label shown. Result: the exact object used in the model is documented.
- If the version remains unresolved, check whether another repository copy exists; CORE aggregates open-access research outputs and offers discovery services and tools for finding repository copies of scholarly work. Result: either a matching copy or a documented gap.
A mismatch between the two records does not by itself show which version is correct. Treat the version as unresolved and verify against the file you actually downloaded before citing it in the model documentation.
