Dynamic Navigation based upon Entitiy Recognition using synonyms

2 views
Skip to first unread message

Michael Trumpler

unread,
Mar 26, 2013, 3:38:42 AM3/26/13
to Google-Search-...@googlegroups.com
We're trying to build dynamic navigation based upon entity recognition. This works fine basically. Now we'd like to group synonyms together using the following xml syntax for the list of entitties:

<?xml version="1.0"?>
<instances>
<instance>
  <name> Abwasser </name>
  <term> abwasser </term>
  <term> kläranlage </term>
  <term> kläranlagen </term>
  <store_term_or_name> name </store_term_or_name>
</instance>
...
</instances>

This doesn't seem to work - the dynamic navigation lists names and terms.

Has anybody worked out a smiliar scenario?

Michael

Jeremy Garreau

unread,
Mar 26, 2013, 4:08:36 AM3/26/13
to Google-Search-...@googlegroups.com
Did you recrawl your content after changing your ER file definition ?

Your file seems to be fine, you need to check your result gsaEntity_YOURENTITYNAME metadata to check the value

Michael Trumpler

unread,
Mar 26, 2013, 6:47:09 AM3/26/13
to Google-Search-...@googlegroups.com
Yes we did recrawl the content. The result searching for kläranlage looks like this:

...
<PMT NM="gsaentity_Fachangebot" DN="Fachangebot" IR="0" T="0">
<PV V="Abwasser" L="" H="" C="187"/>
...
<PV V="Kläranlagen" L="" H="" C="69"/>
...
<PV V="Kläranlage" L="" H="" C="53"/>
...

What does function is that the results for the term "kläranlage" are shown under the name "Abwasser".
What we do not want is the apperance of the terms ("kläranlage", kläranlagen") themselves in the dynamic navigation.
Did we get this wrong - are the terms not excluded ?

Mathias Bierl

unread,
Mar 26, 2013, 6:48:51 AM3/26/13
to Google-Search-...@googlegroups.com
Did you encode the XML file for the entity recognition correctly ?
If not it can not find the special chars like ä and will not do its work

Michael Trumpler

unread,
Mar 26, 2013, 7:20:56 AM3/26/13
to Google-Search-...@googlegroups.com
The file is encoded using utf-8. I'm uploading the complete file.
fachangebot.xml

Mathias Bierl

unread,
Mar 26, 2013, 12:01:42 PM3/26/13
to Google-Search-...@googlegroups.com
Maybe the case is also a factor because in your example you use upper case at beginning in xml lower case

Floris Weegink

unread,
May 8, 2013, 9:16:47 AM5/8/13
to Google-Search-...@googlegroups.com
You should use a regexp catcher instead of term cather.
And in order to make it case insensative you should use a prefix like this

    <instance> 
<name>Abwasser</name> 
<pattern>(?i)abwasser</pattern>
<pattern>(?i)kläranlage</pattern>
<pattern>(?i)kläranlagen</pattern>
<store_regex_or_name> name </store_regex_or_name> 
</instance>

Please let me know if this works for you.

Best regards,
Floris Weegink | Incentro

Pablo Solera

unread,
May 9, 2013, 4:39:02 AM5/9/13
to Google-Search-...@googlegroups.com
Hi Floris, 

Great answer!
I didn't notice the regular expressions are always case sensitive.

Pablo

Michael Trumpler

unread,
May 16, 2013, 2:28:44 AM5/16/13
to Google-Search-...@googlegroups.com
Thanks for this useful info!
We recently did manage to get our dynamic navigation working.
The key to solve the issue was patience.
When testing the differnt configuration sets, we were to impatient.

Thanks for the support,
Michael
Reply all
Reply to author
Forward
0 new messages