Appliance Update: Additional Fields XML namespace changed

Post Reply
User avatar
Kai
Site Admin
Posts: 1272
Joined: Tue Apr 25, 2000 1:27 pm

Appliance Update: Additional Fields XML namespace changed

Post by Kai »

There is a new appliance update available: texisScripts 6.3.3. It contains the following fixes: Additional Fields XML namespace changed. Added Authentication Schemes setting (some require future Texis upgrade). Fixed crawling when one Base URL's host is a substring of another. Removed extra gml: XML elements from Parametric GMLPoint output. Fixed metasearch back-end "additional field" element namespaces. Added Allow Leading Wildcards and Single-Word Wildcards settings (latter requires future Texis upgrade, and is on by default). Added page breaks to output of list/edit URLs.
User avatar
Kai
Site Admin
Posts: 1272
Joined: Tue Apr 25, 2000 1:27 pm

Appliance Update: Additional Fields XML namespace changed

Post by Kai »

Some clarifications on the texisScripts 6.3.3 release:

Additional Fields XML namespace was not actually changed in this release (that happened in 6.3.2, when they moved to the <u:> namespace), but in 6.3.3 Meta Search was also modified to propagate Additional Fields in the <u:> namespace.

The Authentication Schemes setting allows authentication schemes (such as Basic and NTLM) to be enabled/disabled; a near-future texis update will support NTLMv2.

The Base URL substring fix involved crawling, for example, http://www/dir/ and http://www.domain.com/dir2/: the latter's links would be incorrectly rejected with "Incorrect prefix".

The GMLPoint fixes (for Parametric Search appliances) involved changing XML from, for example, this:

<u:location>
<gml:Point>
<gml:pos>41.4133 -81.8756</gml:pos>
</gml:Point>
</u:location>

to this:

<u:location>41.4133 -81.8756</u:location>

in order to better support SOAP.

The Allow Leading Wildcards setting controls whether to allow searches with a leading wildcard, eg. `*word'. Such searches can take longer than trailing-wildcard searches (eg. `word*'), so they are disabled by default. The Single-Word Wildcards setting controls whether wildcards with trailing suffixes (eg. `aaa*bbb') will match the suffix (`bbb') in the same word as the prefix, instead of up to 80 characters away, and whether the suffix must match the end of a word, instead of just a substring. Full functionality of this also awaits a near-future Texis update.

The List/Edit URLs page now has page breaks (similar to results output), to better manage large lists of URLs.
Post Reply