The Complete Guide to Curating Media Favorites
An eight-stage favorites loop turns every saved item into a deliberate retrieval promise with identity, owner, review trigger, and exit rule.
In short: A useful favorite promises a future action: return, compare, recommend, rewatch, or monitor. Give it exact media identity, a viewer or household scope, one stated reason, a retrieval route, and an exit or review trigger. Keep temporary tonight choices, active next-up items, and long-term favorites in separate workflows.
Favorites stop helping when the list becomes an undifferentiated record of every momentary interest. Curation does not mean keeping only a few prestigious titles. It means every saved item has a purpose and remains findable when that purpose returns.
Use the eight-stage curation loop
| Stage | Pass question |
|---|---|
| 1. Intent | What future action should this save enable? |
| 2. Identity | Which exact work, series, episode, or version is it? |
| 3. Owner | Whose preference is this? |
| 4. Admission | Does it belong in long-term favorites? |
| 5. Retrieval | Can it be found again from at least one tested route? |
| 6. Use | Did the favorite support the intended action? |
| 7. Exception | What if it duplicates, moves, or becomes unavailable? |
| 8. Review | When should it be kept, moved, or removed? |
An item that cannot pass the intent or identity gate should not enter the list yet.
Stage 1: state the intent
Write one verb: revisit, follow, compare, recommend, sample later, or preserve as a reference. “Looks interesting” can be a temporary shortlist reason, but it is weak long-term intent.
Use the favorites admission decision when the reason is unclear.
Stage 2: identify the entity
Record title, media type, release context, series and episode hierarchy when relevant, and version attributes. DCMI metadata terms distinguish identifiers, titles, types, relations, formats, and languages. That separation matters when duplicate-looking cards represent distinct works or variants.
Favorite the entity that matches the future action. A series-level follow intent should not accidentally save only the episode that was open.
Stage 3: establish owner and scope
A favorite is preference data. Identify the viewer, confirmed profile, or deliberately shared household list. Do not assume profile isolation from an avatar alone. Test the actual scope with a harmless item and keep a private external note when separation cannot be verified.
Stage 4: choose the right destination
Use:
- Long-term favorites for durable preference or retrieval.
- Next-up for an intended near-term viewing action.
- Tonight shortlist for a temporary group decision.
- Themed shortlist for a bounded purpose or occasion.
- History/progress for what happened, not what is preferred.
The long-term-versus-next-up guide prevents one list from carrying incompatible intents.
Stage 5: test retrieval
Save the item, leave its detail page, and find it again. Confirm what opens, which version is selected, and whether the scope survives on another supported device if that matters. W3C label guidance supports controls that expose purpose and state; a heart icon should have a clear saved or not-saved label.
Norva may retain favorites under the same account across supported devices, alongside other account state. Exact scope and synchronization should be verified in the current build and support documentation.
Stage 6: measure use
The list succeeds when it shortens a real decision. Track a small outcome:
- retrieved and watched;
- retrieved and recommended;
- compared with another version;
- moved to next-up;
- no longer relevant.
Do not use raw list size as the main success metric.
Stage 7: handle exceptions without losing identity
When an item becomes unavailable, preserve identity and determine whether the purpose remains. When two cards look alike, compare work and version fields before removing either. When an item appears missing, test filters, scope, source, and sync before adding a duplicate.
Use the unavailable-favorite workflow for current source changes.
Stage 8: schedule review
A quarterly review is practical for long-term lists, while temporary lists need a much earlier expiry. At review, keep, move, merge, archive externally, or remove. Record the reason only where it will inform the next decision.
Common mistakes and limitations
- Saving without a future action.
- Mixing tonight choices with durable favorites.
- Favoriting the wrong entity or version.
- Assuming profile and device scope.
- Removing unavailable items before preserving identity.
- Measuring success by list growth.
Frequently asked questions
How many favorites should someone keep?
There is no universal number. Keep the list small enough that each item remains retrievable and reviewable for its intended purpose.
Must watched titles leave favorites?
No. Completion and preference are separate. Apply the stated future action and review trigger.
Is a watchlist the same as favorites?
Not necessarily. Define whether the list represents near-term intent, long-term preference, or another purpose.