[MGNLDAM-4] Determine and Implement strategy for performing migration of all content in DMS Created: 30/Oct/12  Updated: 11/Feb/13  Resolved: 26/Nov/12

Status: Closed
Project: Magnolia DAM Module
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0

Type: Task Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Eric Hechinger
Resolution: Fixed Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLMIGRATION-172 Create DAM migration task Closed
is related to MGNLSTK-1030 Update Demo project in order to Use D... Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MGNLDAM-23 Migrate Binary data to DAM repository Sub-task Closed Eric Hechinger  
MGNLDAM-24 Change DMS to DAM content references Sub-task Closed Eric Hechinger  
MGNLDAM-25 Move uploaded binary from content(web... Sub-task Closed Eric Hechinger  
Template:
Acceptance criteria:
Empty
Task DoR:
Empty

 Description   

In particular - I added an optional dependency of the dam module on demo-project so that its assets would be in the dms workspace when the dam module gets installed so that all assets would be migrated.
Maybe there is a different way to do this. Maybe it becomes part of the whole migration project.



 Comments   
Comment by Christopher Zimmermann [ 05/Nov/12 ]

What code performs migration - DAM module? Migration Module?
What needs to be migrated?
Contents of DMS to DAM
Transactional? How to handle errors.
Links to DMS assets that are stored in page content? (URI Rewriting?)
Code that references DMS?
What else needs to be considered - what are the implications of moving assets and changing their type?

Generated at Mon Feb 12 04:55:37 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.