Topics

filtering <othermeta>


Dan Vint
 

I checked the spec and othermeta supports/allows filtering with the @product attribute. I'm running the HTML transformation and it seems like the OT is not processing these elements. I have this map

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE map PUBLIC "-//PINGIDENTITY//DTD DITA Map//EN" "PingIdentityMap.dtd">
<map id="kmd1603213063098" xml:lang="en-us">
<title>FORMAT: Single map to use DITAVALS at build time - build manifest
<ph product="prod_b">Product B</ph>
<ph product="prod_c">Product C</ph>
<ph product="prod_a">Product A</ph></title>
<topicmeta>
<othermeta content="FormatProdA" name="bundle" product="prod_a"/>
<othermeta content="FormatProdB" name="bundle" product="prod_b"/>
<othermeta content="Formatcommon" name="bundle" product="prod_common"/>
<othermeta content="FormatProdBC" name="bundle" product="prod_bc"/>
<othermeta content="FormatProdAC" name="bundle" product="prod_ac"/>

</topicmeta>
<containerref href="eek1572622465806.ditamap"/>

<topicref keyref="vln1599578426163"/>
<!-- topic with ditavals -->
<topicref keyref="sfq1599578470970" product="prod_a"/>
<!-- topic product A -->
<topicref keyref="wkc1599578503581" product="prod_b"/>
<!-- topic product B -->
<topicref keyref="vva1599578551353"/>
<!-- topic all -->
<topicref keyref="tpu1603147966773" product="prod_c"/>
<!-- topic product C -->

<topicref keyref="vln1599578426163" product="prod_c prod_b"/>
<!-- topic with ditavals for Prod B and C-->
</map>

And for instance this DITAVAL file

<ditaval id="dyr1599584459162" xml:lang="en-us">
<title>FORMAT Prod A include Prod B and Prod C exclude</title>
<shortdesc/>
<body>
<ditavalcontent>
<val>
<prop action="exclude" att="product" val="prod_c"/>
<prop action="exclude" att="product" val="prod_b"/>
<prop action="include" att="product" val="prod_a"/>
</val>
</ditavalcontent>
</body>
</ditaval>

I know the process of filtering is working because the topics are being stripped out properly, but the HTML shows all the metadata being generated

<html lang="en-us"><head>
<meta charset="UTF-8"></meta>
<meta name="copyright" content="(C) Copyright 2020"></meta>
<meta name="DC.rights.owner" content="(C) Copyright 2020"></meta>
<meta name="DC.type" content="concept"></meta>
<meta name="description" content=""></meta>
<meta name="bundle" content="FormatProdAC"></meta>
<meta name="bundle" content="FormatProdBC"></meta>
<meta name="bundle" content="Formatcommon"></meta>
<meta name="bundle" content="FormatProdB"></meta>
<meta name="DC.format" content="HTML5"></meta>
<meta name="DC.identifier" content="tpu1603147966773"></meta><meta name="DC.language"

The bundle value controls how Zoomin manages my content. I'm generating 5 different versions and Zoomin uses this to identify if the content is new or replaces something on the site.

In writing this up, I'm looking at a topic from each bundle and I'm seeing different combinations of the values being written out

<meta name="bundle" content="FormatProdAC"></meta>
<meta name="bundle" content="FormatProdBC"></meta>
<meta name="bundle" content="Formatcommon"></meta>

<meta name="bundle" content="FormatProdAC"></meta>
<meta name="bundle" content="FormatProdBC"></meta>
<meta name="bundle" content="Formatcommon"></meta>
<meta name="bundle" content="FormatProdB"></meta>
<meta name="bundle" content="FormatProdAC"></meta>
<meta name="bundle" content="FormatProdBC"></meta>
<meta name="bundle" content="Formatcommon"></meta>
<meta name="bundle" content="FormatProdB"></meta>

<meta name="bundle" content="FormatProdAC"></meta>
<meta name="bundle" content="FormatProdBC"></meta>
<meta name="bundle" content="Formatcommon"></meta>
<meta name="bundle" content="FormatProdA"></meta>

<meta name="bundle" content="FormatProdAC"></meta>
<meta name="bundle" content="FormatProdBC"></meta>
<meta name="bundle" content="Formatcommon"></meta>
<meta name="bundle" content="FormatProdA"></meta>

<meta name="bundle" content="FormatProdAC"></meta>
<meta name="bundle" content="FormatProdBC"></meta>
<meta name="bundle" content="Formatcommon"></meta>
<meta name="bundle" content="FormatProdB"></meta>

I modified my DITAVAL file to remove the other labels

<ditaval id="dyr1599584459162" xml:lang="en-us">
<title>FORMAT Prod A incluude Prod B and Prod C exclude</title>
<shortdesc/>
<body>
<ditavalcontent>


<val>
<prop action="exclude" att="product" val="prod_c"/>
<prop action="exclude" att="product" val="prod_b"/>
<prop action="include" att="product" val="prod_a"/>

