Skip to page content

Relationships for an Asset in Cascade

Relationships are what make content management work efficiently. Link to any asset through Internal links, and you can find that asset no matter where someone moves it. This promotes content reuse, good content strategy, collaboration, and good SEO practices.

It starts with identifying the Content Owner. As the Content Owner of any asset, you can make sure your content is regularly updated in a single spot: your spot on your website. All non-owners who have a piece of that content, but no true ownership, can link to your content, the assets on your website.

You can see who all is connected to you for your important information by

  1. finding an asset,
  2. selecting More,
  3. Relationships, and
  4. viewing the assets that point to your asset, who modified them last and when, and who owns those assets.

You can select their assets in this Relationship report, and collaborate with them regarding any changes you need them to make regarding pointing to your asset. For example, if someone was pointing to your fee statement page as part of their tuition and fees process, and they mentioned on-campus bikes were $15 before introducing your link, you could Comment on their asset, and tell them the fee for on-campus bikes went up to $20. You can even create a Task for them to complete regarding this change. Obviously, the less they describe of your content, the better from a management and SEO perspective, but sometimes other maintainers may need to point out main topics before asking their users to come to your web content for the full details.

This is also helpful when you need to remove content from your website, but other websites are sharing it. You can contact each of them and request they remove their link to your asset or change the link to a more appropriate asset you've now defined for your website's content strategy.

Relationships are also a good reminder that not all changes require deleting assets and telling everyone to change their links. For example, if you properly named a file on your website in a generic manner, like undergraduate-application.pdf, and many websites pointed to it, all you'd have to do is Edit that file asset, drop a new file in there, and publish the changes each period. The address doesn't change, and no one has to update anything except you, since you did the quick work of a rather easy and sophisticated find and replace.