Content ratings
A content rating is a classification within a named scheme and release/territory context, distinct from an audience or critic opinion score.
A content rating describes a classification under a particular scheme. A community rating of 8/10 describes an opinion score. The two values should not be used as if they answer the same question.
Labels belong to their schemes
| Example | Context |
|---|---|
| PG-13 | U.S. MPA film classification |
| TV-PG | U.S. television guideline label |
| 8/10 | An opinion-score scale |
A similar-looking PG component does not make the movie and television labels identical contracts. Their schemes and applicable descriptors supply the meaning.
A useful record retains scheme, territory and the relevant release or presentation context. A film's classification can differ across territories or editions.
Descriptors can supply more context
Some schemes accompany the broad category with information about the reason/content. That is another part of the classification relationship, not a second critic score.
Preserving only an unqualified display string can discard the source/territory context used for a later comparison.
In Emby, Metadata Manager documents parental-rating fields as inputs to configured access behavior. Accurate identity and imported classification consequently matter beyond the displayed label.
Missing and unrated are different states
An absent field can mean that the selected source did not supply a usable classification. An explicitly recorded unrated status is another claim.
Neither should be guessed from a genre such as Family. A provider failure also does not establish a low classification.
The server's configured handling of unknown or overridden values belongs to its product rules. The metadata itself supplies evidence, rather than a universal allow/block flag.
Corrections need the intended release
A classification for a differently edited version can be accurate for that version while unsuitable for the local presentation. Compare the identity, territory, edition and source before replacing the field.
Do not make a cross-scheme conversion merely because two labels contain similar words. The source's defined scheme and the application's supported policy determine the usable relationship.