In-depth practical guides

Check identifiers in a documentary case

Separate format, check digit, assignment and matching when linking authors, publications and versions.

Updated :

Document verification desk with a ledger and company file.

AI-generated illustration

Does a well-formed identifier describe the right object?

An identifier needs its namespace and referent. ORCID identifies a person, ISSN a continuing resource, ISBN a publication edition and format; a DOI can identify different objects. An arithmetic check catches some copying errors, not identity.

  1. Preserve text

    Keep leading zeros, punctuation and the observed URL. Separate original and normalised values; avoid spreadsheet numeric conversion.

  2. Declare the type

    Check the namespace first. Do not merge local article identifiers, DOIs, PubMed records and author identifiers.

  3. Check transcription

    ORCID uses MOD 11-2, ISSN modulus 11, ISBN-13 weighted modulus 10. Check the result without automatically repairing the last character.

  4. Check assignment

    Open the reference registry or record and compare title, author, edition and version. Link distinct objects rather than removing different identifiers.

Reading workshop

Four records, no automatic merge

This fictional exercise separates namespace, received string and described object. DEMO identifiers are not assigned by any real registry.

Fictional data and records for learning: none of these results comes from a live service query.

Same string, different record

One catalogue provides linked print and digital editions. Another catalogue reuses the same local string. The decision must retain missing evidence rather than invent equivalence.

If the table exceeds the screen, scroll horizontally; arrow keys work when the region is focused.

Same string, different record
Fictional recordDeclared objectWhat is establishedDecision
DEMO-A:000042Print edition of the DEMO manualString retained with leading zerosKeep this record.
DEMO-B:000042Record from catalogue BA different namespaceCorrespondence with A is not established.
DEMO-A:42Another received recordNo rule links 42 and 000042Do not normalize to a number.
DEMO-A:000043Digital edition of the DEMO manualDocumented relation to the print editionLink formats without merging records.

Which decision respects the evidence?

Open each proposition to compare its diagnosis. More checks may still be needed.

Merge A:000042 and B:000042

No: equal strings across namespaces are insufficient. Request a documented mapping.

Replace A:000042 with A:42

No: no producer rule justifies removing zeros. Retain both received values.

Link A:000043 and A:000042 as two formats

Yes in this fictional case because the relation is supplied. This does not establish a single object to deduplicate.

Fictional matching record

Origin: DEMO-A and DEMO-B catalogues
Received: A:000042; B:000042; A:42; A:000043
Supplied relation: A:000043 = digital format linked to A:000042
A/B correspondence: not established
Numeric normalization: not applied

Keep original strings in the record. A relation between editions differs from record identity.

Documentation of the rules, separate from fictional examples

Compare other situations and exercises

Correct check, wrong edition

In a fictional case, two coherent ISBN-13s describe two book formats. A shared title does not establish removable duplicates.

One name, several authors

An illustrative list links one surname to two ORCIDs. Syntax cannot decide identity; read documented publications and affiliations.

Guided reading of an excerpt

The same local value does not merge two records

These fictional identifiers are local to the named catalogues. None is presented as a DOI, ORCID or identifier assigned by a real registry.

Fictional exercise: identifiers, values and dates illustrate the check. This excerpt is not a live collected response.

  1. Name the namespace

    catalogue-A and catalogue-B may assign the same string to different objects.

  2. Retain leading zeros

    Keep 000042 as text. Numeric conversion would destroy part of the received form.

  3. Check correspondence

    Compare object, title, version and the producer’s identification rule before linking records.

Three fictional local identifiers

catalogue-A | notice | "000042"
catalogue-B | notice | "000042"
catalogue-A | notice | "42"

What to inspect

A:000042 and B:000042
Equal values do not establish identity across catalogues.
A:000042 and A:42
Equivalence depends on a documented rule, not automatic conversion.
Can all these identifiers be replaced by the number 42?

Reasoning

No. That erases namespace and original form and creates an unjustified merge. Retain the received value and separately document any validated correspondence.

Official references : W3C — Data on the Web Best Practices

Worked exercise

An identifier resolves to the right title, wrong item

