Act on your first review feedback
In this tutorial, we’re going to respond to a review in a Collaboration Hub project: upload new versions of rejected assets, and send them back to the same people for a second review. Most content goes through more than one round of feedback, and each round should build on the last, not start again. By the end, you’ll have two re-versioned assets in a second review, with the reviewer able to compare each new version against the old one.
This is part 3 of 6 in the project manager tutorials. Previous: Run your first project review. Next: Follow your first project through its workflow.
Prerequisites
To follow this tutorial, you need:
-
To have completed Run your first project review, with both assets rejected. You’ll use the same project, review, and second email address.
-
The same access as that tutorial: the Creator role for Reviews, under Adaptation Studio, and access to Collaboration Hub projects. Each role’s permissions are listed in User role presets and permissions.
-
An amended version of each of the two images, saved with the same file names as the originals.
Keeping the file names the same matters in step 3, where the platform matches new versions to existing assets by name. Make a small, visible change to each image, such as a larger logo or a warmer colour, so the difference is easy to spot later.
|
What you see here depends on your workspace’s configuration. Which project roles can upload new versions and recreate reviews is set up for your workspace. If Reversion or Recreate Review isn’t available, contact your administrator. |
What we’ll create
We’ll find the two rejected assets in the project and upload a new version of each, one at a time and then in bulk. Then we’ll recreate the review, so the same reviewer can check the new versions against the feedback they gave.
The tutorial takes about 20 minutes, including the videos, in four steps:
Step 1: Find the rejected assets
A review’s decisions are recorded on the assets themselves, in the project’s resources.
We’re going to find our two rejected images.
-
Open your project and select the Resources tab.
-
Select the asset folder that holds the two images.
You’ll notice that each image now has a red Rejected status pill. Approved assets have a green pill instead.
In a folder with many assets and mixed outcomes, use the review state filter to display only the rejected ones.
Step 2: Re-version one asset
Re-versioning replaces an asset with a new version, while keeping it the same asset in the project and the review.
We’re going to upload the new version of the first image.
-
Open the first image’s menu and select Reversion.
-
In the Reversion Asset window, upload the amended first image.
-
Select Reversion.
You’ll notice that:
-
The tile displays the new version.
-
The version number has gone up.
-
The Rejected pill has gone, because the new version hasn’t been reviewed yet.
Only the latest version is displayed in the folder. The earlier version is kept, and reviewers can still compare against it.
Step 3: Re-version in bulk
When several assets need new versions, upload them all in one go. We’ll use the bulk route for the second image, so you know how it works when there are many.
-
In the toolbar above the asset tiles, select Reversion.
-
Drag the amended second image into the upload window, or browse for it.
The platform matches the file to the existing asset by its file name.
-
Select Upload.
You’ll notice that the second image now has a new version number, and its status pill has reset, like the first one.
If a file name doesn’t match an existing asset, an error appears instead, and that file isn’t uploaded.
A version number on the end of the name, such as _v2, still matches.
Anything else needs the single route from step 2.
Step 4: Recreate the review
Recreating a review starts a follow-up round with the same settings and people, so reviewers can compare each new version with the one they commented on.
We’re going to recreate Spring campaign first review.
-
In your project, open the Reviews tab, then the Completed Reviews folder.
-
Find
Spring campaign first review, open its menu, and select Recreate Review.
The recreated review opens, ready to manage.
-
Change the name to
Spring campaign second review. -
Set the deadline to tomorrow.
-
Check the reviewer list.
-
Select Start Review, then Confirm.
You’ll notice that:
-
Your second email address is still the reviewer and decision maker; the recreated review kept them.
-
The review becomes active as soon as you confirm.
Open your second inbox. A new email says a follow-up review is available, and it includes each asset’s version number. Select Go to Review. At the top of Review Studio, a dropdown lets the reviewer switch between versions. Compare displays the old and new versions side by side, with the first round’s comments. To compare versions as a reviewer, follow Make your first review decisions.
The finished second round
Here’s what we’ve built:
-
Assets: both images re-versioned, one through its own menu and one in bulk, each with a higher version number.
-
Review:
Spring campaign second review, recreated from the first round with the same decision maker. -
Reviewer’s view: the new versions, with the old versions and their comments available to compare.
Conclusion
In this tutorial, you’ve learned how to:
-
Find rejected assets in a project using their status pills.
-
Re-version a single asset.
-
Re-version assets in bulk by matching file names.
-
Recreate a review for a follow-up round.
Once the decision maker approves the new versions, the project can move on to publishing. To follow the project through the rest of its workflow, continue with Follow your first project through its workflow.
Understanding Collaboration Hub explains how reviews fit into the content workflow.