Skip to content

Broken link: "Best practices: content tags and metadata" page was deleted but is still referenced from TRC delivery docs #38

@chrisdp

Description

@chrisdp

docs/THE ROKU CHANNEL/video-on-demand/delivery/index.md:109 links to doc:content-tags-and-metadata, but the page no longer exists.

What happened

The page was removed in two stages:

  1. ce50a72c (Jan 23, "fixes") — docs/TRC/video-on-demand/recs/content-tags-and-metadata.md content was merged into recs/index.md.
  2. 884f5067 (Feb 3, "fixed TRC docs") — the entire recs/ directory was deleted, removing both the merged page and the s3-connection page.

The inbound link at delivery/index.md:109 wasn't updated. The exact context:

Partners can aid in the curation of their content on Roku Channel by providing Tags with each movie, episode, or clip. Roku Channel editorial team and recommendations engine will utilize the provided Tags and Genres to help surface content on Roku Channel Platform UI. The more tags that are included, the more ways the content can be curated/surfaced to the end user. Please see Best practices: content tags and metadata for more details.

What the deleted page covered

The 223-line page (recoverable from git history) covered:

  • The "why" of tagging — recommendation algorithm uses tags; bad/mismatched tags hurt performance
  • Recommendation: ship at least 2 relevant Roku-provided tags per asset
  • Worked examples (Mean Girls / Schindler's List / Hoarders)
  • The full list of Roku Core Tags (~25 entries: action, comedy, drama, horror, etc.)
  • The full list of Niche/Specific Tags (~90 entries: anime, period pieces, true crime, etc.)
  • kidsdirected requirement
  • Editorial contacts (editorial@roku.com / svod-editorial@roku.com)

Coverage gap in current v2 docs

Of the topics above, only kidsdirected and the XML-level tag mechanics survive (in delivery/index.md and ovp-linear-ingest-spec.md). The Roku tag list, the "at least 2 relevant tags" recommendation, the mismatched-tags guidance, and the editorial contacts are not documented anywhere else in the repo.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions