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; } } }

TS Search: FieldMapping not picking up Template

bturns · 2005-03-14T20:46:58+00:00

I have this entry in my Fieldmapping.xml file kphealthconnect/metrics /file_administration/Region Region …

bturns

I have this entry in my Fieldmapping.xml file

<template>

<templateType>kphealthconnect/metrics</templateType>
<templatingFields>
<templatingField>
<xpath>/file_administration/Region</xpath>
<fieldSpecification>
<fieldName>Region</fieldName>
<fieldType>string</fieldType>
<fieldStorage>zone:RegionName</fieldStorage>
</fieldSpecification>
</templatingField>
</templatingFields>
</template>

The search form makes this field available to search on. However, I am entering a value that I know exists to search on. Search returns no results on this entry.

Does anyone know of a good way to troubleshoot search. Are there any detailed log files? Is there anyway to determine why a particular search isn't working?

Does the above field look good?

Find more posts tagged with

Comments

iwovGraduate

Did you reindex anything after making this field searchable ? If not, try that.
You are using incremental updates ?

You must be using TS 6.5. Its always a good idea to mention TS version, SP/Patch level, OS, etc. eventhough it might be obvious.

iwovGraduate

See this thread: Metadata Search TS 6.5. Might be helpful.

bturns

Yes I reindexed after making the changes and stopped and started the search and index server.

We are on TS 6.5. Solaris 8.

iwovGraduate

Try this:

Modify a file (which you know should show up in search results) in workarea, submit it. Then, (possibly stop/start the services) reindex that branch. If you are using incremental updates it should automatically do it. Otherwise you'll use the CLT. Check the index log file. What does it say ?

bturns

Well this is really weird. I really don't know what I did different. Other than this time I made sure that the fieldName and fieldStorage values matched.

<fieldName>RegionName</fieldName>
<fieldStorage>zone:RegionName</fieldStorage>

I don't see why this would matter. I also did a reindexing and a restarted the index and search servers. I'm still figuring this out but it appears that when updating files and indexes there is a specific order that you have to perform the different functions:

- update config file (FieldMapping.xml)
- reindex content
- stop and start search and index server. (index before search)

I'm not sure what the order is but I will let you all know if I find anything.

bturns

Ok, I've discovered what the issues is. Basically what happens is when the index is created it uses the fieldmapping.xml file to catalog all the fields.

If the Fieldmapping.xml file is changed after the index is created then all the fields that were previously cataloged will no longer show up in the search because the search field has not changed. In order to be able to search on the new field name all the files need to be reindexed. This is seeming to be a pain because only changed files are reindexed. So if the FieldMapping.xml file is changed you've got to modify all your content so that it is reindexed. I guess the best approach would be to design all fields (in Fieldmapping.xml) prior to submitting and indexing your content.

Hope this helps.

Thanks,

Brian

Adam Stoller

I would think you could force a full re-indexing without having to modify and re-submit all your content.
It will still use a significant amout of CPU and memory to perform a full re-index - but you wouldn't have to muck with time-stamps on the files and whatever processes you may have in place for handling content submission.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

bturns

the only command that I would think would do that would be iwndxrefreshbr -b <branch_name>.

However, I tested it and it doesn't seem to do the whole branch. If you find something that does please let me know.

Adam Stoller

Hmm - you may want to open a case with Support regarding this...

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

iwovGraduate

I had a similar situation. What I did was removed the index directory for a branch which I wanted to reindex, and then reindexed the branch. I believe there is a CLT to actually remove it (prugebr or rmbr ?), but I just deleted the directory.

As mentioned earlier, this will spike up the CPU usage during the time its indexing the branch.

Adam Stoller

The only thing I see on quick perusal is iwndxrmbr - but the usage would seem to suggest that it's not as "destructive" as your method and therefore likely to not have the same effect:

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

iwovGraduate

