# Identifier resolution FAIRsharing has created a number of [FAIR metrics](/fairsharing/about-our-records/fair-assistance/fair-metrics-co-creation.md) for a variety of communities and use cases. This page outlines how tests implementing these metrics should behave with regards to identifier resolution. ## URIs and resolvable identifiers If the metric states clearly that the identifier must be resolvable (often by stating that it must be a URI), then do not pass eg the 'canonical' form of the identifier, but rather the URI form. {% hint style="info" %} If the metric requires a resolvable identifier, then ensure you are passing a URI of some type. For example, pass instead of `10.25504/FAIRsharing.2abjs5` {% endhint %} ### Metadata harvesting and resolution When any identifier is resolved, FAIRsharing uses the [FAIR Champion Harvester](https://github.com/markwilkinson/FAIR-Champion-Harvester) library to retrieve metadata in a way consistent with FAIR Champion and OSTrails. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://fairsharing.gitbook.io/fairsharing/about-our-records/fair-assistance/identifier-resolution.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.