Page History
Introduction
DMS module do not exist anymore in M5. His re
Proposed approach
Create DAM migration tasks located in the DAM module. Migration project is only used to migrate from 4.4.6 to 4.5.x.
All migrations needed to move from 4.5.x to 5.0.x are from module's responsibility.
...
- Migrate DMS to DAM repository.
Export the DAM bootstrap file. - Migrate demo-project / demo-features data reference from DMS to DAM
Export the demo-project and demo-features bootstrap files - Update Demo project version handler
Register a new delta (from 2.5) with the 3 DAM migration tasks - Update Demo project bootstrap files
Replace the existing DMS/Demo-project/Demo-features bootstrap files with the previously newly created.
Tasks
Migrate Binary data to DAM repository
GOAL: Migrate DMS (or other repository) into the DAM repository.
...
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
GOAL: Change content node reference from DMS to DAM module.
...
Info |
---|
This module used the All visitor define will then be apply to the content tree. |
Move uploaded binary from content(website) to DAM repository
GOAL: Move the binary data stored under the content repository (website
) to the DAM repository.
...
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 | |
contentRepository | Content repository name. Typically website | String | |
contentPathsList | List of the content path to handle. For example from the website repository : Arrays.asList("/demo-project") will only handle the content of this folder. | List<String> | |
targetSubPath | Subroot folder that will contain the migrated uploaded binary. If targetSubPat=subRoot , then the DAM repository will have the following structure : subRoot If set to null, the exact same folder structure will be duplicate. |
|
FAQ:
Q: Are the images uploaded via the FCK Editor also handled by the task "Move uploaded binary from content(website) to DAM repository" ??
...