[MGNLDAM-51] MoveUploadedContentToDamMigrationTask store's fileName and extension redundantly Created: 03/Dec/12 Updated: 11/Feb/13 Resolved: 08/Jan/13 |
|
| Status: | Closed |
| Project: | Magnolia DAM Module |
| Component/s: | None |
| Affects Version/s: | 1.0 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Critical |
| Reporter: | Daniel Lipp | Assignee: | Eric Hechinger |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Date of First Response: |
| Description |
|
Reviewing |
| Comments |
| Comment by Eric Hechinger [ 08/Jan/13 ] |
|
This is a normal behavior. Do not forget that this is just a migration task that moves properties Basically, the original resource node properties are duplicated to the ressource node associated to the asset node. We also have to populate asset node properties with some informations. Normally theses informations are provided by the Asset dialog, but in this case, it's an existing content that is moved to an asset Node. So we have to populate Asset properties with available informations, in this case these informations are coming from the uploaded resource node. |
| Comment by Mikaël Geljić [ 05/Feb/13 ] |
|
bulk operation to close 2012 resolved tickets in MGNLUI, MGNLDAM, MGNLWORKFLOW and SCRUM. |