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

Teamsite Search - Configured extendedAttributeFields but not returning results?

Tim__D

When performing an advanced search on custom EA's that are replicants no results are being returned. In the examples, one is given suggesting that the product can be configured to index all instances of a replicant.

Example:
<fieldSpecification>
<fieldName>TeamSite/Metadata/location/system_id</fieldName>
<fieldType>int</fieldType>
<fieldStorage>zone:ExtAtt-system_id</fieldStorage>
</fieldSpecification>

I have RTM re-indexed etc.. all the obvious stuff.

- Tim

TeamSite 6.7.2 SP1
Solaris 10

Find more posts tagged with

Comments

Tim__D

I now see that the example that was for a template not an EA. I also found some problems. See the new fragment from my fieldmapping.xml file.

<fieldSpecification>
<fieldName>TeamSite/Metadata/location[0]/system_id</fieldName>
<fieldType>int</fieldType>
<fieldStorage>CustomInt1</fieldStorage>
</fieldSpecification>

However I see no examples that deal with TagUI replicants.

For replicant EA's I've tried using the /TeamSite/Metadata/field[0]field syntax as well and that also does not work?

Any help is appreciated.

Tim__D

See updated syntax. Ideally I'd like it to index all replicants so instead of "/0/" I could do something like /0-100/ or location/system_id. Anyone know if this is possible?

<fieldSpecification>
<fieldName>TeamSite/Metadata/location/0/system_id</fieldName>
<fieldType>int</fieldType>
<fieldStorage>CustomInt1</fieldStorage>
</fieldSpecification>

Tim__D

In 7.3.1 the solution to indexing EAs that are replicants is to define an instance nums using a /*/

TeamSite/Metadata/location/*/system_id

However the issue I am facing is that though EA's with replicants can be index in the same zone the advanced search screen does not honor the /*/ syntax when defining a custom EA attribute to search for and the only way it will return results is to define each one which is results in separate fields in the UI which is essentially unusable for users.

Adam Stoller

In 7.3.1 the solution to indexing EAs that are replicants is to define an instance nums using a /*/

TeamSite/Metadata/location/*/system_id

However the issue I am facing is that though EA's with replicants can be index in the same zone the advanced search screen does not honor the /*/ syntax when defining a custom EA attribute to search for and the only way it will return results is to define each one which is results in separate fields in the UI which is essentially unusable for users.

Have you opened a case with Support to file a defect on it?
If not, you probably should...

GriffTheDog

In our solution we have a defined maximum number of replicants.

In the FieldMapping.xml we point them individually to the same zone:

[HTML]

TeamSite/Metadata/location/0/keywords/0/keyword
string
zone:keyword

TeamSite/Metadata/location/0/keywords/1/keyword
string
zone:keyword

TeamSite/Metadata/location/0/keywords/2/keyword
string
zone:keyword

[/HTML]

In the search_custom.xml we point to the first EA only and since the replicants are indexed into the same zone results come back from all three replicants.

[HTML]

[/HTML]

TeamSite 6.7.2 on Windows 2003
TeamSite 7.3.2 on Windows 2008

Tim__D

Thanks All. The above would work but I am dealing with unbounded replicants which have a few nestings in places making defining all the combinations in fieldmapping.xml less than ideal to say the least.

We're experimenting with this more elegant alternative. Basic regex [0-9]+ and .* seem to be supported as long as the

[HTML]true[/HTML] element is defined. So far results are promising.

Its in the XSD but did not stick out in the documentation.

[HTML]

TeamSite/Metadata/vocabulary/[0-9]+/key
string
zone:ExtAtt-vocabulary-key
true

[/HTML]

In the search_custom.xml specify the same value of "fieldName" in this case "TeamSite/Metadata/vocabulary/[0-9]+/key" as the id.

Still testing this but as I said...looks promising. Disregard my previous "10-18-2013, 08:18 PM" post entirely.