Skip to main content.
home | support | download

Back to List Archive

How to disable XML indexing of the title field

From: Tref Gare <trefg(at)>
Date: Wed Jan 29 2003 - 23:42:14 GMT
Hi all,

I've got an xml indexing issue.

We've got a bunch of xml files which document events listed on a
website.  Each xml file includes multiple <title> fields for each event
appearing in the navigation as well as an <eventTitle> for the actual
hero event.

The issue is that swish-e seems to be indexing all the title fields by
default and therefore returning search hits for events that only appear
in the nav.  We want to index only the hero event data.

Is there some way for us to switch off the default indexing of the title
fields (if indeed this is the case).

A full example of one of our xml files is attached and our config file
as well.  Here below is a summarised version of one of the xml files.
In this example if we search for lion king, it is being returned because
lion king is present in the <navigation level="3">area.

<navigation level="3">
    <item><title><![CDATA[iron helmets, smoking guns]]></title>
    <item><title><![CDATA[the lion king]]></title>
    <navigation level="4"></navigation>
    <event version="1.0" 
        id="F551B3166E6E42AB" eventID="" ticketingEventID=""
        htmlLocation="" compoundType="activity stream">
            <oneLiner>Aance company Chunky Move.</oneLiner>
            <paragraph> he moves of an on-screen dancer. Come
            <dates>Friday 6 December 2002- Monday 27 January
            <times>Daily 10am</times>

Many thanks in advance.


Tref Gare
Development Consultant
Level 19/114 William St, Melbourne VIC 3000
phone: +61 3 9642 5553
fax: +61 3 9642 1335
"This email is intended only for the use of the individual or entity
named above and contains information that is confidential. No
confidentiality is waived or lost by any mis-transmission. If you
received this correspondence in error, please notify the sender and
immediately delete it from your system. You must not disclose, copy or
rely on any part of this correspondence if you are not the intended
recipient. Any communication directed to clients via this message is
subject to our Agreement and relevant Project Schedule. Any information
that is transmitted via email which may offend may have been sent
without knowledge or the consent of Areeba."

Due to deletion of content types excluded from this list by policy,
this multipart message was reduced to a single part, and from there
to a plain text message.
Received on Wed Jan 29 23:42:37 2003