Media versions

A media version captures a rendition of a content item. Its asset title, version, attachment, file type and checksum make it easier to tell similar exports apart. The link to the content item preserves the operational context: who owns the work, which project it serves and whether the item is still in editing or already published.

An authorized Producer submits a draft rendition. The capture workflow resolves its linked content item, advances the rendition into review and refreshes the parent record. Usage rights belong to the media version, so a version intended for a new use can carry its own licensee, allowed use and date interval. The review of a rendition should therefore include both the file identity and its intended use.

• Rendition identity. The Producer records a version and file identity that can be compared with the source item.
• Review state. Submitted renditions move from draft into review, where the Editor can examine the actual attachment.
• Use terms. The Rights Manager links usage rights to the rendition and checks the allowed use and dates.

Decide which exports count as separate media versions. A resized image, a localized cut and a corrected final file may each need their own version record if the team must review or license them separately. Agree which checksum practice the team will use when files move between tools, and make the file type recognizable to the people who will publish the asset.

The team should also decide who is authorized to submit a rendition and who reviews it. A submitted version moves into review, but that step alone does not authorize publication of its parent content item. The file revision approval and publication flow must still be followed for the release candidate.

A project needs a landscape image and a square image. The Producer records each as a media version linked to the same content item and uploads the corresponding attachment. The square image is sent to review, while the landscape version remains draft. The Editor can see the different statuses and avoid treating the two exports as one approved file.

The Rights Manager records usage terms for the square version and checks the interval before it is used. If the allowed use covers only a specific channel, the team should keep that constraint with the version in its usage rights record. When the Editor reviews the item for publication, the exact rendition and its terms remain visible through the item and version links.

A later corrected square image gets another version label and attachment. Keeping the earlier checksum and version record preserves a useful comparison. A reviewer can open the version under review, compare its identity with the intended release, and return to the parent item without guessing which project or owner it belongs to.

• Media Versions List — Compare renditions by version, state, file identity and linked content.
• Versions under review — Focus on renditions submitted for review.
• Usage Rights List — Read the permitted use and interval attached to a version.

See media capture and rights review.