Page History

...

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/Others Data repository to the DAM repository.
   Update folder and Data node type and property.
• Update Content DMS references (UUID link from content to DMS).
   Adapt the content property in order to work with the new DAM module and asset handling.
• Migrate Uploaded Data (in the content tree) to the DAM repository.
   Copy binary & create DAM  asset.
   Adapt the content property in order to work with the new DAM module and asset handling.

ToDo based on these task: (Is this section redundant with below items???)

• 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

...