Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Updating metadata via REST API in dc namespace (AEM Cloud)

Avatar

Level 1

We are trying to accomplish a simple use case of uploading an asset and settings its metadata to AEM Cloud via REST API from an external system. We have been able to upload the asset using the new Cloud Upload API successfully.

 

Now, I am looking for an HTTP route to call from an external system into AEM that will allow me to update metadata on the newly uploaded asset. The Assets HTTP API lists an update metadata of an asset endpoint here:

https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/assets/admin/mac-ap...

The problem with this is it seems to update metadata only in the jcr namespace, however, we need to update metadata in the dc namespace as well (otherwise, the metadata values do not show up in the AEM UI). 

 

From what we understand there may be two approaches to solving this:

1) Using a workflow to sync values from the jcr namespace into the dc namespace that triggers when we set metadata from the Assets HTTP API - however, I have no familiarity with how to set up a workflow like this, so any documentation links or instructions would be helpful on how to do this.

2) Using a "sling API", but given previously I've only ever had to use HTTP APIs for AEM, I'm not familiar with if the sling API can be called via a REST-style HTTP request from an external system, and what the HTTP request would need to look like (and if this would require any customization deployed to AEM first).

 

Thank you for your help!

 

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

@tarunc49511966 I believe approach (1) is only applicable if metadata update made using Touch-UI and not using API. 

nitinjl_0-1648843887968.png

Ref - https://experienceleague.adobe.com/docs/experience-manager-64/assets/extending/mac-api-assets.html?l...

So, if that statement holds true, you should be able to update both dc and jcr properties in one API call. 

 

View solution in original post

1 Reply

Avatar

Correct answer by
Community Advisor

@tarunc49511966 I believe approach (1) is only applicable if metadata update made using Touch-UI and not using API. 

nitinjl_0-1648843887968.png

Ref - https://experienceleague.adobe.com/docs/experience-manager-64/assets/extending/mac-api-assets.html?l...

So, if that statement holds true, you should be able to update both dc and jcr properties in one API call.