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

Searching EA's, getting no results

kellyrmilligan

Solaris, TS 6.5

Here is my fieldmapping file:

<?xml version="1.0" encoding="UTF-8"?>
<searchFieldMapping xmlns="http://www.interwoven.com/products/teamsite/search/config/FieldMapping.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.interwoven.com/products/teamsite/search/config/FieldMapping.xsd FieldMapping.xsd">
<globalFields>

<extendedAttributeFields>
<fieldSpecification>
<fieldName>TeamSite/Metadata/BS_SYSTEM</fieldName>
<fieldType>string</fieldType>
<fieldStorage>zone Smiley Frustrated

ystem</fieldStorage>
</fieldSpecification>
<fieldSpecification>
<fieldName>TeamSite/Metadata/FSU</fieldName>
<fieldType>string</fieldType>
<fieldStorage>zone:fsu</fieldStorage>
</fieldSpecification>
<fieldSpecification>
<fieldName>TeamSite/Metadata/KEYWORDS</fieldName>
<fieldType>string</fieldType>
<fieldStorage>zone:keywords</fieldStorage>
</fieldSpecification>
<fieldSpecification>
<fieldName>TeamSite/Metadata/MT_PROCESS</fieldName>
<fieldType>string</fieldType>
<fieldStorage>zone Smiley Tongue

rocess</fieldStorage>
</fieldSpecification>
<fieldSpecification>
<fieldName>TeamSite/Metadata/MT_SUBJECT</fieldName>
<fieldType>string</fieldType>
<fieldStorage>zone:subject</fieldStorage>
</fieldSpecification>
</extendedAttributeFields>
</globalFields>
</searchFieldMapping>

The fields are coming up on the search page, but when I search for a value I know exists, it is not getting any results. any ideas?

Find more posts tagged with

Comments

mgal

is that file submitted to the staging area?

Thxs,

Mohammed Gazal.

nipper

more importantly are the EAs in the Staging are as well.

Search works on what has been submitted, even if it returns that pointers to the WA.

BTW, there is a FR to have search work locally in a WA

kellyrmilligan

Thanks for the responses, yes, the ea's are submitted in STAGING. I was looking at it some more, do the field names in FieldMapping.xml have match the field name in datacapture.cfg?

<fieldStorage>zone:BS_SYSTEM</fieldStorage>

and

<item name="BS_SYSTEM">

kellyrmilligan

Well, two of the five fields are searching correctly now, which is a good and bad thing..

Here is the revised FieldMapping.xml file:

<extendedAttributeFields>
<fieldSpecification>
<fieldName>TeamSite/Metadata/BS_SYSTEM</fieldName>
<fieldType>string</fieldType>
<fieldStorage>zone:BS_SYSTEM</fieldStorage>
</fieldSpecification>
<fieldSpecification>
<fieldName>TeamSite/Metadata/FSU</fieldName>
<fieldType>string</fieldType>
<fieldStorage>zone:FSU</fieldStorage>
</fieldSpecification>
<fieldSpecification>
<fieldName>TeamSite/Metadata/KEYWORDS</fieldName>
<fieldType>string</fieldType>
<fieldStorage>zone:KEYWORDS</fieldStorage>
</fieldSpecification>
<fieldSpecification>
<fieldName>TeamSite/Metadata/MT_PROCESS</fieldName>
<fieldType>string</fieldType>
<fieldStorage>zone:MT_PROCESS</fieldStorage>
</fieldSpecification>
<fieldSpecification>
<fieldName>TeamSite/Metadata/MT_SUBJECT</fieldName>
<fieldType>string</fieldType>
<fieldStorage>zone:MT_SUBJECT</fieldStorage>
</fieldSpecification>
</extendedAttributeFields>

and my datacapture.cfg fields:

<item name="MT_SUBJECT">
<description>Content Type</description>
<label>Subject</label>
<select required="f" multiple="t" size="5">
$options
</select>
</item>
<item name="MT_PROCESS">
<description>Content Type</description>
<label>Process</label>
<select required="t" multiple="t" size="5">
$options
</select>
</item>
<item name="BS_SYSTEM">
<description>Content Type</description>
<label>System</label>
<select required="n" multiple="t" size="5">
$options
</select>
</item>

These are working:

<item name="FSU">
<description>Content Type</description>
<label>HCSC Sites</label>
<select required="t" multiple="t" size="5">
$options
</select>
</item>
<item name="KEYWORDS">
<description>Enter Content for the Main Window of the Page</description>
<label>Keywords:</label>
<textarea rows="5" cols="25" rtf="t" required="f" wrap="physical"/>
</item>

These are populated with some perl, but the item names are the important things I think...of course the content can be the issue as well ,but fsu is identical to the ones that aren't working. The attributes are in staging. I have purged and rebuilt the index. regular search is working just fine. The only requirement is full metadata search.

Any ideas?

nipper

What type of files are you looking at ? This bug was *supposed* to be fixed in SP1 but it is still there,

57977 Content in text (.txt) documents (including files with .cpp, .c, or .html
extensions) which are not saved in UTF-8 encoding are not properly indexed and the
resulting content is not searchable.
Workaround: Save files of these types in UTF-8 encoding.

Don't know if EAs are affected by this or not.

kellyrmilligan

Only looking at DCRs, and search is working like a charm on them. We have some ea's that we are setting up for tagging, and the content is there, but 3 of the fields mentioned before are not searchable, not sure why. Is what appears on the GUI when you click on properties the same as what is searched?

kellyrmilligan

Not sure why it is working now, I started from scratch, and after every field I stopped and started both the index and search managers. maybe this is required after adding fields to this file?

Migrateduser

I think your question is answered in the search webcast (but my mind may be playing tricks on me).

Check out:
http://devnet.interwoven.com/site.fcgi/webcasts/docs/webcast-recordings.html#webcast05-15

hth,

lissa