A stable identifier can preserve a work’s identity when its display name changes. But an identifier is meaningful within a scheme. A bare number detached from its provider and record type can be ambiguous, especially when movies, series, seasons and episodes use separate namespaces.
Portability means retaining enough context for the destination to interpret the relationship. It does not mean that every application supports every source identifier or that a matching identifier proves programme access.
Preserve the complete identity reference
A catalogue might use a metadata-provider key for a film and another for a series. The same numeric spelling can exist in different contexts without naming the same work. Record the provider, record type and value together when the format allows it.
Names remain useful for people, but they are less stable as machine matching keys. Translated titles, punctuation changes and branding updates can alter a display label without changing the intended work. An appropriate identifier can help avoid a mistaken rematch during migration.
Check an export before relying on it
If the destination ignores the identifier, a successful import may fall back to title-based matching. That is a different assurance level. Record it honestly rather than claiming the identity was preserved solely because the field appeared in the exported text.
- Identify the provider identifier fields used by the source application.
- Confirm which record level each value describes.
- Inspect whether the export preserves the provider and type alongside the value.
- Read the receiving application’s supported identifier handling.
- Compare a few ambiguous titles after import to verify the intended match.
Avoid confusing identity with location
A metadata ID is not necessarily a playable address. It can identify a descriptive record without granting access to a programme. Do not paste it into an account field or invent a resource URL around it. Use the documented role of each value.
When a source corrects a mistaken identifier, check attached artwork, hierarchy and local progress relationships. Those may have been built around the earlier match. Updating one field is not proof that every dependent display has refreshed.
A good support report includes the source scheme, record type, current value and intended work. Keep account endpoints out of the example when they are unrelated to metadata identity. Clear portable identifiers help maintain accurate recognition across names and applications while leaving entitlement and playback as separate questions.
Useful answers
Is a bare numeric ID always enough to identify a work?
No. Preserve its source scheme and record type.
Does a metadata identifier grant programme access?
No. It identifies descriptive data, not account entitlement.
Can a destination ignore an exported identifier?
Yes. Check its documented support and verify the actual import match.