Duplicate set of metadata properties in Property Picker when using Metadata Schema Form Editor (AEM 6.5.14.0) | Community
Skip to main content
T
taxotaxo
February 10, 2023
Solved

Duplicate set of metadata properties in Property Picker when using Metadata Schema Form Editor (AEM 6.5.14.0)

  • February 10, 2023
  • 1 reply
  • 1064 views

Hi all,

I am fairly new to AEM and am trying to build a basic Schema form for assets that simplifies the "default" form for my users.

 

When I click on the checkbox icon in "Map to property" in a field's Settings, the Property Picker shows two complete metadata "folders," one nested inside the other:

This doesn't look right to me -- I don't think the second, nested "metadata" folder should be there, since those properties would be written to .jcr:content/metadata/metadata/dc:title (or similar). If the duplicate properties aren't supposed to be there, I'd like to remove them from the Property Picker so that they aren't accidentally included in a schema or search form.

 

The only documentation I've been able to find is a brief mention in the Tips and limitations section of the Configure metadata functionality doc page, which says, "Property Picker displays properties that are used in schema editors and search forms. Property Picker does not pick metadata properties from an asset." How can I find where these duplicate properties are coming from or at least prevent them from showing up in Property Picker?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by digarg17

This  is OOTB behaviour in AEM Assets 6.5 version I think. Even your local 6.5 sdk would have this metadata node under metadata although cloud only has a blank metadata node inside metadata node. 

 

For your purpose , you can map your custom client specific properties directly under ./jcr:content/metadata like if you check the default schema title property, it is applied as ./jcr:content/metadata/dc:title

1 reply

D
Adobe Employee
digarg17Adobe EmployeeAccepted solution
Adobe Employee
February 11, 2023

This  is OOTB behaviour in AEM Assets 6.5 version I think. Even your local 6.5 sdk would have this metadata node under metadata although cloud only has a blank metadata node inside metadata node. 

 

For your purpose , you can map your custom client specific properties directly under ./jcr:content/metadata like if you check the default schema title property, it is applied as ./jcr:content/metadata/dc:title

    T
    taxotaxoAuthor
    February 14, 2023

    Thanks for the info! Any idea what the second, nested set of properties is for? It seems confusing to have each property appear twice under the same asset node.

      Terms & ConditionsAccessibility statement

      Loading footer...