Duplicate Category Names? Identify Whether They Are Truly the Same
Repeated category labels are compared by source, media type, membership, filters, language, profile, device, count, and time before being called duplicates.
In short: Do not classify two same-name categories as duplicates from their labels alone. Record each category's source scope, media type, parent view, language, displayed count, representative members, account, profile, filters, grouping, device, application version, and timestamp. Open both independently, compare a small item sample, and preserve source labels. Avoid renaming, merging, hiding, or deleting anything before the scopes are understood and support evidence is saved.
Labels are presentation evidence, not unique identifiers. Two categories called “Drama” can belong to different authorized sources, media types, languages, or views while remaining meaningfully distinct.
Capture each category context
Record the exact label, screen, parent section, media type, enabled sources, and order for category A and category B. Note punctuation, spacing, capitalization, and translated wording, but do not assume a visual difference determines identity.
The category and metadata handbook provides the layer matrix.
Freeze account and view controls
Use the same Norva account, profile, availability, year, rating, audio, subtitles, search, sorting, and grouping. Record every value. A category that appears twice under different filters or parent views is not a clean duplicate test.
Compare source scope
Where the interface shows it, record which authorized source or sources contribute to each category. Through each provider's official route, note whether same-name categories exist. Do not infer how Norva combines or preserves source labels internally.
Compare media type and language
Determine whether one category contains films, series, episodes, or another visible type while the other contains a different type. Record interface language and source-language cues. Similar translated labels can originate from distinct source names.
The localized-title guide offers a language comparison pattern that also applies to labels.
Compare representative membership
Choose up to three privacy-safe samples from each category and one overlapping item if present. Record source, year, media type, version, and category placement. Categories with different members are not necessarily duplicates even when counts happen to match.
Also note whether selecting each label opens a distinct route, breadcrumb, source marker, or parent section where the interface exposes one. These ordinary navigation cues can distinguish scopes without claiming they are internal identifiers. If the routes look identical, record that observation rather than treating it as proof of duplication.
Interpret counts carefully
Record displayed counts at close timestamps with identical controls. A count can change with source membership, filters, or grouping. The cross-device category-count guide explains why totals require full context.
Check another supported device
Use the same account, profile, sources, filters, grouping, and close observation time. Record both application versions. If one device shows one label and another shows two, preserve that cross-screen evidence without claiming a local storage cause.
Preserve the timeline
Record when both categories were first observed, recent imports or refreshes, source changes, application updates, and every rename or filter action. If the duplicate-looking labels appeared after an event, note the sequence without claiming causation.
Avoid premature cleanup
Do not rename source categories, hide one view, merge categories, remove a source, or repeat imports before saving the comparison. A label change can make later evidence harder to align and may affect legitimate source organization.
Classify the pair
Use same label with different source, different media type, different parent view, different language origin, overlapping membership, matching sampled membership, device-specific duplicate display, appeared after a documented event, or unknown. “True duplicate” should remain a narrow observation, not an inferred database state.
Original evidence: same-label category comparison
| Field | Category A | Category B |
|---|---|---|
| Exact label and parent view | ||
| Source scope | ||
| Media type and language | ||
| Displayed count | ||
| Three member samples | ||
| Filters and grouping | ||
| Device, version, time | ||
| Classification |
Common mistakes and limitations
- Treating label text as a unique identifier.
- Comparing different parent views or filters.
- Ignoring source, media type, and language scope.
- Assuming equal counts mean equal membership.
- Renaming or hiding a category before saving evidence.
- Exporting complete category membership.
Frequently asked questions
Are same-name categories always duplicates?
No. Compare source, media type, parent view, language, membership, and context before classifying them.
Should I rename one source category?
Not as the first diagnostic action. Preserve the original labels and confirm ownership and support guidance.
What if their sampled members also match?
Record the overlap and broader context. A small sample still cannot prove complete membership or internal identity.