Cluster Documents from Different Sources - Fluid Topics - 3.10 - Technical Notes

Empower Metadata with Fluid Topics

Fluid Topics
Fluid Topics Version
Technical Notes
Target Audience

It is possible to manually assign any value to ft:clusterId metadata key on the condition that this value is the same for all the documents to be clustered.

The ft:clusterId metadata element is case-sensitive. If case does not match, the cluster will not work.

The following example shows how to set the value for the ft:clusterId metadata key in order to cluster the Time Machine Price List Ftmap, the Time Machine v2.0 Technical Datasheet DITA map and the Product Leaflet image.

  1. Add the ft:clusterId metadata key with the value Foo to the Ftmap in an ft:meta element as follows:

    <?xml version="1.0" encoding="UTF-8"?>
    <ft:map ft:editorialType="book" ft:lang="en-US" ft:originID="time_machine_price_list" ft:title="time Machine Price List" xmlns:ft="">
    <ft:rights accessLevel="public" />
    <ft:metas> <ft:meta key="Category">Leaflet</ft:meta>
    <ft:meta key="ft:clusterId">Foo</ft:meta> </ft:metas>
    <ft:node ft:title="Time Machine v1.0" href="time_machine_1_0.html" ft:originID="time_machine_1_0"/>
    <ft:node ft:title="Time Machine v2.0" href="time_machine_2_0.html" ft:originID="time_machine_2_0"/>

  2. Add the ft:clusterId metadata key with the value Foo to the DITA map in a bookmeta element as follows:

    <?xml version=”1.0” encoding=”UTF-8”?>
    <!DOCTYPE bookmap PUBLIC “-//OASIS//DTD DITA BookMap//EN” “bookmap.dtd”>
    <mainbooktitle>Time Machine v2.0 - Technical Datasheet</mainbooktitle>
    <othermeta name="Category” content=”Leaflet”/>
    <othermeta name=”ft:clusterId” content=”Foo”/>
    <topicref href=”features.dita” otherprops="novice, expert"/>
    <topicref href="dimensions.dita" otherprops="expert"/>

  3. Add the ft:clusterId metadata key with the value Foo to the control file of the Unstructured Document in an ft:facet element as follows:

    <?xml version=”1.0” encoding=”UTF-8”?>
    <ft:resources xmlns:ft=”” xmlns:xsi=”” xsi:schemaLocation=””>
    <ft:resource xml:lang=”en-US” id=”product_leaflet_1_0” status=”visible”>
    <ft:dispName>Time Machine v1.0</ft:dispName>
    <ft:facet name=”Category”>Leaflet</ft:facet>
    <ft:facet name=”ft:clusterId”>Foo</ft:facet>

  4. Upload the Ftmap, the DITA map, and the unstructured document with its control file in separate ZIP archives through the appropriate sources.

Once uploaded, Fluid Topics clusters the three documents in a variant drawer, where they appear in alphabetical order. If several variants are available for one of the clustered documents, filters appear in the variant drawer to let the use refine their search.