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

ExtendAssets screen for Touch UI

Nitish_Jain01
Level 3
Level 3

Hi All,

Need some inputs. 

There's a requirement to provide bulk metadata update functionality to the client. The solution suggested is to update Touch UI screen to provide the functionality to update metadata for document sin one go.

I know there's such functionality but it requires selection of one asset at a time. Client has more than 27k documents and not defined folder tolology. So the requirement is to update metadata in one go.

It has been suggested to extend the "http://localhost:4502/assets.html/content/dam" by providing one more custom option on the screen. Need some example which shows how we can customize the screen.

1 Accepted Solution
mvance
Correct answer by
Employee
Employee

Hi,

I'm not sure I fully understand the need to customise the screen.

For a large number of updates like this, best to write a program to access the JCR directly, and not use AEM at all:

https://helpx.adobe.com/experience-manager/using/programmatically-accessing-cq-content-using.html

To maintain over time, for new assets, if there is some need, you could use a custom launcher, for example. But ideally I think, the end users shoudl maintain the metadata, before teh files enter AEM, and after they are in the system

https://docs.adobe.com/docs/en/aem/6-2/administer/content/assets/metadata/meta-edit.html

Mark

View solution in original post

1 Reply
mvance
Correct answer by
Employee
Employee

Hi,

I'm not sure I fully understand the need to customise the screen.

For a large number of updates like this, best to write a program to access the JCR directly, and not use AEM at all:

https://helpx.adobe.com/experience-manager/using/programmatically-accessing-cq-content-using.html

To maintain over time, for new assets, if there is some need, you could use a custom launcher, for example. But ideally I think, the end users shoudl maintain the metadata, before teh files enter AEM, and after they are in the system

https://docs.adobe.com/docs/en/aem/6-2/administer/content/assets/metadata/meta-edit.html

Mark

View solution in original post