A local rename can make a shortcut easier for a household to recognize. It should not change what the source actually represents. Keep the friendly label separate from guide keys, provider identifiers and private resource addresses wherever the application supports that distinction.

Before editing, identify whether the name is a local preference or part of a maintained catalogue. A change made directly in a snapshot can be replaced by the next source refresh. A supported local label may have a different persistence rule.

Hawaii is not a Pacific Time shortcut. — IPTV USA editorial illustration

Choose a label that helps without misleading

“Evening News” may be convenient for a favourite, but the actual channel edition should remain available for support. A film nickname can be memorable while still being too ambiguous to identify the work outside the household. Preserve the original name in a suitable field or private note.

Avoid adding unsupported claims to a label. Calling an entry “4K,” “all episodes” or “official” does not establish those facts. A local convenience name should describe the choice accurately rather than turn preference into a promise.

Rename the right layer

Do not rename a guide identifier to match the new friendly label unless a verified mapping correction requires it. A key can look less readable while remaining the correct relationship value. Cosmetic consistency is not a reason to break that link.

  1. Identify the exact entry and the field controlling its visible local label.
  2. Check the application’s documented rename and refresh behaviour.
  3. Preserve the original identity and any important edition qualifier.
  4. Change only the display preference, leaving keys and access data intact.
  5. Reopen the entry and confirm that the intended source and guide still match.

Plan for shared use and migration

Other household members may rely on familiar names. Explain a significant local reorganization and avoid giving several different sources the same vague nickname. Clear labels should reduce accidental selection rather than conceal meaningful regional or language differences.

During export, check whether the local rename survives. A destination may restore the source’s original label or omit the preference entirely. That is not necessarily loss of the underlying programme; it can be a difference in which fields were transferred.

For support, provide the original identity alongside the local label and describe the actual issue. A maintainer cannot reliably investigate “the good sports one” without knowing the source entry. Keeping personal naming separate from factual identity allows useful customization while preserving a clear route to updates, corrections and recovery.

Useful answers

Should a local rename change a guide key?

No. Keep display preferences separate from matching identifiers.

Will every rename survive a source refresh?

No. Check where the edit is stored and how the player updates data.

What name should support receive?

Give the original identity and relevant edition along with any local nickname.

Keep exploring

Deduplicating a catalogue without losing editionsReading mixed-direction programme titlesA programme-guide entry does not guarantee replayBrowse every articleQuestions and answers