Aglet

Prioritize an Import Mapping Correction

Prioritizing mapping work means choosing whether to stop new misrouting, repair historical imports, clarify a source format, or document an intentional transformation. Rank by downstream consequence and continuing exposure, then separate deterministic field swaps from ambiguous meaning. Preserve the evidence behind each queue choice.

Decide where the work belongs

  1. Rank destination consequence

    For each mapped field, list reports, joins, decisions, exports, and workflows that consume it. Record the concrete effect of a swap, default, or coercion and the affected run count. A less frequent identifier error may outrank a common descriptive-field mismatch.

  2. Assess forward exposure

    Check whether new imports use the same header, mapping revision, or source template. Classify the work as immediate mapping correction, source clarification, bounded historical repair, or contract documentation. Prioritize forward protection when every new run repeats the same misrouting.

  3. Choose queue action

    Select investigate, pause a named import path for review, correct the mapping, reconcile a bounded history, or monitor. Include source format, destination field, owner, comparison fixture, and escalation trigger. Do not broaden scope to every import when one header or revision explains the evidence.

What to carry forward

Return a ranked mapping queue with consequence, affected runs, recurrence, repair confidence, owner, and next action. The leading item should say whether forward imports or historical rows come first. Mark priority provisional when source meaning, header stability, or destination use is unclear.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow