Apologies for the very generic name, the question is sort of complicated. I currently am running AEM 6.5 but hoping we will upgrade to a full DAM system and/or AEM in the cloud. Is there anything I should be keeping in mind as I write a file structure for assets? I'd like to future-proof my file system by doing anything that might be important for a cloud DAM now on basic 6.5 if it's possible. More work now, but hopefully must less work later.
I've read all the documentation for both platforms, I would love to hear any tips based on real-world usage. Thanks in advance!
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
Following are key considerations to bear in mind when transitioning to AEM in the cloud:
Following are key considerations to bear in mind when transitioning to AEM in the cloud:
Aem cloud support the same Asset structure that are on aem 6.5.
however you need to keep the scope of work in mind at this time only when you move to cloud as there are some feature that are supported on on-premise and AMS but not available on cloud like smart translation search, metadata write back for renditions and many more. You might also need to consider the file name length if you are going to use dynamic media on cloud as well. You can read this document to know in advance what will be going to work on aem assets as cloud https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/assets/home.html?la...
Make sure you create a back up of reindition
Remove the deprecated features
Name of the folder structure should be same
The node structure plan should be finalized
Migration script should be well written
To ease your work you can use groovy script
Before Upgrade:
After Migrate:
For Code Perspective:
Hope this will help you. Thanks
Views
Likes
Replies