Skip to content
GearDock

Documentation

Content Completion

How missing product information is detected and, where evidence permits, filled.

Last updated

Completion has two halves: finding out what is missing, and filling only what available evidence can actually support.

Gap Detection

GearDock compares what is known about a product against what a product of that type would normally carry, and reports each attribute as supported, weakly supported, conflicting, or missing.

Supported
An attached source supports this value, and the passage is recorded.
Weakly supported
A value exists but the evidence is indirect, ambiguous, or low-confidence. Publishable only after a person looks.
Conflicting
Two sources disagree. GearDock does not pick a winner quietly. The conflict comes to you for a decision.
Missing
No available source addresses this attribute at all.

What Completion Will Not Do

Unsupported Gaps Stay Gaps

GearDock does not produce a plausible value for an attribute no source addresses. A blank field gets noticed and chased; a confident, unverifiable figure does not, and is the more damaging of the two.

This means a completed catalog will still contain visible gaps. That is the intended outcome: the catalog is complete in specific, known places rather than apparently complete everywhere.

Something here unclear or out of date? Tell us Documentation gaps are worth more to us than feature requests.