A display name helps a person recognize a channel. An identifier helps software keep the right records connected. They may contain similar text, but they are not interchangeable. Renaming a visible label is therefore a different operation from changing the guide mapping attached to an entry.
This distinction matters after a rebrand, a local rename or a playlist refresh. A channel may acquire a more familiar title while its stable identifier stays the same. Conversely, two regional feeds can share a familiar brand name while requiring separate identities and schedules.
Give the label and the key different jobs
Imagine two fictional entries called City News East and City News West. Their names tell a viewer which edition to choose. Their identifiers might be city-news-east.example and city-news-west.example. If both entries are renamed simply City News, a person loses a useful distinction even if the underlying records remain separate.
The reverse mistake is changing an identifier only to make it look like the current display name. If programme data still refers to the old stable key, that cosmetic edit can break the join. A recognizable name is not evidence that a replacement key is correct.
Plan a local rename
Do not use a rename to conceal a regional or language difference. A short label that makes a remote easier to use can still retain a suffix such as East, French or Local when that distinction changes the programme being selected. The aim is better navigation, not a single brand name at any cost.
- Decide whether the problem is readability, sorting or an incorrect source association.
- Record the existing display label and identifier before editing.
- Change only the local label if the player documents that operation separately.
- Check that the selected feed and programme guide still correspond.
- Reopen the catalogue after a refresh to see whether the local preference persists.
Understand the importer’s matching rules
Some importers support explicit guide identifiers and may also recognize name-based metadata. Others offer manual mappings. Consult the actual application’s rules rather than assuming every player resolves names identically. An optional attribute being present in a file does not prove that the current importer uses it.
If the guide is empty after a rename, compare the mapping first. If the guide still belongs to the correct source but the order looks strange, investigate sorting instead. Those observations lead to different fixes and should not be grouped under “the channel name is wrong.”
A useful correction report includes the old label, intended label, relevant edition and a non-secret mapping example. Keep access URLs out of that report. A clean separation between display and identity makes later catalogue changes easier to handle, because a spelling correction no longer requires guessing which schedule or feed should replace it.
Useful answers
Can two feeds have the same displayed name?
Yes. Preserve their meaningful region, language or edition differences instead of assuming they are duplicates.
Should a guide ID be changed after every rebrand?
Not merely for appearance. Confirm the source mapping; a stable key may intentionally outlive a display name.
Why did a local rename not survive refresh?
The importer may rebuild labels from its source or store local preferences differently. Check the documented behaviour before repeating the edit.