Viewing dependencies in Translation

Objects in the Translation cycle have the same parent-child dependency relationships as in the Authoring cycle. As in Authoring, the relationship between various objects in the Translation cycle affects how those objects can move through the workflow.

Dependency relationships in Translation

Dependencies in Translation are no different from other dependencies. There are parent objects and child objects. These dependency relationships determine how objects move through the Translation workflow.

For example, by moving a Translation Manifest to Translation:done, you can move its Language Manifests and content objects to Translation:done in one step—provided all those objects are at a status that allows them to move to Translation:done. Objects that are not at such a status block the movement of the Translation Manifest to Translation:done.

This is how dependency relationships work in Authoring, so it should be familiar.

Object Dependencies
Translation Manifest

Parents: none

Children: Language Manifests

Language Manifest

Parents: Translation Manifest

Children: translated content objects

translated map

Parents: Language Manifest

Children: translated content objects referenced by the map (sub-maps, topics, images, etc.)

What dependencies can you see?

The dependencies that you can see for translated content in CCMS Web differ from those you can see for Authoring content.

Objects localized using CCMS Desktop are not visible from the Dependencies view in CCMS Web.

For a Translation Manifest, you can see:

  • The source map in Authoring
  • The associated Language Manifests

For a Language Manifest, you can see:

  • The source map in Authoring
  • The associated Translation Manifest

For a content object in Translation, you can see:

  • The source object in Authoring
  • The associated Translation Manifests and Language Manifests

For an object in Authoring, you can see:

  • No dependencies in Translation

In CCMS Desktop, objects localized using CCMS Web do not appear in the Dependencies view at all.