• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

Ditaval not filtering nested topics

Participant ,
Aug 05, 2020 Aug 05, 2020

Copy link to clipboard

Copied

I have a ditamap with several nested topics describing different products. When I run my ditaval, it filters correctly at the root map level and inside of topics but it does not filter nested topics.

I've tried rejigging the ditaval file to both exclude all but my desired property or only include my desired property. Neither works.

Help, please.

 

Wanda

Views

239

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Participant , Aug 14, 2020 Aug 14, 2020

The problem turned out to be multiple values in the filtering attribute.

I have discovered that the issue is that there are multiple values in the attributes where the ditaval was not filtering. I added an entry in a test ditaval that included multiple value props and that filtered correctly.

 

So this worked:

 

<val>

    <prop att="props" val="OGC" action="exclude"/>

    <prop att="props" val="OGEP" action="include"/>

    <prop att="props" val="OGEXO" action="exclude"/>

    <prop att="props" val="OGC OG

...

Votes

Translate

Translate
Adobe Employee ,
Aug 06, 2020 Aug 06, 2020

Copy link to clipboard

Copied

Hi Wanda

 

Can you share a sample structure of the ditamap or possibly mail us so we can look into it.

 

Thanks

Amitoj Singh

Email: amisingh@adobe.com

 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Participant ,
Aug 14, 2020 Aug 14, 2020

Copy link to clipboard

Copied

The problem turned out to be multiple values in the filtering attribute.

I have discovered that the issue is that there are multiple values in the attributes where the ditaval was not filtering. I added an entry in a test ditaval that included multiple value props and that filtered correctly.

 

So this worked:

 

<val>

    <prop att="props" val="OGC" action="exclude"/>

    <prop att="props" val="OGEP" action="include"/>

    <prop att="props" val="OGEXO" action="exclude"/>

    <prop att="props" val="OGC OGEXO" action="exclude"/>

</val>

 

The alternative was to create duplicate topics and assign a single filtering value.

 

Wanda

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jul 23, 2024 Jul 23, 2024

Copy link to clipboard

Copied

LATEST

Does this mean that it's not enough to use a filtering value of "exclude" - that you also need a filtering value to "include"? THis seems pointless to me. I would assume that it's enough to flag certain elements to exclude (and anything unflagged is included by default)

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines