Scan-to-Full-Record Link¶
Software tool — instantiates Boundary-Embedded Disclosure Design
A persistent identifier, QR code, resolver, or clickable link that takes a consumer from the compact disclosure to the maintained detailed records.
A Scan-to-Full-Record Link is the route, not the card: a persistent identifier — a QR code, a DOI, a resolver URL, a clickable reference — that carries no boundary payload of its own but reliably takes a consumer from the tiny disclosure they can see to the full, maintained record behind it. Its defining property is resolution stability: whatever else changes, following the link must still land on the current authoritative record. Where a label, badge, or manifest carries some boundary facts, this mechanism carries none; it exists so that the compact surface can stay compact while still being one deliberate action away from everything it cannot hold — validation reports, provenance trails, licenses, owners, and escalation channels.
Example¶
A research figure — a chart of measured values — is reused in a conference slide, stripped of its context. Printed beneath it is a DOI, a persistent identifier that resolves through the DOI system to the dataset's landing page even if the hosting server, filename, or institution changes over the years.[n1] A viewer who wants to know whether the figure applies to their case follows the identifier and arrives at the maintained record: the full dataset, the methods, the version history, the license, and a named contact. If the figure is being used outside its documented scope, that same landing page offers the escalation path — a "contact the data steward" route — so a questionable reuse becomes a query to the owner rather than a silent assumption. The link itself asserts nothing; it just guarantees the door still opens.
How it works¶
The mechanism assigns the artifact a stable, resolvable identifier and encodes it in a form the consumer can act on where they meet the artifact — scanning a code, clicking a reference, resolving an identifier. A layer of indirection (a resolver) sits between the printed identifier and the record's actual location, so the target can move without breaking the link. The route's job is threefold: get the reader to the current record, give them the action of going there, and, at the destination, offer the path to a human when the reader needs an exception or a judgment the record alone cannot supply.
Tuning parameters¶
- Identifier persistence — a raw URL versus an indirected persistent identifier. Indirection survives moves and reorganizations but requires a resolver someone must maintain.
- Encoding modality — printed QR/DataMatrix, embedded hyperlink, or typed identifier. Scannable codes suit physical objects; hyperlinks suit digital ones; each fails in the other's medium.
- Resolution target freshness — whether the link lands on a versioned snapshot or the always-current record. Current-record targets stay accurate but can surprise a reader expecting the version they started from.
- Escalation reachability — whether the destination exposes a live owner/contact path. A reachable steward turns edge cases into conversations but must be staffed to answer.
When it helps, and when it misleads¶
Its strength is that it lets the visible disclosure stay small without amputating the reader from the full evidence: one scan or click bridges the compact surface to the maintained record, and to a human when judgment is needed. A persistent-identifier scheme keeps that bridge intact across the years an artifact circulates.[1]
Its failure mode is link rot: a route that resolves to a dead page, an outdated snapshot, or a login wall recreates the very context-loss the disclosure was meant to prevent, and does so invisibly — the code still scans, it just leads nowhere useful. The classic misuse is printing a link to satisfy a checklist while nobody maintains the record it points to, so the door opens onto an empty room. The guarding discipline is to treat the target as a maintained asset — monitor resolution, use indirection so the destination can move without breaking the identifier, and keep the record on the other end current and reachable.
How it implements the components¶
deeper_record_link— this is the front door: the persistent, resolvable route from the compact disclosure to the full maintained record.reader_action_affordance— the scan or click is the reader's action to check deeper evidence before relying on the artifact.exception_or_override_path— the destination exposes the owner/steward and escalation channel for reuse the record alone cannot adjudicate.
The link is a door, not a card: it holds no attached_disclosure_surface, minimum_boundary_payload, or confidence_or_warning_signal of its own — those ride on the Artifact Boundary Label it is usually printed beside. It carries no machine_readable_field_set; the record it resolves to is the Provenance Header or Manifest (its nearest neighbor — the manifest *is the record, this link is only the route to it), and it defines no reuse_boundary_trigger (the Inline Boundary Panel).*
Related¶
- Instantiates: Boundary-Embedded Disclosure Design — the link is the route from the compact disclosure to the deeper record.
- Sibling mechanisms: API Reuse Boundary Header · Artifact Boundary Label · Dataset Datasheet or Data Card · Inline Boundary Panel · License and Use Badge · Provenance Header or Manifest
Editorial Notes¶
Form Classification¶
Form family: Interface, Display & Cue
Rationale: Scan-to-Full-Record Link operates as a user-facing prompt, display, template, or perceptual cue that shapes attention and action at the point of use because it a persistent identifier, QR code, resolver, or clickable link that takes a consumer from the compact disclosure to the maintained detailed records.
Independent corroboration: The frozen evidence defines Scan-to-Full-Record Link as 'A persistent identifier, QR code, resolver, or clickable link that takes a consumer from the compact disclosure to the maintained detailed records', so its operative form is Interface, Display & Cue.
Nearest alternative: Representation, Specification & Plan — Scan-to-Full-Record Link includes features of a static representation, map, specification, schema, or prospective plan that externalizes information, but its defining operation is a user-facing prompt, display, template, or perceptual cue that shapes attention and action at the point of use.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Library & Information Science
Origin pattern: Convergent development
Present-day reach: Multi-domain
Rationale: Persistent identifiers linking compact descriptions to maintained records are information-management mechanisms.
Related originating lineages:
- Computer Science & Software Engineering — Computer science and software-engineering practice supplies a parallel or contributing lineage for the mechanism's defining operation: a persistent identifier, QR code, resolver, or clickable link that takes a consumer from the compact disclosure to the maintained detailed records.
Review resolution: Both blind reviewers agree that library_information_science is the primary historical origin. Explicit reconciliation of origin_mode_disagreement, encyclopedia_synthesis_disagreement starts from reviewer_a's mechanism-specific evidence: Persistent identifiers linking compact descriptions to maintained records are information-management mechanisms. Reviewer A proposed alternates=computer_science, origin_mode=convergent, domain_reach=multi_domain, and encyclopedia_synthesis=false; reviewer B proposed alternates=computer_science, origin_mode=single_lineage, domain_reach=multi_domain, and encyclopedia_synthesis=true. The final record retains every independently supported alternate from either review (computer_science) without an arbitrary cap, selects origin_mode=convergent to represent the combined lineage evidence, and records domain_reach=multi_domain and encyclopedia_synthesis=true. Present-day transfer is recorded as reach and is not treated as proof of historical origin.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
This link is the connective tissue several siblings depend on: the Artifact Boundary Label, Inline Boundary Panel, Dataset Datasheet or Data Card, and License and Use Badge each embed one so their compact surfaces can point to the full record. Because so much rides on it, its persistence is a shared dependency, not a detail — when the link rots, every disclosure that consumes it silently loses its deeper record.
[n1] A Digital Object Identifier (DOI) is a persistent identifier resolved through a central handle system, so a reference keeps resolving to the current location of a record even as hosting, URLs, or custodians change. Persistent identifiers are the standard defense against link rot for scholarly and data records. ↩
References¶
[1] International Organization for Standardization. Information and Documentation—Digital Object Identifier System. ISO 26324:2022, 2nd ed. (2022). Defines DOI as a persistent, resolvable identifier that maintains object identity over time. registry ↩