davidjgonzalez
commented
6 years ago An immediate through it what should be the behavior for Folder level configurations like processing profiles, or smart tags. Would these settings automatically trigger/apply to the bulk move/merged assets? As a user, i would expect the assets in a folder to adhere to the folder's settings -- im not sure how challenging this would be (across the different processing concerns) or if it would naturally "just work" ... (TBH, I don't think some of the folder level processing "just works" using a single-asset move operation, though that doesn't mean this couldn't/shouldn't do better).
badvision
toddhaser
klcodanr
I would like to be able to supply a mapping spreadsheet that instructs a tool where to move and/or combine existing folders in the DAM. The source data should be a spreadsheet with the following columns:
A report should be generated that summarizes all actions taken. If a detailed report flag is checked, that report should include all assets moved as well.
Optionally, the user can enable an additional page update mode which scans for pages/components affected by changed asset paths and update them as needed.
A dry run mode should offer a report of operations required without making any changes.
The utility should also provide additional options to enable/disable versioning and publish behavior. The versioning should cover any pages updated, and publishing should include assets and/or pages which were previously published to automatically republish them after all changes have been made.