nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

using MetaTagger for search engines

rishi

We currently have iPhrase as our search engine and it spiders the actual website.
We are considering using MetaTagger primarily to assist in searches.

My question is if a search engine can do an efficient job of going through a web page and creating its indices, why do we need MetaTagger? Our iPhrase expert's recommendation was to have a max of 3 or 4 keywords else search results can get messed up.

I do see a few advantages of MetaTagger
--> Specifically tagging pages(as EAs) which do not appear in searches (e.g.pages with less content).
--> Tagging non-supported content(but iPhrase supports PDF, Word so this may not matter)
--> Adding meta information to a file to be used for other purposes (tracking,etc).
--> Classification, Summarizer (if you want to use it)
--> Building internal (within Teamsite) searches
--> Updating a search engine database

But they do not seem so relevant to our situation.
I would be interested in hearing if anyone had similar thoughts\experience and about the application of MetaTagger in our situation.

Find more posts tagged with

Comments

Migrateduser

One of the key elements in integrating iphrase and TeamSite is to use the Interwoven Connector for iPhrase. This enables you to do several things:
- Index the latest Edition of TeamSite content and metadata for complete and up-to-date content exposure
- Import key concepts and synonyms from MetaTagger vocabularies and taxonomies for much improved results.
- Perhaps most importantly, ou leverage MetaTagger content categorization to display well-organized results that users can easily act upon and finally.
- Finally, it integrates with the Interwoven workflow, eliminating any need to modify the existing processes and tools used by your content creators.

I m interested in your use case - can you tell me a little bit more about your plans?

rishi

I am aware of the Interwoven Connector for iPhrase as our intranet site is using this.

For our public website, we are thus comparing 2 iPhrase implementations :-
1) iPhrase spiders the backing store and uses the EAs to build its indices.

2) iPhrase spiders the website(goes through content in pages) and build its indices(weekly) - current implementation.
For 2, The search is controlled through various configuration files (keywords,etc) maintained by the iPhrase Technical group. This includes content categorization, though controlled by the IS team.

I understand MetaTagger will give content creators control over the searches (this is not really a requirement)
and more current and maybe improved search results.

However in the current iPhrase implementation, there are no issues which are major enough to make such a big
architecture change(move from 2 to 1).
Hence, we will probably not use MetaTagger.