<prop action="exclude" att="product" val="prod_common"/>
<prop action="exclude" att="product" val="prod_bc"/>
<prop action="exclude" att="product" val="prod_ac"/>


</val>
</ditavalcontent>
</body>
</ditaval>

But that didn't change my results.

Any idea what I'm missing?

..ddan


Melissa Kershes
 

Hey Danny. 

When I was doing this the bundle name was generated as part of the transform so I used that to make sure I had uniqueness when it was needed.  

The IXIASoft CCMS renames the ditaval file to the map id when it is exported for processing.  Since the bundle name is generally the mapid_ditavalID i added a value in the middle of the bundle name based on vrm. You could use your ditaval values to differentiate the bundle name.  

Melissa

On Tue, Oct 20, 2020, 7:34 PM Dan Vint <dvint@...> wrote:
I checked the spec and othermeta supports/allows filtering with the
@product attribute. I'm running the HTML transformation and it seems
like the OT is not processing these elements. I have this map

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE map PUBLIC "-//PINGIDENTITY//DTD DITA Map//EN"
"PingIdentityMap.dtd">
<map id="kmd1603213063098" xml:lang="en-us">
        <title>FORMAT: Single map to use DITAVALS at build time - build
manifest
                <ph product="prod_b">Product B</ph>
                <ph product="prod_c">Product C</ph>
                <ph product="prod_a">Product A</ph></title>
        <topicmeta>
                <othermeta content="FormatProdA" name="bundle" product="prod_a"/>
                <othermeta content="FormatProdB" name="bundle" product="prod_b"/>
                <othermeta content="Formatcommon" name="bundle"
product="prod_common"/>
                <othermeta content="FormatProdBC" name="bundle" product="prod_bc"/>
                <othermeta content="FormatProdAC" name="bundle" product="prod_ac"/>

        </topicmeta>
        <containerref href="eek1572622465806.ditamap"/>

        <topicref keyref="vln1599578426163"/>
        <!-- topic with ditavals -->
        <topicref keyref="sfq1599578470970" product="prod_a"/>
        <!-- topic product A -->
        <topicref keyref="wkc1599578503581" product="prod_b"/>
        <!-- topic product B -->
        <topicref keyref="vva1599578551353"/>
        <!-- topic all -->
        <topicref keyref="tpu1603147966773" product="prod_c"/>
        <!-- topic product C -->

        <topicref keyref="vln1599578426163" product="prod_c prod_b"/>
        <!-- topic with ditavals for Prod B and C-->
</map>

And for instance this DITAVAL file

<ditaval id="dyr1599584459162" xml:lang="en-us">
        <title>FORMAT Prod A include Prod B and Prod C exclude</title>
        <shortdesc/>
        <body>
                <ditavalcontent>
                        <val>
                                <prop action="exclude" att="product" val="prod_c"/>
                                <prop action="exclude" att="product" val="prod_b"/>
                                <prop action="include" att="product" val="prod_a"/>
                        </val>
                </ditavalcontent>
        </body>
</ditaval>

I know the process of filtering is working because the topics are being
stripped out properly, but the HTML shows all the metadata being
generated

<html lang="en-us"><head>
<meta charset="UTF-8"></meta>
<meta name="copyright" content="(C) Copyright 2020"></meta>
<meta name="DC.rights.owner" content="(C) Copyright 2020"></meta>
<meta name="DC.type" content="concept"></meta>
<meta name="description" content=""></meta>
<meta name="bundle" content="FormatProdAC"></meta>
<meta name="bundle" content="FormatProdBC"></meta>
<meta name="bundle" content="Formatcommon"></meta>
<meta name="bundle" content="FormatProdB"></meta>
<meta name="DC.format" content="HTML5"></meta>
<meta name="DC.identifier" content="tpu1603147966773"></meta><meta
name="DC.language"

The bundle value controls how Zoomin manages my content. I'm generating
5 different versions and Zoomin uses this to identify if the content is
new or replaces something on the site.

In writing this up, I'm looking at a topic from each bundle and I'm
seeing different combinations of the values being written out

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdB"></meta>
        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdB"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdA"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdA"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdB"></meta>

I modified my DITAVAL file to remove the other labels

<ditaval id="dyr1599584459162" xml:lang="en-us">
        <title>FORMAT Prod A incluude Prod B and Prod C exclude</title>
        <shortdesc/>
        <body>
                <ditavalcontent>


                        <val>
                                <prop action="exclude" att="product" val="prod_c"/>
                                <prop action="exclude" att="product" val="prod_b"/>
                                <prop action="include" att="product" val="prod_a"/>

                                <prop action="exclude" att="product" val="prod_common"/>
                                <prop action="exclude" att="product" val="prod_bc"/>
                                <prop action="exclude" att="product" val="prod_ac"/>


                        </val>
                </ditavalcontent>
        </body>
</ditaval>

But that didn't change my results.

Any idea what I'm missing?

..ddan






Dan Vint
 

I'll check that out. I'm using a build manifest to generate these all at one time and they don't demonstrate that functionality.



Sent from my Verizon, Samsung Galaxy smartphone


