Missing metadata

Missing metadata is a field-level absence whose cause can lie in the source, acquisition, parsing, mapping or selection rather than in one universal refresh failure.

A blank overview in the library establishes that the displayed record lacks that overview. It does not identify where the information was lost or whether the source ever contained it.

Locate the missing field's boundary

Observation Possible boundary
Provider has no record for a home video No applicable descriptive source
Selected provider record has no overview Field absent at the source
Resource could not be obtained Acquisition did not supply usable data
Sidecar contains the field but uses an unsupported mapping Import does not create that library field
Correct value is a rejected candidate Selection/protection policy
Current source differs from a cached or earlier record Version/freshness relationship

These cases call for different evidence. Repeating the same request cannot create a provider record that does not exist or add support for an unrecognized property.

A successful download also does not establish successful field import. Readability, syntax and mapping come after acquisition.

Ask a field-specific question

For a missing title, inspect the relevant identity and descriptive source. For missing video dimensions, inspect the selected file and probe information. For a missing photo capture time, inspect the source's capture record rather than substituting its copy timestamp.

A resource can have correct technical metadata with no public catalogue match. A provider can supply a complete synopsis for an item whose local file cannot be read.

The meaning of “metadata missing” becomes useful only after identifying its scope.

Unknown and deliberately cleared differ

A source may omit a field because it has no claim. A user can also intentionally clear an incorrect value. Precedence explains why those states need different handling during a partial update.

Filling every blank from a low-confidence candidate can produce a visually complete but inaccurate library. Leaving an unknown field empty retains the distinction between evidence and a guess.

Refresh targets a particular cause

Emby's Metadata Manager documents missing-data and replacement refresh behavior. A suitable operation can obtain new provider information when that is the missing boundary.

If the match points to the wrong work, correct identification first. If a local descriptive record is not associated with the item, resolve that relationship. If the field is not supported by the applicable reader, another refresh of the same record will still encounter that mapping limit.

Keeping the field, source/entity, observed acquisition/import result and selected state together makes the next action concrete.

See Also

References