Cobaltmetrics can only be queried by identifiers. Cobaltmetrics stores identifiers as URIs, so every search term should consist of a scheme, a colon, and a value.
For example, to search for RFC 3986, enter
All URLs are URIs, so you can also enter
https URLs into the search bar, and we'll do our best to extract identifiers from them, for example
https://tools.ietf.org/html/rfc3986 instead of
Our API will automatically normalize identifiers based on their type, for example if they are not sensitive to case like DOIs, or if their canonical form includes hyphens like ISSNs or ORCID iDs. Likewise, our API will reject syntactically incorrect identifiers.
See our page on URI schemes for the complete list of schemes that are currently supported in Cobaltmetrics.
By default, Cobaltmetrics will search for the identifiers you entered and, through a process known as URI transmutation, all other identifiers known to identify the same document or digital object. For example, we know from PubMed that
doi:10.1093/NAR/GKS1195 refer to the same article. URI transmutation allows you to find all citations and backlinks to a document with multiple identifiers, with a single query.
See our page on URI transmutation for more details.
Our team has a strong background in natural language processing and hands-on experience with bibliometrics. We know how ambiguous natural language can be, especially named entities like the names of persons and organizations. We decided early on to focus on speed and accuracy, so searching by names will most likely never be supported. And if you are one of the 47,000 people in the US named John Smith, please register for an ORCID identifier.