-------- Original message --------
From: Melissa Kershes <sarala557@...>
Date: 10/20/20 4:40 PM (GMT-08:00)
To: main@dita-users.groups.io
Cc: dita-users@groups.io
Subject: Re: [dita-users] filtering <othermeta>

Hey Danny. 

When I was doing this the bundle name was generated as part of the transform so I used that to make sure I had uniqueness when it was needed.  

The IXIASoft CCMS renames the ditaval file to the map id when it is exported for processing.  Since the bundle name is generally the mapid_ditavalID i added a value in the middle of the bundle name based on vrm. You could use your ditaval values to differentiate the bundle name.  

Melissa

On Tue, Oct 20, 2020, 7:34 PM Dan Vint <dvint@...> wrote:
I checked the spec and othermeta supports/allows filtering with the
@product attribute. I'm running the HTML transformation and it seems
like the OT is not processing these elements. I have this map

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE map PUBLIC "-//PINGIDENTITY//DTD DITA Map//EN"
"PingIdentityMap.dtd">
<map id="kmd1603213063098" xml:lang="en-us">
        <title>FORMAT: Single map to use DITAVALS at build time - build
manifest
                <ph product="prod_b">Product B</ph>
                <ph product="prod_c">Product C</ph>
                <ph product="prod_a">Product A</ph></title>
        <topicmeta>
                <othermeta content="FormatProdA" name="bundle" product="prod_a"/>
                <othermeta content="FormatProdB" name="bundle" product="prod_b"/>
                <othermeta content="Formatcommon" name="bundle"
product="prod_common"/>
                <othermeta content="FormatProdBC" name="bundle" product="prod_bc"/>
                <othermeta content="FormatProdAC" name="bundle" product="prod_ac"/>

        </topicmeta>
        <containerref href="eek1572622465806.ditamap"/>

        <topicref keyref="vln1599578426163"/>
        <!-- topic with ditavals -->
        <topicref keyref="sfq1599578470970" product="prod_a"/>
        <!-- topic product A -->
        <topicref keyref="wkc1599578503581" product="prod_b"/>
        <!-- topic product B -->
        <topicref keyref="vva1599578551353"/>
        <!-- topic all -->
        <topicref keyref="tpu1603147966773" product="prod_c"/>
        <!-- topic product C -->

        <topicref keyref="vln1599578426163" product="prod_c prod_b"/>
        <!-- topic with ditavals for Prod B and C-->
</map>

And for instance this DITAVAL file

<ditaval id="dyr1599584459162" xml:lang="en-us">
        <title>FORMAT Prod A include Prod B and Prod C exclude</title>
        <shortdesc/>
        <body>
                <ditavalcontent>
                        <val>
                                <prop action="exclude" att="product" val="prod_c"/>
                                <prop action="exclude" att="product" val="prod_b"/>
                                <prop action="include" att="product" val="prod_a"/>
                        </val>
                </ditavalcontent>
        </body>
</ditaval>

I know the process of filtering is working because the topics are being
stripped out properly, but the HTML shows all the metadata being
generated

<html lang="en-us"><head>
<meta charset="UTF-8"></meta>
<meta name="copyright" content="(C) Copyright 2020"></meta>
<meta name="DC.rights.owner" content="(C) Copyright 2020"></meta>
<meta name="DC.type" content="concept"></meta>
<meta name="description" content=""></meta>
<meta name="bundle" content="FormatProdAC"></meta>
<meta name="bundle" content="FormatProdBC"></meta>
<meta name="bundle" content="Formatcommon"></meta>
<meta name="bundle" content="FormatProdB"></meta>
<meta name="DC.format" content="HTML5"></meta>
<meta name="DC.identifier" content="tpu1603147966773"></meta><meta
name="DC.language"

The bundle value controls how Zoomin manages my content. I'm generating
5 different versions and Zoomin uses this to identify if the content is
new or replaces something on the site.

In writing this up, I'm looking at a topic from each bundle and I'm
seeing different combinations of the values being written out

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdB"></meta>
        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdB"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdA"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdA"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdB"></meta>

I modified my DITAVAL file to remove the other labels

<ditaval id="dyr1599584459162" xml:lang="en-us">
        <title>FORMAT Prod A incluude Prod B and Prod C exclude</title>
        <shortdesc/>
        <body>
                <ditavalcontent>


                        <val>
                                <prop action="exclude" att="product" val="prod_c"/>
                                <prop action="exclude" att="product" val="prod_b"/>
                                <prop action="include" att="product" val="prod_a"/>

                                <prop action="exclude" att="product" val="prod_common"/>
                                <prop action="exclude" att="product" val="prod_bc"/>
                                <prop action="exclude" att="product" val="prod_ac"/>


                        </val>
                </ditavalcontent>
        </body>
</ditaval>

But that didn't change my results.

Any idea what I'm missing?

..ddan






Melissa Kershes
 

I dropped the code to do that into the conductor file as part of the target so it gets called whenever the transform is run, from a build manifest to a regular “generate output” option by a user.

 

Hope this helps a bit!

Melissa

 

