IMVDb music-video metadata
IMVDb identifies music-video records separately from audio recordings; an archived integration illustrates how artist and song-title evidence were mapped into video metadata.
A music video is a video work associated with a song and performers. An audio recording can accompany several visual versions: an official narrative video, a live performance or another edit.
IMVDb's music-video identity should therefore be kept separate from an album or audio-recording reference.
The visual work needs its own relationship
| Information | Useful scope |
|---|---|
| Song title and performing artist | Matching evidence |
| Audio recording identity | Recorded-audio relationship |
| Music-video record | The intended visual work/version |
| Video-production credits | Responsibilities for that production |
| Local encode | The particular media representation |
Identical artist/title words do not prove that two local videos are the same production. Their visual content and version can matter alongside catalogue evidence.
A concrete archived integration
The examined source is an archived IMVDb provider for Emby, pinned to 2 October 2018. It declares a music-video metadata interface and distinguishes search by artist/title from retrieval by a selected IMVDb identifier.
Its reader consumes fields such as id, song_title, year and artist-name data. That is direct evidence of the historical mapping. It does not establish that all production credits or every artist in a record were imported.
A field visible on a provider's catalogue and a field consumed by one integration are different observations. Cast and crew credits explains how responsibilities and identity need to remain structured.
Retain the music-video key
A provider-specific video identifier can anchor the selected visual record while MusicBrainz relationships describe the associated music. The keys should not be copied into each other's fields simply because both concern the same song.
For an Emby library, the intended content type, local title/artist evidence and available integration form the actual route. A descriptive record still needs to belong to the music video being played.
Current availability needs current evidence
The publisher's developer pages did not yield readable content during this source check. That observation does not establish permanent service closure.
This page uses the dated implementation to explain the relationship and its observed fields. It does not claim that every current Emby installation includes that provider or that a live IMVDb request succeeded. The linked publisher documentation is the place for a current interface check.