An asset is described with metadata and has artifacts, each of which can be modified. The nature of the modification,
or update, dictates if a new asset version is required.
It is up to the organization to establish the asset versioning policies, such as when a new asset version is required.
For example, modifying a grammar issue in the metadata may be deemed by some to not require a new asset version.
Whereas if the grammar issue is in one of the artifacts, then some may state that a new asset version is required.
A general guideline to follow is to categorize asset modifications as structural and non-structural. Structural changes
include modifying the following items:
-
Metadata
-
-
Asset version
-
Asset relationship
-
Artifact reference
-
Artifact
-
-
File name or path or content
In general, these kinds of changes require a new asset version to be created. Non-structural changes are modifications
to asset metadata other than those described; and do not require a new asset version.
The organization needs to determine the tolerance level for changes before requiring a new asset version. When the new
version is created then the asset review and approval activities take place.
|