From: main@dita-users.groups.io <main@dita-users.groups.io> On Behalf Of Dan Vint
Sent: Wednesday, October 21, 2020 9:23 AM
To: main@dita-users.groups.io
Cc: dvint@...
Subject: Re: [dita-users] filtering <othermeta>

 

I'll check that out. I'm using a build manifest to generate these all at one time and they don't demonstrate that functionality.

 

 

 

Sent from my Verizon, Samsung Galaxy smartphone

 

 

-------- Original message --------

From: Melissa Kershes <sarala557@...>

Date: 10/20/20 4:40 PM (GMT-08:00)

Subject: Re: [dita-users] filtering <othermeta>

 

Hey Danny. 

 

When I was doing this the bundle name was generated as part of the transform so I used that to make sure I had uniqueness when it was needed.  

 

The IXIASoft CCMS renames the ditaval file to the map id when it is exported for processing.  Since the bundle name is generally the mapid_ditavalID i added a value in the middle of the bundle name based on vrm. You could use your ditaval values to differentiate the bundle name.  

 

Melissa

 

On Tue, Oct 20, 2020, 7:34 PM Dan Vint <dvint@...> wrote:

I checked the spec and othermeta supports/allows filtering with the
@product attribute. I'm running the HTML transformation and it seems
like the OT is not processing these elements. I have this map

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE map PUBLIC "-//PINGIDENTITY//DTD DITA Map//EN"
"PingIdentityMap.dtd">
<map id="kmd1603213063098" xml:lang="en-us">
        <title>FORMAT: Single map to use DITAVALS at build time - build
manifest
                <ph product="prod_b">Product B</ph>
                <ph product="prod_c">Product C</ph>
                <ph product="prod_a">Product A</ph></title>
        <topicmeta>
                <othermeta content="FormatProdA" name="bundle" product="prod_a"/>
                <othermeta content="FormatProdB" name="bundle" product="prod_b"/>
                <othermeta content="Formatcommon" name="bundle"
product="prod_common"/>
                <othermeta content="FormatProdBC" name="bundle" product="prod_bc"/>
                <othermeta content="FormatProdAC" name="bundle" product="prod_ac"/>

        </topicmeta>
        <containerref href="eek1572622465806.ditamap"/>

        <topicref keyref="vln1599578426163"/>
        <!-- topic with ditavals -->
        <topicref keyref="sfq1599578470970" product="prod_a"/>
        <!-- topic product A -->
        <topicref keyref="wkc1599578503581" product="prod_b"/>
        <!-- topic product B -->
        <topicref keyref="vva1599578551353"/>
        <!-- topic all -->
        <topicref keyref="tpu1603147966773" product="prod_c"/>
        <!-- topic product C -->

        <topicref keyref="vln1599578426163" product="prod_c prod_b"/>
        <!-- topic with ditavals for Prod B and C-->
</map>

And for instance this DITAVAL file

<ditaval id="dyr1599584459162" xml:lang="en-us">
        <title>FORMAT Prod A include Prod B and Prod C exclude</title>
        <shortdesc/>
        <body>
                <ditavalcontent>
                        <val>
                                <prop action="exclude" att="product" val="prod_c"/>
                                <prop action="exclude" att="product" val="prod_b"/>
                                <prop action="include" att="product" val="prod_a"/>
                        </val>
                </ditavalcontent>
        </body>
</ditaval>

I know the process of filtering is working because the topics are being
stripped out properly, but the HTML shows all the metadata being
generated

<html lang="en-us"><head>
<meta charset="UTF-8"></meta>
<meta name="copyright" content="(C) Copyright 2020"></meta>
<meta name="DC.rights.owner" content="(C) Copyright 2020"></meta>
<meta name="DC.type" content="concept"></meta>
<meta name="description" content=""></meta>
<meta name="bundle" content="FormatProdAC"></meta>
<meta name="bundle" content="FormatProdBC"></meta>
<meta name="bundle" content="Formatcommon"></meta>
<meta name="bundle" content="FormatProdB"></meta>
<meta name="DC.format" content="HTML5"></meta>
<meta name="DC.identifier" content="tpu1603147966773"></meta><meta
name="DC.language"

The bundle value controls how Zoomin manages my content. I'm generating
5 different versions and Zoomin uses this to identify if the content is
new or replaces something on the site.

In writing this up, I'm looking at a topic from each bundle and I'm
seeing different combinations of the values being written out

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdB"></meta>
        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdB"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdA"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdA"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdB"></meta>

I modified my DITAVAL file to remove the other labels

<ditaval id="dyr1599584459162" xml:lang="en-us">
        <title>FORMAT Prod A incluude Prod B and Prod C exclude</title>
        <shortdesc/>
        <body>
                <ditavalcontent>


                        <val>
                                <prop action="exclude" att="product" val="prod_c"/>
                                <prop action="exclude" att="product" val="prod_b"/>
                                <prop action="include" att="product" val="prod_a"/>

                                <prop action="exclude" att="product" val="prod_common"/>
                                <prop action="exclude" att="product" val="prod_bc"/>
                                <prop action="exclude" att="product" val="prod_ac"/>


                        </val>
                </ditavalcontent>
        </body>
