Exporting Registry Object

To export an object successfully, you must have view permission on the object that you select for export and all the additional objects that CentraSite exports with that object. This section explains how the export process handles:

Object Ownership: Object's ownership and organizational attributes are included with the exported object. However, this data is imported with an object only if the Keep current owner and Keep current organization options are enabled at import time. However, how to assign the ownership to the imported object is determined by whether the:

Imported object replaces an existing object if the object in the archive is newer than the existing object in the registry or the Allow replace of registry objects option is used. The existing object is replaced but its Owner and Organization attributes remain unchanged (the updated object belongs to the same organization and user as it did before it was replaced by the copy from the archive file).

Imported object is added to the registry as a new object, its organizational and user ownership is determined by the following parameters:

If Keep current owner is set in the import dialog and the original owner exists with the same UUID on the target, the objects is long to that user after import. If the user with the same UUID does not exist on the target, the import of the particular object fails.

If Keep current organization is set in the import dialog, the original associations of the objects are maintained if the organization exists with the same UUID on the target. If the organization with the same UUID does not exist on the target, the import of the particular object fails.

Instance Level Permissions: The export process does not export the instance-level permissions that are assigned to an object.

Supporting Documents: When you export an asset, the asset's supporting documents are also exported with the asset.

Note:

The export feature does not provide a way to export supporting documents or other repository items directly. However, you can use the Download button on the Supporting Document Library page to download documents from one instance of CentraSite and then upload them to another.

Other Versions of an Object: If you export an asset that is versioned, the exported asset includes a reference to the previous version of the asset. However, the referenced version itself does not be included in the archive.

Different Versions of CentraSite: CentraSite does not restrict the transfer of objects between different product versions. However, if a user-defined type is exported and already exists on the target machine, the import fails if the existing type already has instances and the modification of the type due to the different product version is such that the existing instances do not validate with the type any longer. Typically, enhancements of the type with additional fields do not cause any problems, but modification of existing fields may lead to unexpected results.

The additional objects that CentraSite includes in the archive file when it exports an object are determined by the specific export handler that is associated with the exported object's type. Generally, CentraSite includes the following objects with any object that you export:

The supporting documents that are attached to the object.

The type definition of the object, if the object type is a custom object type or a modified predefined object type.

The taxonomy associated with the object type, if the taxonomy is a custom taxonomy or a modified predefined taxonomy.

The association types associated with the object type, if the association types is a custom association type or a modified predefined association type.

Additionally, if the object is an instance of a composite type, CentraSite also exports the object's components referred by Relationship attributes.

The export set for an object generally contains all objects referenced by an object (referenced standard objects such as predefined asset types are not included, since these can be expected to exist on the target machine). However, you may examine the export report for warnings. If there are warnings and they identify objects that is not present in the target registry at import time (usually indicated by a INMIEW0038 warning in the report), you must either:

Export the referenced objects separately and import them into the target registry before you import the archive file that you just created.

Use the Add to List command to build a list that includes the object that you want to export and all the objects that are identified by the INMIEW0038 warnings and export the list. This generates an archive file that contains the exported objects and the objects that it references.

CentraSite does not automatically export the referenced objects that are referred by custom associations unless the check box Include assets referenced by selected assets is selected. In this case, a warning message is displayed to indicate the missing references. Ensure that such referenced objects are already present in the target registry when importing archives.