Why is my topic metadata merging with my map metadata during preprocessing?
Posted: Wed Nov 24, 2021 8:33 pm
Hi,
I am trying to troubleshoot an unexpected value coming from preprocessing. On debugging topicpullImpl.xsl it appears that the text values from the <map<topicmeta> elements are somehow merging with those from
<reference><prolog><metadata> elements
where the reference is one of the children of the map that is linked to from another child topic of the map.
When I look at the value forin a customization of topicpullImpl.xsl
I am seeing text value from the parent map
<map><topicmeta><publisher>
merged with attribute values from
<reference><prolog><metadata><othermeta>
from the $targetElement variable
Apologies if I am not explaining this very well.
I would appreciate any direction anyone might be able to provide on this as I am baffled.
Thanks in advance,
Ann
I am trying to troubleshoot an unexpected value coming from preprocessing. On debugging topicpullImpl.xsl it appears that the text values from the <map<topicmeta> elements are somehow merging with those from
<reference><prolog><metadata> elements
where the reference is one of the children of the map that is linked to from another child topic of the map.
When I look at the value for
Code: Select all
<xsl:value-of select="$targetElement//*[contains(@class, ' topic/prolog ')]/*[contains(@class, ' topic/metadata ')]/*[contains(@class , ' topic/othermeta ')][@name='category']/@content"/>
I am seeing text value from the parent map
<map><topicmeta><publisher>
merged with attribute values from
<reference><prolog><metadata><othermeta>
from the $targetElement variable
Apologies if I am not explaining this very well.
I would appreciate any direction anyone might be able to provide on this as I am baffled.
Thanks in advance,
Ann