Fictional example: the values and documents teach the method and do not describe a real organisation.

The citation gives DOC-A but uses a table from DOC-B. Both identifiers resolve; compare the actual objects retrieved.

If the table exceeds the screen, scroll horizontally; arrow keys work when the region is focused.

Starting information
IdentifierTitleAppendix with the table used
DOC-ASame titleAbsent
DOC-BSame titlePresent

Your checks

  1. Resolve each ID and read its version.
  2. Check the cited table is present.
  3. Match citation to the document actually used.
Read the answer

Answer and decision

Successful resolution and matching titles are insufficient. The citation combines different objects. Cite DOC-B if that is what was consulted, or remove the table absent from DOC-A. Preserve editions rather than merging records.

If the case changes

Document a published version relation if available; it does not make contents interchangeable.

Record to retain

Keep ID, edition, file, table location and known relation.

Documentation reference : W3C — PROV Model Primer, derivation and revision · Consulted on

Record to retain

  • Original identifier, type and normalisation
  • Registry or record consulted
  • Matched object and version
  • Check result and matching decision

Official references

Related source profiles

Related protocols

Checks before reaching a conclusion

  • Is the namespace explicit?
  • Are leading zeros retained?
  • Does the registry describe the object?
  • Are different versions linked?

A documented match separating correct transcription from verified identity.

Frequently asked questions

Does a correct check digit certify registration?

No. It checks arithmetic. Use the appropriate registry or record to verify assignment and correspondence.

Can trailing DOI punctuation be removed?

Not automatically: characters may belong to the suffix. Compare the source and resolver; retain the original before editing.

Is it necessary to normalize the identification before the search?

Keep the form received first. A transformation can facilitate research if its rules are known, but it must be documented and not remove a significant character from the system concerned.

TOOLS / REGISTERS

Information to record

Open the reference registry or record and compare title, author, edition and version. Link distinct objects rather than removing different identifiers.

  • Access date and time zone
  • Exact URL
  • Entity identifier
  • Document identifier
  • Document type
  • Expected key and uniqueness
  • Version / revision
  • Observed status
  • Method / definition
  • Limit / uncertainty
  • Decision / next action
  • Review owner
  • Next review

DOCUMENTED REFERENCE

ARK: keep the object, authority and view reference

The Gallica address ark:/12148/bpt6k83037p/f143 has distinct components. ARK is a persistent identifier system. The domain provides access while the assigning authority and assigned name identify an object within its namespace.

ark:/12148bpt6k83037pf143
ARK: keep the object, authority and view reference
ReferenceValue or formWhat it identifies
ark:/ARKARK label in the form used by this Gallica example.
12148NAANName Assigning Authority Number, or NAAN; neither a date nor a page number.
bpt6k83037pNameAssigned document name in that namespace; the string alone does not reveal title or year.
f143QualifierReference to a particular view in this Gallica path; a whole-document citation and a passage citation differ in precision.

Implication for the record

Keep full ARK, actual destination, title, edition or version and consultation date. Persistence relies on identifier management; it does not certify immutable content. An ARK is not a file’s cryptographic hash.

Can version be omitted when the link stays stable?

No. Identifier stability and content stability are separate questions. Record version and consulted passage. For file comparison, also preserve a hash and observation date rather than treating the identifier as proof of binary identity.

Primary documentation

Documentation consulted on .

DOCUMENTED REFERENCE

ST.3: country, office and international publication

The two letters on an intellectual property document do not always identify a country. WIPO Standard ST.3 also covers organisations. These entries were checked against the August 2026 revision and must be read in their field context.

ST.3: country, office and international publication
ReferenceValue or formWhat it identifies
ST.32026-08This is the revision date consulted, not the file date. Older archives may use historical codes documented in the annexes.
FR / GBFR / GBFR refers to France and GB to the United Kingdom. In a priority field, these letters describe the recorded priority, not the applicant’s nationality.
EPEPOEP identifies the European Patent Office. Do not expand this prefix as a country code or infer identical protection throughout Europe.
EMEUIPOEM identifies EUIPO for EU marks and designs and relevant designations in international systems. It is not interchangeable with EP or EU.
WO / IBWIPOWO is used notably for PCT international publication; IB identifies the International Bureau in the capacities specified by the standard. Publication and receiving office are different information.

