The same channel label can describe different regional or language feeds. A name-only deduplication pass can therefore remove a real choice. Before treating two records as redundant, compare the identity information that distinguishes what a viewer will actually receive.
A shared logo is not sufficient proof of equivalence either. Broadcasters commonly use recognizable branding across several editions. The catalogue should preserve useful differences even when the artwork and short display names look alike.
Look for the distinction behind the name
A fictional “Harbor News” entry could represent an eastern schedule, a western schedule or a different language service. If the catalogue omits those qualifiers, the naming may need improvement. That is different from proving that the underlying sources are duplicates.
Guide associations provide another clue, but not a complete verdict. Different schedules can indicate different editions; identical guide keys can also be a mapping error. Use a combination of source-maintainer information, edition metadata and a specific programme comparison before deciding what to merge.
Review a same-name pair
Avoid naming an entry after an assumed resolution merely because one address ends differently. File paths and labels are not decoded-picture measurements. A useful qualifier should reflect a supported distinction, not a guess made to differentiate two rows.
- Record both entries without changing either source address.
- Compare region, language, edition and documented guide association.
- Ask whether the catalogue maintainer identifies them as separate feeds.
- If appropriate, add a supported local display qualifier rather than deleting an entry.
- Check that each surviving label still opens the intended source.
Keep cleanup reversible
A local hide option can be useful when a household wants a shorter list but the identities remain uncertain. That expresses a navigation preference without claiming the hidden entry is redundant. Keep the original catalogue available so a later correction can restore it.
When switching players, compare how each application handles duplicate display names. One might preserve both records while another groups or sorts them in an unexpected way. An import that appears to lose a channel may actually have changed the visible arrangement. Search by a known distinguishing field where the application supports it.
A good correction report explains which qualifier is missing and supplies a non-secret example. “Two different regional editions both display as Harbor News” is a clearer problem than “duplicates in the list.” The goal is to make each choice identifiable. A small accurate set of labels is more useful than a reduced count obtained by erasing meaningful editions.
Useful answers
Can two entries with the same name be different feeds?
Yes. Regional, language and schedule editions can share a short label.
Does an identical logo justify merging entries?
No. Branding can be shared across distinct feeds.
Is hiding an unwanted entry the same as proving duplication?
No. Hiding is a local navigation choice; identity still needs evidence.