</ditaval>

But that didn't change my results.

Any idea what I'm missing?

..ddan





Jay Sadler
 

Ixiasoft also can give you a custom ant task to copy the original (Ixiasoft) name of the ditaval instead of a ditaval file based on the source ditamap name. Create a target in your conductor to use this custom task if you need a copy in your output.


From: main@dita-users.groups.io <main@dita-users.groups.io> on behalf of Melissa Kershes via groups.io <sarala557@...>
Sent: Wednesday, October 21, 2020 6:27
To: main@dita-users.groups.io <main@dita-users.groups.io>
Subject: Re: [dita-users] filtering <othermeta>
 
[External Email]

I dropped the code to do that into the conductor file as part of the target so it gets called whenever the transform is run, from a build manifest to a regular “generate output” option by a user.

 

Hope this helps a bit!

Melissa

 

From: main@dita-users.groups.io <main@dita-users.groups.io> On Behalf Of Dan Vint
Sent: Wednesday, October 21, 2020 9:23 AM
To: main@dita-users.groups.io
Cc: dvint@...
Subject: Re: [dita-users] filtering <othermeta>

 

I'll check that out. I'm using a build manifest to generate these all at one time and they don't demonstrate that functionality.

 

 

 

Sent from my Verizon, Samsung Galaxy smartphone

 

 

-------- Original message --------

From: Melissa Kershes <sarala557@...>

Date: 10/20/20 4:40 PM (GMT-08:00)

Subject: Re: [dita-users] filtering <othermeta>

 

Hey Danny. 

 

When I was doing this the bundle name was generated as part of the transform so I used that to make sure I had uniqueness when it was needed.  

 

The IXIASoft CCMS renames the ditaval file to the map id when it is exported for processing.  Since the bundle name is generally the mapid_ditavalID i added a value in the middle of the bundle name based on vrm. You could use your ditaval values to differentiate the bundle name.  

 

Melissa

 

On Tue, Oct 20, 2020, 7:34 PM Dan Vint <dvint@...> wrote:

I checked the spec and othermeta supports/allows filtering with the
@product attribute. I'm running the HTML transformation and it seems
like the OT is not processing these elements. I have this map

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE map PUBLIC "-//PINGIDENTITY//DTD DITA Map//EN"
"PingIdentityMap.dtd">
<map id="kmd1603213063098" xml:lang="en-us">
        <title>FORMAT: Single map to use DITAVALS at build time - build
manifest
                <ph product="prod_b">Product B</ph>
                <ph product="prod_c">Product C</ph>
                <ph product="prod_a">Product A</ph></title>
        <topicmeta>
                <othermeta content="FormatProdA" name="bundle" product="prod_a"/>
                <othermeta content="FormatProdB" name="bundle" product="prod_b"/>
                <othermeta content="Formatcommon" name="bundle"
product="prod_common"/>
                <othermeta content="FormatProdBC" name="bundle" product="prod_bc"/>
                <othermeta content="FormatProdAC" name="bundle" product="prod_ac"/>

        </topicmeta>
        <containerref href="eek1572622465806.ditamap"/>

        <topicref keyref="vln1599578426163"/>
        <!-- topic with ditavals -->
        <topicref keyref="sfq1599578470970" product="prod_a"/>
        <!-- topic product A -->
        <topicref keyref="wkc1599578503581" product="prod_b"/>
        <!-- topic product B -->
        <topicref keyref="vva1599578551353"/>
        <!-- topic all -->
        <topicref keyref="tpu1603147966773" product="prod_c"/>
        <!-- topic product C -->

        <topicref keyref="vln1599578426163" product="prod_c prod_b"/>
        <!-- topic with ditavals for Prod B and C-->
</map>

And for instance this DITAVAL file

<ditaval id="dyr1599584459162" xml:lang="en-us">
        <title>FORMAT Prod A include Prod B and Prod C exclude</title>
        <shortdesc/>
        <body>
                <ditavalcontent>
                        <val>
                                <prop action="exclude" att="product" val="prod_c"/>
                                <prop action="exclude" att="product" val="prod_b"/>
                                <prop action="include" att="product" val="prod_a"/>
                        </val>
                </ditavalcontent>
        </body>
</ditaval>

I know the process of filtering is working because the topics are being
stripped out properly, but the HTML shows all the metadata being
generated

<html lang="en-us"><head>
<meta charset="UTF-8"></meta>
<meta name="copyright" content="(C) Copyright 2020"></meta>
<meta name="DC.rights.owner" content="(C) Copyright 2020"></meta>
<meta name="DC.type" content="concept"></meta>
<meta name="description" content=""></meta>
<meta name="bundle" content="FormatProdAC"></meta>
<meta name="bundle" content="FormatProdBC"></meta>
<meta name="bundle" content="Formatcommon"></meta>
<meta name="bundle" content="FormatProdB"></meta>
<meta name="DC.format" content="HTML5"></meta>
<meta name="DC.identifier" content="tpu1603147966773"></meta><meta
name="DC.language"

