Versions Compared

Old Version 10

changes.mady.by.user Eric Hechinger

Saved on

compared with

New Version Current

changes.mady.by.user Eric Hechinger

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

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.

...

PropertyDescriptionDefault valueValid values
taskNameTask name used by the reporting tool, and to log/display informations related to this task. String 
taskDescriptionTask Description used to display informations in the admin. central update view. String
originalPathsListList 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>
targetSubPathSubroot 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.		 String
dataRepositorySource 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 NodeVisitor pattern in order to treat the content tree. It is possible to add customs NodeVisitor by extending this class and override the protected List<NodeVisitor> addCustomVisitors() method.

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.

...

PropertyDescriptionDefault valueValid values
taskNameTask name used by the reporting tool, and to log/display informations related to this task. String 
taskDescriptionTask Description used to display informations in the admin. central update view. String
contentRepositoryContent repository name. Typically  website String
contentPathsListList 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>
targetSubPathSubroot folder that will contain the migrated uploaded binary. If targetSubPat=subRoot, then the DAM repository will have the following structure :
subRoot/demo-project/about/subsection-articles/article/content/01... If set to null, the exact same folder structure will be duplicate.		 String

 

FAQ:

Q: Are the images uploaded via the FCK Editor also handled by the task "Move uploaded binary from content(website) to DAM repository" ??

...