Implication for the record

Keep the code, field name, complete number and documentary system together. A prefix alone establishes neither grant, current ownership nor the countries where a right remains in force.

Is a WO publication a granted worldwide patent?

No. The code identifies the international publication context. Follow a PCT file through its national or regional phases and their events in the competent registers.

Primary documentation

Documentation consulted on .

DOCUMENTED REFERENCE

ISBN: distinguish edition identity from checksum validity

An ISBN identifies a publishing product: a particular title, edition and format, not every manifestation of a work. The local check follows International ISBN Agency arithmetic to detect transcription errors. It does not query allocation records or identify a book.

9789295055124ISBN-13 · 978-92-95055-12-4
ISBN: distinguish edition identity from checksum validity
ReferenceValue or formWhat it identifies
ISBN-1313New ISBNs have thirteen digits since 1 January 2007. Historical ten-character ISBNs use different arithmetic.
Prefix978 / 979The agency currently lists prefixes 978 and 979. An EAN checksum with another prefix is insufficient for ISBN-13.
Elements5Five elements: prefix, registration group, registrant, publication and check digit. Variable lengths rule out fixed-position publisher extraction.
Weights1, 3, 1, 3…Weights alternate 1 and 3 from the left across the first twelve digits.
Check digit(10 − (sum mod 10)) mod 10The check digit makes the complete weighted sum divisible by ten. A divisible partial sum requires zero, not ten.
Example978-92-95055-12-4The seventh international manual bears this ISBN, also cited in its official Slovene translation. It is the local documentary example.
ScopeTitle · edition · formatDifferent languages, editions or product forms may need distinct ISBNs. Different ISBNs do not establish distinct intellectual works.

Check an ISBN-13 or ISSN checksum

Enter all digits, with or without spaces and hyphens. X is allowed only at the end of an ISSN. Arabic and Persian digits are accepted. No network request.

Documented example: ISBN of the seventh international manual. Weighted sum of first twelve digits: 126; check digit: 4.

Removing spaces and hyphens is only for arithmetic. ISBN group boundaries and allocation are not checked. ISBN-10 and ORCID use different rules and are not handled here. A checksum does not detect every error, including some digit transpositions.

Implication for the record

Preserve leading zeros and original text. This check does not use allocation ranges to validate group boundaries or publisher existence. Correct length and checksum do not establish assignment; check title, language, date and format in a catalogue.

Does a correct checksum prove a book exists?

No. It establishes limited mathematical consistency. Allocation, bibliographic description and availability require a separate catalogue or publisher source; author identity is not confirmed either.

Primary documentation

Documentation consulted on .

DOCUMENTED REFERENCE

UUID: read the version without certifying an identity

A UUID contains 128 bits. In the RFC 9562 variant, four bits indicate its version. The table reproduces published examples from Appendices A and B.1, not identifiers assigned here to companies or documents.

017F22E279B07CC310₂rand_b48 + 4 + 12 + 2 + 62 = 1280x017F22E279B0 = 1645557742000 ms
UUID: read the version without certifying an identity
ReferenceValue or formWhat it identifies
UUIDv1C232AB00-9414-11EC-B3C8-9F6BDECED846Time-based version with Gregorian timestamp, sequence and node; the node field does not prove a machine’s hardware address.
UUIDv35df41881-3aed-3515-88a7-2f4a814cf09eDeterministic namespace-and-name computation using MD5, not an object signature.
UUIDv4919108f7-52d1-4320-9bac-f847db4148a8Random or pseudorandom version with 122 bits outside version and variant. Quality depends on the generator.
UUIDv52ed6657d-e927-568b-95e1-2665a8aea6a2Namespace-and-name computation using SHA-1; stable results also require identical name bytes.
UUIDv61EC9414C-232A-6B00-B3C8-9F6BDECED846Rearranges version 1 timestamp fields for ordering. It is not version 7’s Unix timestamp.
UUIDv7017F22E2-79B0-7CC3-98C4-DC0C0C07398FThe first 48 bits encode Unix milliseconds. This example contains 1645557742000, or 2022-02-22T19:22:22.000Z.
UUIDv82489E9AD-2EE2-8E00-8EC9-32D5F69181C0Custom layouts. Example B.1 does not define a universal time layout for every version 8 UUID.