The bundle value controls how Zoomin manages my content. I'm generating
5 different versions and Zoomin uses this to identify if the content is
new or replaces something on the site.

In writing this up, I'm looking at a topic from each bundle and I'm
seeing different combinations of the values being written out

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdB"></meta>
        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdB"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdA"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdA"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdB"></meta>

I modified my DITAVAL file to remove the other labels

<ditaval id="dyr1599584459162" xml:lang="en-us">
        <title>FORMAT Prod A incluude Prod B and Prod C exclude</title>
        <shortdesc/>
        <body>
                <ditavalcontent>


                        <val>
                                <prop action="exclude" att="product" val="prod_c"/>
                                <prop action="exclude" att="product" val="prod_b"/>
                                <prop action="include" att="product" val="prod_a"/>

                                <prop action="exclude" att="product" val="prod_common"/>
                                <prop action="exclude" att="product" val="prod_bc"/>
                                <prop action="exclude" att="product" val="prod_ac"/>


                        </val>
                </ditavalcontent>
        </body>
</ditaval>

But that didn't change my results.

Any idea what I'm missing?

..ddan





Dan Vint
 

Thanks for alternative ideas, but I'm really trying to understand why I'm not getting the correct result with the markup. Seems to me there is only one value that should appear, but I'm getting multiples in the content. 

Initially I read Melissa's response as being something that happens out of the box and didn't realize she was talking about a customization. I typically don't use build manifests, so I thought it might be something different in the two approaches. 



Sent from my Verizon, Samsung Galaxy smartphone


-------- Original message --------
From: Jay Sadler <jay.sadler@...>
Date: 10/22/20 11:53 AM (GMT-08:00)
To: "Melissa Kershes via groups.io" <sarala557@...>, main@dita-users.groups.io
Subject: Re: [dita-users] filtering <othermeta>

Ixiasoft also can give you a custom ant task to copy the original (Ixiasoft) name of the ditaval instead of a ditaval file based on the source ditamap name. Create a target in your conductor to use this custom task if you need a copy in your output.

From: main@dita-users.groups.io <main@dita-users.groups.io> on behalf of Melissa Kershes via groups.io <sarala557@...>
Sent: Wednesday, October 21, 2020 6:27
To: main@dita-users.groups.io <main@dita-users.groups.io>
Subject: Re: [dita-users] filtering <othermeta>
 
[External Email]

I dropped the code to do that into the conductor file as part of the target so it gets called whenever the transform is run, from a build manifest to a regular “generate output” option by a user.

 

Hope this helps a bit!

Melissa

 

From: main@dita-users.groups.io <main@dita-users.groups.io> On Behalf Of Dan Vint
Sent: Wednesday, October 21, 2020 9:23 AM
To: main@dita-users.groups.io
Cc: dvint@...
Subject: Re: [dita-users] filtering <othermeta>

 

I'll check that out. I'm using a build manifest to generate these all at one time and they don't demonstrate that functionality.

 

 

 

Sent from my Verizon, Samsung Galaxy smartphone

 

 

-------- Original message --------

From: Melissa Kershes <sarala557@...>

Date: 10/20/20 4:40 PM (GMT-08:00)

Subject: Re: [dita-users] filtering <othermeta>

 

Hey Danny. 

 

When I was doing this the bundle name was generated as part of the transform so I used that to make sure I had uniqueness when it was needed.  

 

The IXIASoft CCMS renames the ditaval file to the map id when it is exported for processing.  Since the bundle name is generally the mapid_ditavalID i added a value in the middle of the bundle name based on vrm. You could use your ditaval values to differentiate the bundle name.  

 

Melissa

 

On Tue, Oct 20, 2020, 7:34 PM Dan Vint <dvint@...> wrote:

I checked the spec and othermeta supports/allows filtering with the
@product attribute. I'm running the HTML transformation and it seems
like the OT is not processing these elements. I have this map

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE map PUBLIC "-//PINGIDENTITY//DTD DITA Map//EN"
"PingIdentityMap.dtd">
<map id="kmd1603213063098" xml:lang="en-us">
        <title>FORMAT: Single map to use DITAVALS at build time - build
manifest
                <ph product="prod_b">Product B</ph>
                <ph product="prod_c">Product C</ph>
                <ph product="prod_a">Product A</ph></title>
        <topicmeta>
                <othermeta content="FormatProdA" name="bundle" product="prod_a"/>
                <othermeta content="FormatProdB" name="bundle" product="prod_b"/>
                <othermeta content="Formatcommon" name="bundle"
