This is with TS 6.7.1 SP1 on Linux.
We capture a number of metadata (on various file types, not on DCRs) attributes using the Tagger GUI. Using the FieldMapping.xml file I added some of these attributes to the Search GUI's metadata dropdown lists, which works just fine after restarting the search services.
In the Search's dropdowns the options are labeled like the metadata they are stored as, e.g. "TeamSite/Metadata/approver" etc.
Since this is not very user friendly, I want to use customized labels as dropdown options, in the above example something like "Approver".
According to the documentation for the GUI customization (ts671_sp1_custom_v01_en.pdf, pages 47ff and 155ff) this can be achieved by editing search_custom.xml (located at <iw-home>/local/config/lib/content_center/customer_src/etc/conf/customer).
So, I added the following to search_custom.xml:
<extended-attribute-list id="iw.search.attribute_list">
<extended-attribute id="custom.attribute.approver" label="custom.attribute.approver.label" resourceBundle="com.corp.custom.strings" />
</extended-attribute-list>
and created the file <iw-home>/local/config/lib/content_center/customer_src/src/com/corp/custom/strings.properties with the following line in it:
custom.attribute.approver.label=Approver
I expected the label "Approver" to show up in the Search GUI's dropdown list instead of "TeamSite/Metadata/approver", but it didn't.
Did I miss something or is this really not working?
(I was wondering how TS makes the connection between the Search GUI and the entry I made in the search_custom.xml file?)
