Aglet

Triage a downloaded filename that differs from the document

A downloaded file name can change during selection, response construction, browser saving, or local normalization. Triage should capture the document identity, visible name, requested representation, suggested name, and final saved result. The goal is to separate a naming policy from a lost or misleading name.

Establish what is happening

  1. Capture names at each boundary

    Record the document title or display name, selected revision, requested format, response name hint, and final local filename. Preserve Unicode, spaces, punctuation, extension, and case because normalization can remove meaningful distinctions.

  2. Compare identity and format

    Verify that the saved file belongs to the selected document and that its extension matches the delivered representation. Note whether the visible name is a title, a storage key, or a user-facing filename with a separate policy.

  3. Classify the change

    Classify the case as expected sanitization, extension replacement, collision handling, encoding loss, wrong revision, or unclear naming rule. Record the name users need to recognize the document and the next action if it is ambiguous.

What to carry forward

Triage is complete when visible, requested, suggested, and saved names are compared for one document identity. If naming policy is intentionally different from display title, record the missing explanation separately from an actual wrong-file result.

Technical background: RFC Editor reference.

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