product="prod_common"/>
                <othermeta content="FormatProdBC" name="bundle" product="prod_bc"/>
                <othermeta content="FormatProdAC" name="bundle" product="prod_ac"/>

        </topicmeta>
        <containerref href="eek1572622465806.ditamap"/>

        <topicref keyref="vln1599578426163"/>
        <!-- topic with ditavals -->
        <topicref keyref="sfq1599578470970" product="prod_a"/>
        <!-- topic product A -->
        <topicref keyref="wkc1599578503581" product="prod_b"/>
        <!-- topic product B -->
        <topicref keyref="vva1599578551353"/>
        <!-- topic all -->
        <topicref keyref="tpu1603147966773" product="prod_c"/>
        <!-- topic product C -->

        <topicref keyref="vln1599578426163" product="prod_c prod_b"/>
        <!-- topic with ditavals for Prod B and C-->
</map>

And for instance this DITAVAL file

<ditaval id="dyr1599584459162" xml:lang="en-us">
        <title>FORMAT Prod A include Prod B and Prod C exclude</title>
        <shortdesc/>
        <body>
                <ditavalcontent>
                        <val>
                                <prop action="exclude" att="product" val="prod_c"/>
                                <prop action="exclude" att="product" val="prod_b"/>
                                <prop action="include" att="product" val="prod_a"/>
                        </val>
                </ditavalcontent>
        </body>
</ditaval>

I know the process of filtering is working because the topics are being
stripped out properly, but the HTML shows all the metadata being
generated

<html lang="en-us"><head>
<meta charset="UTF-8"></meta>
<meta name="copyright" content="(C) Copyright 2020"></meta>
<meta name="DC.rights.owner" content="(C) Copyright 2020"></meta>
<meta name="DC.type" content="concept"></meta>
<meta name="description" content=""></meta>
<meta name="bundle" content="FormatProdAC"></meta>
<meta name="bundle" content="FormatProdBC"></meta>
<meta name="bundle" content="Formatcommon"></meta>
<meta name="bundle" content="FormatProdB"></meta>
<meta name="DC.format" content="HTML5"></meta>
<meta name="DC.identifier" content="tpu1603147966773"></meta><meta
name="DC.language"

The bundle value controls how Zoomin manages my content. I'm generating
5 different versions and Zoomin uses this to identify if the content is
new or replaces something on the site.

In writing this up, I'm looking at a topic from each bundle and I'm
seeing different combinations of the values being written out

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdB"></meta>
        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdB"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdA"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdA"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdB"></meta>

I modified my DITAVAL file to remove the other labels

<ditaval id="dyr1599584459162" xml:lang="en-us">
        <title>FORMAT Prod A incluude Prod B and Prod C exclude</title>
        <shortdesc/>
        <body>
                <ditavalcontent>


                        <val>
                                <prop action="exclude" att="product" val="prod_c"/>
                                <prop action="exclude" att="product" val="prod_b"/>
                                <prop action="include" att="product" val="prod_a"/>

                                <prop action="exclude" att="product" val="prod_common"/>
                                <prop action="exclude" att="product" val="prod_bc"/>
                                <prop action="exclude" att="product" val="prod_ac"/>


                        </val>
                </ditavalcontent>
        </body>
</ditaval>

But that didn't change my results.

Any idea what I'm missing?

..ddan





Dan Vint
 

I just looked at my last test and I'm getting only single values. Something else is going on and I need to review the set of ditaval files.

Thanks



Sent from my Verizon, Samsung Galaxy smartphone


-------- Original message --------
From: dvint <dvint@...>
Date: 10/22/20 12:16 PM (GMT-08:00)
To: main@dita-users.groups.io, "Melissa Kershes via groups.io" <sarala557@...>
Cc: dvint@...
Subject: Re: [dita-users] filtering <othermeta>

Thanks for alternative ideas, but I'm really trying to understand why I'm not getting the correct result with the markup. Seems to me there is only one value that should appear, but I'm getting multiples in the content. 

Initially I read Melissa's response as being something that happens out of the box and didn't realize she was talking about a customization. I typically don't use build manifests, so I thought it might be something different in the two approaches. 



Sent from my Verizon, Samsung Galaxy smartphone


-------- Original message --------
From: Jay Sadler <jay.sadler@...>
Date: 10/22/20 11:53 AM (GMT-08:00)
To: "Melissa Kershes via groups.io" <sarala557@...>, main@dita-users.groups.io
Subject: Re: [dita-users] filtering <othermeta>

Ixiasoft also can give you a custom ant task to copy the original (Ixiasoft) name of the ditaval instead of a ditaval file based on the source ditamap name. Create a target in your conductor to use this custom task if you need a copy in your output.

From: main@dita-users.groups.io <main@dita-users.groups.io> on behalf of Melissa Kershes via groups.io <sarala557@...>
Sent: Wednesday, October 21, 2020 6:27
To: main@dita-users.groups.io <main@dita-users.groups.io>
Subject: Re: [dita-users] filtering <othermeta>
 
[External Email]

I dropped the code to do that into the conductor file as part of the target so it gets called whenever the transform is run, from a build manifest to a regular “generate output” option by a user.

 

Hope this helps a bit!

Melissa

 

From: main@dita-users.groups.io <main@dita-users.groups.io> On Behalf Of Dan Vint
Sent: Wednesday, October 21, 2020 9:23 AM
To: main@dita-users.groups.io
Cc: dvint@...
Subject: Re: [dita-users] filtering <othermeta>

 

