I would like to see more of a separation in how assets and folders are managed in AEM. They are both managed the same way in 2 separate spaces, the assets pane and teh content tree. I would like to see the content tree be the space for managing folders and the assets pane be the space to manage assets.
Use-case:
Admin users managing assets are creating a folder structure with multiple nested folders to keep things organized. In this use case we'll use brands and lines of business. We have assets that are are for a specific brand
Current/Experienced Behavior:
Admin users managing assets are creating a folder structure with multiple nested folders to keep things organized. There are folder based profiles added to those folders including tags that are applied to any assets added to those. We also created a workflow that will copy tags down from parent to child so those tags aren't overridden by subfolder tagging.
In this use case we'll use brands and lines of business. We have assets that are are for a specific brand. They are placed in the folder for that brand and the metadata from the folder based profile is applied. There are multiple lines of business that fall under that brand and there is a folder for each one of those in there as well with a folder based profile added and specific tags for those. Assets are added to those and the tags are automatically applied.
This workflow is working fine, however, it leaves us with folders living among a sea of assets. When navigating the DAM via folder structure it becomes very difficult to sift through when there are hundreds (sometimes thousands) of assets surrounding the folders. If I have to update permissions or profiles for specific folders its either confusing (scrolling) or clunky (filtering on folders) to find the folder.
Improved/Expected Behavior:
I would like to be able to manage all of my folders in the content tree space. Create folders, select and get info, add folder based metadata, etc. And I'd like to be able to manage my assets in the asset pane.Create assets, select and get info, add asset based metadata, etc.
Environment Details (AEM version/service pack, any other specifics if applicable):
We are on the most current Assets as a Cloud Service environment.
@dmescia2 Thanks for proposing this idea. This has been reported to the engineering under the internal reference ASSETS-56547. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to Jira's status.