Aglet

Triage a missing document derivative after processing

A source can upload successfully while its preview, extracted text, converted file, or other derivative is missing. Triage should name the promised output and bind it to the source revision, then compare processing evidence with visible availability. The aim is to separate missing work from missing attachment.

Establish what is happening

  1. Name the expected output

    Record source document identity, revision, derivative type, format, and where the output should appear. Capture the status and controls shown to the reader, including whether another derivative is available.

  2. Trace availability evidence

    Check processing completion, derivative record or reference, output length or metadata, storage result, and page state. Distinguish a derivative that was never produced from one that exists but is not linked or displayed.

  3. Classify the gap

    Classify the case as processing failure, missing association, wrong revision, unsupported output, delayed availability, or unclear promise. State the user action blocked and preserve the source and derivative identities for investigation.

What to carry forward

Triage is complete when the source revision, promised derivative, processing evidence, and visible availability are compared. If the output promise is unclear, record that contract gap instead of treating an optional representation as missing work.

Technical background: W3C guidance.

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