Read UUID fields

Local reading of hexadecimal 8-4-4-4-12 notation. Any timestamp is encoded by the producer, not proof of creation. Selector examples come from RFC 9562.

Field reading updated.

Version
7
Variant
RFC 9562 variant · 10₂
Encoded UTC time
2022-02-22T19:22:22.000Z

Implication for the record

Correct syntax proves neither effective uniqueness, authenticity nor the associated object’s creation time. The reader decodes time only for version 7 with the RFC variant; Nil and Max are handled separately. It generates no identifiers or documents.

Primary documentation

Documentation consulted on .

DOCUMENTED REFERENCE

ORCID: check the digit without assigning an identity

An ORCID retains leading zeros and encodes neither country, institution nor discipline. Its last position checks transcription. The examples below are published by ORCID; they are not identities that a reader may claim.

0000-0002-1825-0097MOD 11-2 · (12 − (1314 mod 11)) mod 11 = 7
ORCID: check the digit without assigning an identity
ReferenceValue or formWhat it identifies
body15 × 0–9The first fifteen digits feed MOD 11-2 in order. Hyphens separate four groups of four characters and do not enter the calculation.
MOD 11-2t ← (t + d) × 2Start at zero, then double the sum of the current total and each digit. The check value is (12 − (total modulo 11)) modulo 11.
X10 · 0000-0002-1694-233XThe value 10 is written as a final X. The official example ending in 233X tests this case without replacing X with a numeral.
URIhttps://orcid.org/0000-0002-1825-0097The full HTTPS URI with hyphens retains registry context. Preserve zeros on import and avoid a numeric spreadsheet column.
scopearithmetic ≠ registry ≠ authenticationA consistent calculation proves neither assignment by ORCID, control of the account nor the source of an affiliation. Consult the record, then distinguish manual entry from an authenticated connection.

Read the arithmetic check · ORCID

Short code or HTTPS URL on the exact orcid.org domain, without query or fragment. 16 characters, in four groups or without hyphens. Final x is accepted and converted to X; only ordinary outer spaces, tabs and line breaks are removed.

Format and arithmetic check are consistent. Assignment and identity not checked.

Normalised form · existence not checked
https://orcid.org/0000-0002-1825-0097
Entered check value
7
Calculated check value for the body
7
Calculation remainder
5 (mod 11)
Calculation detail
MOD 11-2
t = 1314
1314 mod 11 = 5
(12 − 5) mod 11 = 7

Local calculation: no registry request. The source’s published example remains readable without JavaScript.

Implication for the record

This reader does not query the registry or verify allocation blocks. It does not create an ORCID or automatically correct a wrong check digit. People sharing a name must not be matched solely on the arithmetic consistency of a code.

Primary documentation

Documentation consulted on .

DOCUMENTED REFERENCE

ROR: decode the checksum without inferring an organisation

A ROR identifier is a random string with no information about the institution or its relationships. Its preferred form is a full URL. The documentation uses 02mhbdp94 as an example; this reader exposes the conversion before checking the digits.

02mhbdp94base32 → 88649142 → 98 − (8864914200 mod 97) = 94
ROR: decode the checksum without inferring an organisation
ReferenceValue or formWhat it identifies
pattern0 + 6 × base32 + 2 × 0–9The short form has nine characters: an initial zero, six Crockford base32 characters and two check digits. The initial zero remains in the URL.
alphabet0123456789abcdefghjkmnpqrstvwxyzThe alphabet includes 0–9 and the letters shown, excluding i, l, o and u. Do not map these excluded letters to similar-looking digits on import.
2mhbdp88649142Decoding 2mhbdp in base32 for the official example gives the integer 88,649,142. That integer reveals no name, country or institutional ranking.
check98 − ((n × 100) mod 97) = 94The generator published by ROR calculates 98 − ((n × 100) modulo 97), as two digits. Here the remainder is 4 and the check pair is 94.
recordhttps://ror.org/02mhbdp94Code consistency comes before reading the record: check names, name types, status and documented relationships. Do not predict a subsidiary’s ROR by modifying its parent’s.

