Decide where the work belongs
Identify irreversible transformations
Compare source bytes with stored text for affected examples. Distinguish a display mismatch from a replacement character already written into a field. Record which names, identifiers, or searchable descriptions become unusable and whether downstream tools now receive the same damaged values.
Estimate the affected export population
Group attempts by producer, encoding choice, and language coverage where that information is available. Compare known affected files with successful imports from the same workflow. Avoid inferring that an unreported language works merely because current support examples cover only one locale or alphabet.
Assess warning and recovery quality
Try the preview warning and supported correction path with a controlled file. Determine whether users can select the right encoding before import. If the only recovery is a full re-export and reconciliation, include that effort and the risk of duplicate work in the priority decision.
What to carry forward
Record priority with the damaged fields, recovery limits, evidence for scope, and a named owner. Escalate if the importer silently saves replacement characters or damages identifiers. Revisit the decision when a new export producer or language exposes a different decoding path or weaker preview warning.
Technical background: PostgreSQL documentation.
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