I'll check that out. I'm using a build manifest to generate these all at one time and they don't demonstrate that functionality.

 

 

 

Sent from my Verizon, Samsung Galaxy smartphone

 

 

-------- Original message --------

From: Melissa Kershes <sarala557@...>

Date: 10/20/20 4:40 PM (GMT-08:00)

Subject: Re: [dita-users] filtering <othermeta>

 

Hey Danny. 

 

When I was doing this the bundle name was generated as part of the transform so I used that to make sure I had uniqueness when it was needed.  

 

The IXIASoft CCMS renames the ditaval file to the map id when it is exported for processing.  Since the bundle name is generally the mapid_ditavalID i added a value in the middle of the bundle name based on vrm. You could use your ditaval values to differentiate the bundle name.  

 

Melissa

 

On Tue, Oct 20, 2020, 7:34 PM Dan Vint <dvint@...> wrote:

I checked the spec and othermeta supports/allows filtering with the
@product attribute. I'm running the HTML transformation and it seems
like the OT is not processing these elements. I have this map

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE map PUBLIC "-//PINGIDENTITY//DTD DITA Map//EN"
"PingIdentityMap.dtd">
<map id="kmd1603213063098" xml:lang="en-us">
        <title>FORMAT: Single map to use DITAVALS at build time - build
manifest
                <ph product="prod_b">Product B</ph>
                <ph product="prod_c">Product C</ph>
                <ph product="prod_a">Product A</ph></title>
        <topicmeta>
                <othermeta content="FormatProdA" name="bundle" product="prod_a"/>
                <othermeta content="FormatProdB" name="bundle" product="prod_b"/>
                <othermeta content="Formatcommon" name="bundle"
product="prod_common"/>
                <othermeta content="FormatProdBC" name="bundle" product="prod_bc"/>
                <othermeta content="FormatProdAC" name="bundle" product="prod_ac"/>

        </topicmeta>
        <containerref href="eek1572622465806.ditamap"/>

        <topicref keyref="vln1599578426163"/>
        <!-- topic with ditavals -->
        <topicref keyref="sfq1599578470970" product="prod_a"/>
        <!-- topic product A -->
        <topicref keyref="wkc1599578503581" product="prod_b"/>
        <!-- topic product B -->
        <topicref keyref="vva1599578551353"/>
        <!-- topic all -->
        <topicref keyref="tpu1603147966773" product="prod_c"/>
        <!-- topic product C -->

        <topicref keyref="vln1599578426163" product="prod_c prod_b"/>
        <!-- topic with ditavals for Prod B and C-->
</map>

And for instance this DITAVAL file

<ditaval id="dyr1599584459162" xml:lang="en-us">
        <title>FORMAT Prod A include Prod B and Prod C exclude</title>
        <shortdesc/>
        <body>
                <ditavalcontent>
                        <val>
                                <prop action="exclude" att="product" val="prod_c"/>
                                <prop action="exclude" att="product" val="prod_b"/>
                                <prop action="include" att="product" val="prod_a"/>
                        </val>
                </ditavalcontent>
        </body>
</ditaval>

I know the process of filtering is working because the topics are being
stripped out properly, but the HTML shows all the metadata being
generated

<html lang="en-us"><head>
<meta charset="UTF-8"></meta>
<meta name="copyright" content="(C) Copyright 2020"></meta>
<meta name="DC.rights.owner" content="(C) Copyright 2020"></meta>
<meta name="DC.type" content="concept"></meta>
<meta name="description" content=""></meta>
<meta name="bundle" content="FormatProdAC"></meta>
<meta name="bundle" content="FormatProdBC"></meta>
<meta name="bundle" content="Formatcommon"></meta>
<meta name="bundle" content="FormatProdB"></meta>
<meta name="DC.format" content="HTML5"></meta>
<meta name="DC.identifier" content="tpu1603147966773"></meta><meta
name="DC.language"

The bundle value controls how Zoomin manages my content. I'm generating
5 different versions and Zoomin uses this to identify if the content is
new or replaces something on the site.

In writing this up, I'm looking at a topic from each bundle and I'm
seeing different combinations of the values being written out

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdB"></meta>
        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdB"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdA"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdA"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdB"></meta>

I modified my DITAVAL file to remove the other labels

<ditaval id="dyr1599584459162" xml:lang="en-us">
        <title>FORMAT Prod A incluude Prod B and Prod C exclude</title>
        <shortdesc/>
        <body>
                <ditavalcontent>


                        <val>
                                <prop action="exclude" att="product" val="prod_c"/>
                                <prop action="exclude" att="product" val="prod_b"/>
                                <prop action="include" att="product" val="prod_a"/>

                                <prop action="exclude" att="product" val="prod_common"/>
                                <prop action="exclude" att="product" val="prod_bc"/>
                                <prop action="exclude" att="product" val="prod_ac"/>


                        </val>
                </ditavalcontent>
        </body>
</ditaval>

But that didn't change my results.

Any idea what I'm missing?

..ddan