Read the arithmetic check · ROR

Short code or HTTPS URL on the exact ror.org domain, without query or fragment. Nine characters; ASCII case converted to lowercase with no substitution for i, l, o, u. Only ordinary outer spaces, tabs and line breaks are removed.

Format and arithmetic check are consistent. Assignment and identity not checked.

Normalised form · existence not checked
https://ror.org/02mhbdp94
Entered check value
94
Calculated check value for the body
94
Calculation remainder
4 (mod 97)
Calculation detail
base32(2mhbdp) = 88649142
8864914200 mod 97 = 4
98 − 4 = 94

Local calculation: no registry request. The source’s published example remains readable without JavaScript.

Implication for the record

The tool runs locally and does not check presence in ROR. It rejects excluded letters and internal separators rather than silently repairing them. A normalised URL represents the entered code, not confirmation of existence or affiliation.

Primary documentation

Documentation consulted on .

DOCUMENTED REFERENCE

LEI: separate format, modulo-97 remainder and digit warning

A LEI may contain twenty characters yet fail the transcription check. The XBRL taxonomy also distinguishes an arithmetic error from a warning about certain endings. The example uses the LEI displayed by GLEIF for the foundation itself without inferring its current status.

506700GE1G29325QX363A = 10 … Z = 35 · 5067001614116293252633363 mod 97 = 1
LEI: separate format, modulo-97 remainder and digit warning
ReferenceValue or formWhat it identifies
pattern18 × A–Z / 0–9 + 2 × 0–9XBRL’s format check expects eighteen A–Z or 0–9 characters followed by two digits. This step does not query the registry.
A → Z10 → 35For arithmetic checking, replace A with 10, B with 11 through Z with 35, then concatenate digits without moving the LEI characters.
checkexpanded(full LEI) mod 97 = 1The expanded decimal number for the complete code must leave remainder 1 modulo 97. Calculate digit by digit without storing this large integer in a floating-point number.
body + 0098 − (expanded(body) × 100 mod 97)For the eighteen-character body, append 00 after conversion, then calculate 98 minus the modulo-97 remainder. This is a calculated pair for comparison, not permission to change a published LEI.
warning00 / 01 / 99XBRL flags 00, 01 and 99 separately: some issued LEIs use these endings due to a historical ambiguity. If the remainder is 1, the tool warns and requests registry verification without declaring them nonexistent.

Read the arithmetic check · LEI

20 characters without separators; ASCII case converted to uppercase. Last two characters must be digits. Only ordinary outer spaces, tabs and line breaks are removed.

Format and arithmetic check are consistent. Assignment and identity not checked.

Normalised form · existence not checked
506700GE1G29325QX363
Entered check value
63
Calculated check value for the body
63
Calculation remainder
1 (mod 97)
Calculation detail
A = 10 … Z = 35
5067001614116293252633363 mod 97 = 1
98 − (5067001614116293252633300 mod 97) = 63

Local calculation: no registry request. The source’s published example remains readable without JavaScript.

Implication for the record

Even remainder 1 proves neither assignment, current registration validity nor entity activity. Check the GLEIF record and date the lookup. This reader does not check other allocation rules and does not require positions 5–6 to be 00.

Primary documentation

Documentation consulted on .

DEEPER READING / PRACTICE

Check that an identifier matches its document

A file collects report numbers, DOI, opinion references and other identifiers. The control must find the right object and distinguish valid identifier and accurate correspondence.

Updated on .

Priority checks

Preserve the original form, identify the system used and examine the resolution result. Compare title, organization, date and version with the expected document.

Interpretation pitfalls

A small mistake can lead to another real object. Normalizing an identifier without knowing its rules can also remove a significant character.

Working record to retain

The register retains the original, form of search, document found and concordance. Unresolved identifiers remain visible for subsequent verification.