Making Revisions

When you are a Content Manager for an item that is Provided by your organization, you’ll see the Edit Content button to the right in the content info box.

Clicking on the Edit Content button will take you to the Publishing Dashboard. You will then see a page that looks similar to the one shown below.

View the current revision of the content item without making any changes by using the View Content button and the View buttons for each content section: Descriptive, Structural, and Administrative.

Notice the Exit link to return to the previous screen and not make any revision.

Click the Make revision link to the right of the Published to change the descriptive, structural, and/or the administrative sections of your content.

You’ll see a page like below to make a revision to your content.

Learn more about each content section:

  • Descriptive: information about your content that makes it easy to find and identify
  • Structural: description of the organization and the formatting of the actual files
  • Administrative: connection to other systems or content as well as the status and visibility in DBL

Revision Notes

On the last page of the Administrative section, please add a Comment to describe the reason for making a revision. This is a good practice to help your organization keep track of changes you’re making. 

Note: this revision comment will be viewed by anyone who has access to this content, according to the Visibility setting.

Revision Number

When items are updated - the metadata information is changed, files added, book lists are reordered, etc., the updates are saved as a draft content item.

When you click on the Publish content button, the draft content is republished as the next revision number. Only the current revision is accessible for download. 

This means the previous revision will be archived, removing it from the DBL content library, but It will still remain documented on DBL for storage purposes.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.