Page History
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
GOAL: Change content node reference from DMS to DAM module.
REQUIREMENTS:
- All image / video / audio that reference DMS content should link to DAM.
- No changes for Link's or image gallery needed. Asset should handle this internal data link.
- Possibility to migrate partial Content tree structure.
STEPS:
- Iterate the Content nodes and in case of a DMS reference change and remove property
- DMS reference
image=dms
imageDmsUUID=dmsuuid
- DAM reference
image=
dmsuuid
- DMS reference
Class: ChangeDataReferenceToDAMMigrationTask
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 | |
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> |
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.
REQUIREMENTS:
- All image / video / audio that are stored in the content repository are moved under the DAM repository.
- Create and initialize a new Asset Node based on the moved binary Node.
- From the content Node, refer this Asset as a standard DAM resource.
- Remove the old uploaded binary data from the content repository.
STEPS:
Iterate the Content nodes and in case of an upload content is found:
- Copy the binary node to the DAM repository
- Create the DAM folder
If the binary node was found underdemo-project/about/subsection-articles/article/content/01
this folder will be created in the DAM repository.
- Create the DAM folder
- Create an Asset Node based on the information stored in the moved binary node.
- Add the binary node as child of the Asset Node
- Change the property of the content Node in order to use the DAM module to refer the Binary data.
- Remove the old binary node stored under the content repository.
Class: MoveUploadedContentToDAMMigrationTask
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 | |
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: