PS: Ignore if you are not interested in reading about stupidity of HP Autonomy. This is rant, not request for solution.
Hi,
I am using TeamSite 7.4.1 on Win 2K8 R2 with LSCSAuthouring and TS Search. OOTB fieldmappings in <iw-home>/Search/etc/fieldmappings/examples example are based on earlier version LSCS Authoring possbily 7.2.x or 7.3.1. Overall TeamSiteConnector is just another half baked module from HP Autonomy.
On enabling this fieldmappings example ContentFieldMappings for LiveSite content types in component-guide branch , they simply do not work due to following reasons,
Example field mapping,
<?xml version="1.0" encoding="UTF-8"?>
<Fields>
<Field name="ast_id" dataSource="extendedAttribute" pathToData="TeamSite/LiveSite/Id"/>
<Field name="ast_locale" dataSource="extendedAttribute" pathToData="TeamSite/Metadata/Locale"/>
<Field name="ast_branch" dataSource="extendedAttribute" pathToData="BranchVpath"/>
<Field name="ast_relative_path" dataSource="extendedAttribute" pathToData="AreaRelativePath"/>
<Field name="ast_creation_date" dataSource="extendedAttribute" pathToData="TeamSite/Metadata/CreationDate"/>
<Field name="ast_expiration_date" dataSource="extendedAttribute" pathToData="TeamSite/Metadata/ExpirationDate"/>
<Field name="ast_last_modified_date" dataSource="extendedAttribute" pathToData="LatestModifiedDate"/>
<Field name="cont_id" dataSource="extendedAttribute" pathToData="TeamSite/LiveSite/Id"/>
<Field name="cont_title" dataSource="Xpath" pathToData="Content/Title" xpathDataName="true"/>
<Field name="cont_summary" dataSource="Xpath" pathToData="Content/Summary" xpathDataName="true"/>
<Field name="img_content_id" dataSource="extendedAttribute" pathToData="TeamSite/LiveSite/Id"/>
<Field name="img_relative_path" dataSource="Xpath" pathToData="Content/Images//Image/RelativePath" xpathDataName="true"/>
<Field name="img_description" dataSource="Xpath" pathToData="Content/Images//Image/Description" xpathDataName="true"/>
<Field name="link_content_id" dataSource="extendedAttribute" pathToData="TeamSite/LiveSite/Id"/>
<Field name="link_label" dataSource="Xpath" pathToData="Content/Links//Link/Label" xpathDataName="true"/>
<Field name="link_type" dataSource="Xpath" pathToData="Content/Links//Link/Type" xpathDataName="true"/>
<Field name="link_target" dataSource="Xpath" pathToData="Content/Links//Link/Target" xpathDataName="true"/>
<Field name="auth_content_id" dataSource="extendedAttribute" pathToData="TeamSite/LiveSite/Id"/>
<Field name="auth_email" dataSource="Xpath" pathToData="Content/Authors//Author/Email" xpathDataName="true"/>
<Field name="auth_first_name" dataSource="Xpath" pathToData="Content/Authors//Author/FirstName" xpathDataName="true"/>
<Field name="auth_last_name" dataSource="Xpath" pathToData="Content/Authors//Author/LastName" xpathDataName="true"/>
<Field name="auth_phone" dataSource="Xpath" pathToData="Content/Authors//Author/Phone" xpathDataName="true"/>
<Field name="ctact_content_id" dataSource="extendedAttribute" pathToData="TeamSite/LiveSite/Id"/>
<Field name="ctact_first_name" dataSource="Xpath" pathToData="Content/Contacts//Contact/FirstName" xpathDataName="true"/>
<Field name="ctact_last_name" dataSource="Xpath" pathToData="Content/Contacts//Contact/LastName" xpathDataName="true"/>
<Field name="ctact_email" dataSource="Xpath" pathToData="Content/Contacts//Contact/Email" xpathDataName="true"/>
<Field name="ctact_phone" dataSource="Xpath" pathToData="Content/Contacts//Contact/Phone" xpathDataName="true"/>
<Field name="concat_content_id" dataSource="extendedAttribute" pathToData="TeamSite/LiveSite/Id"/>
<Field name="version" dataSource="extendedAttribute" pathToData="TeamSite/LiveSite/VersionInfo" deploy="false"/>
<Field name="deploymentAudit" dataSource="extendedAttribute" pathToData="TeamSite/LiveSite/DeploymentAudit" deploy="false"/>
<Field name="subjectMetadata" dataSource="extendedAttribute" pathToData="subjectMetadata0" deploy="false"/>
</Fields>
1. xpathDataName attribute which is very well understood by PLC Workflow + LSCS Authoring is completely ignored by TeamSiteConnector
2. When dataSource="Xpath" , pathToData is ignored instead , actual xpath of nodes within DCR needs to be mentioned in attribute "name". Like
<Field name="Content/Authors//Author/Email" dataSource="Xpath" />
3. It will finally read content from DCR and concat everything as single string stored in CONTENT_AUTHORS__AUTHOR_EMAIL
4. If you provide this field in attribute type map in FieldMappings.xml as,
<attributeTypeMap>
<attributeInfo name="Content/Authors//Author/Email" type="text"/>
</attributeTypeMap>
Concate string would be stored as TSIDX_LSCS_TXT_CONTENT_AUTHORS__AUTHOR_EMAIL. But it simply will not do what you are asking it to do i.e. store each email separately.
5. As topping to icing, you cannot fetch this fields using OOTB configuration of Ts Search + LSCS Auth , becuas these fields are not EAs. Hence you have to do backend IDOL query to find out if and how fieldmapping has worked out.
Ofcourse without mention, they have conveniently forgotten to document all this sadistic implementation.
This problem has existed for past 2 years in TS 7.4.1 and TS 7.4.1.2 Patch also continues fieldmappings with same useless implementation.
