Metadata Schema values rules | Community
Skip to main content
A
alanas47134608
June 10, 2019
Solved

Metadata Schema values rules

  • June 10, 2019
  • 4 replies
  • 1934 views

Hi,

I'm working with the DAM in my version of AEM and I've created metadata schemas for some folders in which I've added dropdown fields with different values a user can select to add to their file's metadata. I'm wondering, is it okay that these values have special characters and spaces in them? For example, we have one value has both its display text and value as, "Aerospace & Defense." Has anyone run into this issue?

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 arunpatidar

Hi,

I believe AEM encode the values before it is being used, so shouldn't be any problem.

are you facing any issues?

4 replies

arunpatidar
Community Advisor
arunpatidarCommunity AdvisorAccepted solution
Community Advisor
June 11, 2019

Hi,

I believe AEM encode the values before it is being used, so shouldn't be any problem.

are you facing any issues?

Arun Patidar
    A
    alanas47134608Author
    June 11, 2019

    Hi Arun Patidar,

    Thank you so much for replying! I have not had any issues and the system seems to be taking the value just fine when I select it in the activated schema.

    If you wouldn't mind answering one more question, I'm wondering, do you know if the option text (top) and option value (bottom) should be the same? I assumed yes, hence using a special character in the value.

    L
    Adobe Employee
    leoberliantAdobe Employee
    Adobe Employee
    June 11, 2019

    Text and value can be different. As such, if you have text as "Text 1" and value as "Value1 & value1" in a Touch UI it will presents Text1 and in JCR it will be  "Value1 & value1"

      A
      alanas47134608Author
      June 11, 2019

      Hi berliant​,

      Oh great - thank you for the explanation and images. So it seems like whether I keep the text and value the same or different is optional depending on how I'd like it to appear in the JCR. I also see again, via your example, that an ampersand in the value works fine!

      Terms & ConditionsAccessibility statement

      Loading footer...