Skip to content

Main content

Reference DOI Prefix Case Normalization Tool

Normalize an ASCII-whitespace-free DOI spelling and optional resolver prefix; no DOI existence or publisher authority is checked.

Loading tool…

Description

Normalize a restricted DOI token.

Bibliographic records connect authors, versions, publication dates and locators through explicit identifiers. Literal comparisons and counts help reconcile those records but do not retrieve publications, authenticate sources or establish the quality or meaning of a citation.

Normalize a restricted DOI token.

When to use this tool

Use Reference DOI Prefix Case Normalization when checking the stated bibliographic record, locator, date or counting convention.

How to use the tool and how it works

  1. Enter identifier. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read normalized, removedResolver. Inspect removedResolver before interpreting the associated values.

Normalize a restricted DOI token. Remove a leading DOI resolver URL or doi: prefix, require a 10-dot numeric registrant/slash nonwhitespace suffix pattern, lowercase the result; removedResolver tests an original HTTP(S) prefix.1

DOI identifiers have case-insensitive naming conventions. This helper applies full string lowercasing and a restricted syntax check; it does not implement complete identifier equivalence or resolution.2

Input fieldMeaning and unitsAccepted input
identifierIdentifierRequired. Text; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
normalizedFull-Unicode lowercase stripped DOI-like token; no complete DOI-equivalence validation, registration lookup or percent decoding.Required. Text; maximum UTF-16 length 8192.
removedResolverRemoved ResolverRequired. Boolean.
json
{
  "input": {
    "identifier": "https://doi.org/10.1234/ABC"
  },
  "output": {
    "normalized": "10.1234/abc",
    "removedResolver": true
  }
}

Limitations and assumptions

  • No surrounding whitespace trim, percent decoding or DOI resolution occurs; syntax acceptance does not establish registration or source authenticity.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.

Alternative or Complementary methods

Inspect the original publications and authoritative metadata, and use complete identifier-aware reference management for scholarly attribution and evidence appraisal.

References

  1. Calculation and input contract: bibliometrics/reference-doi-prefix-case-normalization — tool.io

  2. Constructing your identifiers — Crossref

Similar or alternative tools