Introduction
DMS module do not exist anymore in M5. His re
Tasks
Migrate Binary data to DAM repository
GOAL: Migrate DMS (or other repository) into the DAM repository.
REQUIREMENTS:
- All node identifier should be kept (identifier for folder or dataNode are the same in DMS or DAM repository)
- Keep the DMS folder structure
- Possibility to add parent folder on the DAM repository
- Possibility to migrate partial DMS tree structure.
STEPS:
- Copy DMS specific repository's paths (
List<"/demo-project", "/demo-doc">) into the target DAM repository and sub-path. - Change the property's of Folder node and primaryType (
mgnl:folder) - Change the property's of Asset node and primaryType (
mgnl:asset)
Class: MoveDataRepositoryToDAMMigrationTask
Constructor attributes:
| Property | Description | Default value | Valid values |
|---|---|---|---|
taskName | Task name used by the reporting tool, and to log/display informations related to this task. | String | |
taskDescription | Task Description used to display informations in the admin. central update view. | String | |
originalPathsList | List of the data path to migrate. For example from the DMS repository : Arrays.asList("/demo-project", "/demo-doc") will only migrate the content of this two folders. | List<String> | |
targetSubPath | Subroot folder that will contain the migrated DMS folders. If targetSubPat=subRoot, then the DAM repository will have the following structure : subRoot/deom-project/... If set to null, the exact same folder structure will be duplicate. | | |
dataRepository | Source repository name. Typically dms | String |
Change DMS to DAM content references
Move uploaded binary from content(website) to DAM repository
FAQ:
Overview
Content Tools