Hi - I'm trying to see if I can apply metadata to a folder and then push that metadata to its contents
We catalog creative projects and the folder metadata is the same for each asset, unless there happens to be a restricted asset inside it. What I want to do is apply the metadata to the project folder (client0000_description) and then push all of that metadata to the included files. Right now, it seems as if we can only batch apply metadata to files that exist in a single folder or select the folders we need to apply the metadata to and then export an excel doc, add in all of the information needed by hand, not even being able to utilize the dropdowns that exist in the system already) and then import that excel. This process takes 4-5x longer than the asset system we've been using.
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
Hi @JamesRo12 ,
You may follow either of the approaches mentioned below
Approach 1: Metadata Profiles
https://experienceleague.adobe.com/en/docs/experience-manager-learn/assets/configuring/metadata-prof...
You can explore metadata profile option if you want to try available option out of the box. As you mentioned since metadata is same for all the assets under a particular folder, create a metadata profile and apply it on the folder level. When any asset gets uploaded in this folder it will go under processing state during which it will inherit the properties specified in the metadata profile. To view these properties on asset level you may want to create a metadata schema.
More on metadata schema - https://experienceleague.adobe.com/en/docs/experience-manager-learn/assets/configuring/metadata-sche...
Approach 2 : Custom Workflow Process Step
https://experienceleague.adobe.com/en/docs/experience-manager-learn/forms/adaptive-forms/custom-proc...
If there is a scope of custom development another approach would be to create a custom workflow process step. Here you will get more control of the data to be inherited or any properties to be skipped. This process step can be added to the default DAM Asset Upload workflow (on on premise system) or can be added as a post processing workflow on AEM as Cloud Service
More on Post Processing Workflows - https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/assets/manage/as...
Hi @JamesRo12 ,
You may follow either of the approaches mentioned below
Approach 1: Metadata Profiles
https://experienceleague.adobe.com/en/docs/experience-manager-learn/assets/configuring/metadata-prof...
You can explore metadata profile option if you want to try available option out of the box. As you mentioned since metadata is same for all the assets under a particular folder, create a metadata profile and apply it on the folder level. When any asset gets uploaded in this folder it will go under processing state during which it will inherit the properties specified in the metadata profile. To view these properties on asset level you may want to create a metadata schema.
More on metadata schema - https://experienceleague.adobe.com/en/docs/experience-manager-learn/assets/configuring/metadata-sche...
Approach 2 : Custom Workflow Process Step
https://experienceleague.adobe.com/en/docs/experience-manager-learn/forms/adaptive-forms/custom-proc...
If there is a scope of custom development another approach would be to create a custom workflow process step. Here you will get more control of the data to be inherited or any properties to be skipped. This process step can be added to the default DAM Asset Upload workflow (on on premise system) or can be added as a post processing workflow on AEM as Cloud Service
More on Post Processing Workflows - https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/assets/manage/as...
Views
Likes
Replies