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
BedrockMission!

Learn More

View all

Sign in to view all badges

AEM DAM - Metadata Schema - Define Property Names

Avatar

Avatar
Validate 1
Level 2
MeenakshiP
Level 2

Likes

11 likes

Total Posts

35 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 10
Boost 1
View profile

Avatar
Validate 1
Level 2
MeenakshiP
Level 2

Likes

11 likes

Total Posts

35 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 10
Boost 1
View profile
MeenakshiP
Level 2

11-01-2017

Hi All,

When we define the metadata property name for an asset, as per my knowledge it is unique. Only one property as "Name" with value is allowed for any metadata field in crxde. For example: define dc:title. Or it can also be done using metadata Schema Editor where we can define 'Map to property'.

My question is:

Is there any way to define 2 different property names for a given metadata field? I have a requirement to change the existing metadata property keyword from 'X' to 'Y'.

However by doing this, asset metadata property in DAM will no longer display all the pre-populated values for existing metadata property 'X' in DAM.  How does AEM support this problem?

I know in crxde, system will still store old metadata value with reference to the old property name 'X', its just that it will not be shown to the user in asset properties if I change it to 'Y' property name since mapping is changed.

Do I need to write some custom workflow or any script which will copy the existing values to new one?

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Give Back 10
Level 2
huzaifaha985211
Level 2

Likes

0 likes

Total Posts

25 posts

Correct Reply

5 solutions
Top badges earned
Give Back 10
Give Back 5
Give Back 3
Give Back
Affirm 5
View profile

Avatar
Give Back 10
Level 2
huzaifaha985211
Level 2

Likes

0 likes

Total Posts

25 posts

Correct Reply

5 solutions
Top badges earned
Give Back 10
Give Back 5
Give Back 3
Give Back
Affirm 5
View profile
huzaifaha985211
Level 2

19-01-2017

Why not create another property for example oldName where you keep the old X value in it. You can hide it by not displaying it to the user and you can still reference to it in your code to pull the old values etc. 

Answers (1)

Answers (1)

Avatar

Avatar
Establish
Community Manager
kautuk_sahni
Community Manager

Likes

1,157 likes

Total Posts

6,247 posts

Correct Reply

1,144 solutions
Top badges earned
Establish
Coach
Originator
Contributor 2
Contributor
View profile

Avatar
Establish
Community Manager
kautuk_sahni
Community Manager

Likes

1,157 likes

Total Posts

6,247 posts

Correct Reply

1,144 solutions
Top badges earned
Establish
Coach
Originator
Contributor 2
Contributor
View profile
kautuk_sahni
Community Manager

12-01-2017

Hi 

Moving this thread to AEM "Asstes" topic so to have better contextual experts have a look at this.

~kautuk