A useful metadata correction identifies one record, the field that is wrong and evidence for the proposed value. It does not require a broad rewrite of the catalogue. Keeping the request specific makes it easier to verify and less likely to merge unrelated works.
Start by distinguishing a source error from a local presentation choice. A translated title, custom sort value or stale image can look wrong for different reasons. The correction should address the layer that actually differs from the intended information.
Identify the record unambiguously
Include the work type and supported provider identifier where available, alongside the visible title. For a series episode, give its show and season context. For a channel, preserve the regional or language edition. A general poster and short name may identify several records.
Then name the field. “Wrong metadata” is less actionable than “this episode is matched to the similarly named remake” or “the current record uses a general series poster where a season image is expected.” Explain the difference without copying long copyrighted descriptions.
Prepare the correction
Do not attach the entire account export merely because it contains the affected entry. A maintainer often needs only the relevant harmless identifiers and field values initially. Private endpoints, passwords and unrelated viewing history should stay out of a public report.
- Record the current visible value and the exact item identity.
- Identify the proposed value through a reliable source.
- State whether the problem appears in source data or only in the local display.
- Include a short non-secret example or focused screenshot if it clarifies the mismatch.
- Keep the original record recoverable until the corrected result is verified.
Verify the accepted change
After a correction or refresh, inspect the same record and field. A changed poster does not prove a work-identity mismatch was fixed. Likewise, a corrected title may leave an old guide mapping or progress relationship attached to another record.
If the source lacks enough evidence for the proposed value, state the uncertainty. A correction request can be a question rather than a confident replacement. Avoid inventing release years, edition labels or ownership claims to make the record look complete.
Keep a brief private note of the request and outcome when the change affects local organization. That can explain why an override exists and prevent it from being reapplied after the source is fixed. Good corrections improve identification and discovery while preserving accurate relationships, rather than simply making every field look polished.
Useful answers
What should a correction request identify first?
The exact record and the specific field that is wrong.
Does a changed poster prove the work match is correct?
No. Check the underlying identity and relevant details.
Should uncertain replacement metadata be presented as fact?
No. State the uncertainty and ask a focused question.