Yes, as I am looking at this more carefully now, iwndxrmbr does not remove the collection..
However the usage of iwndxpurgebr CLT seems to imply that it DOES remove the collection.

Usage: iwndxpurgebr [-h|-v]
       iwndxpurgebr branchpath

Remove the collection associated with a branch from disk.
The branch is not indexed after the command is executed.

 -h            Display this usage information.
 -v            Display this command's version number.
  branchpath   Path of the branch to be purged.

I think that if you remove the collection, and then run iwndxrefreshbr, it will reindex the branch. From what I understand the iwndxrefreshbr will look at the last edition/version (this is not necessarily the edition number that we see in the UI but the one used internally) that was last indexed and compare it with the latest edition out there. Since it will not find the last edition indexed, it should reindex everything in staging area.

Disclaimer:
1. I have not tried this CLT.
2. The above description is my understanding of the CLT(s) - which could be wrong.

smenon

If you want to force a re-index without having to touch all of your files and re-submit, using the iwndxpurgebr is the way to do it. Once you have removed a collection, adding the branch to be indexed treats it like a new branch and it will re-index all the content essentially performing a baseline index of that branch. As fish points out, this will be memory and CPU intensive while it performs the baseline indexing and so you want to do this when there is little activity on the system - like maybe on a weekend.

--Sunil Menon
Product Manager
Interwoven, Inc.

Migrateduser

Why not try to delete the index collection using the iwndxpurgebr <branch>? After that use iwndxaddbr, I think it will re-index for you without having to resubmit all your content.

iwovGraduate

Yes, doing that should re-index the branch.
Thats exactly what was suggested earlier in the thread and confirmed by smenon.

calswiti

Hi;

Solaris 8
TS 6.5
We are also trying to get the search engine indexer to index attributes from several templates on our system and make them available for search.
I am not sure if the problem is with the xml fields setup in the FieldMapping.xml file OR the sequence of steps that I am taking to modify the mapping file and reindexing the branch in question. We have been able to index and search branch content using the advanced search form , Search Text and File attributes components, but when using the Content Type component --> the search fails to bring back results.

Here is the mapping that I have placed in FieldMapping.xml file for this template: As you can see, I have tried to express the xpath in different ways hoping that it would help. ( maybe I am way off on this :-( )
====================================================
<template>
<templateType>pss/pss_content</templateType>
<templatingFields>
<templatingField>
<xpath>//item[@name='Meta Data Description']</xpath>


<fieldSpecification>
<fieldName>pss_Description</fieldName>
<fieldType>string</fieldType>
<fieldStorage>zone Smiley Tongue

ss_Description</fieldStorage>
</fieldSpecification>
</templatingField>
</templatingFields>
</template>
=============================
Here is the template/xml file that we need indexed :
<record name="access_care_en_us_preview1" type="content">
<item name="Locale">
<value>en-US</value>
</item>
<item name="Deleted Status">
<value></value>
</item>
<item name="Online?">
<value>1</value>
</item>
<item name="Product or Service Name">
<value>32760</value>
</item>
<item name="Country">
<value>United States | English</value>
</item>
<item name="Preview">
<value>1</value>
</item>
<item name="Meta Data Description">
<value>Nortel Access Care OSS provides unified end-to-end management and diagnostics capability for next generation Voice over IP and traditional TDM networks.</value>
</item>
<item name="Meta Data Publish Date">
<value>02/22/2005</value>
</item>

Any help would be gratly appreciated.
Charlie

bturns

I can't tell for sure without seeing your datacapture.cfg. However, from the looks of this all you need in xpath is the following:

<xpath>/Meta Data Description</xpath>

If 'Meta Data Description' is at the first level (meaning it is not contained with in a container or a replicant) then you simply need to put the field between the xpath tags.

Also, remember if FieldMapping.xml is changed you after you've created an index then you will not be able to search on the new field until after the content has been reindexed.

Hope this helps.

Thanks,

BT