The purpose of the page is to raise new features that are requested for future versions of the GSA.

It has been created and updated by GSA users and Administrators. 

Please specify a name for the request, a short description, and the date of inserting the request.

Name: Case Sensitive Indexing     

Description: When indexing a few urls with the same address, that only differ by an Upper Case/ Lower Case, one should use

the regexpIgnoreCase feature. The problem is that it creates duplicates and eats up the license.

The feature request is to enable using the IgnoreCase feature, but also indicate that the URLs are the same, and should not

be count as different.

for more information, please refer to the post:

http://groups.google.com/group/Google-Search-Appliance-Help/browse_thread/thread/26f737086cbf1c64/1f0606360a1e37ff?lnk=gst&q=Duplicate+Problem#1f0606360a1e37ff

Date: 03/11/2009

Name: Parametric Search  

Description: Although the Parametric search feature on the google code site (http://code.google.com/p/parametric/ ) is a great feature (thanks guys) how it handles numbering is misleading as it is only reporting on the top 100 search results, as this is the most amount of search results that can be returned at any one time from the GSA. Therefore an on-board feature that could return parametric details including numbering would be of great benefit especially for auction or sales sites.

Date: 10/02/2009

Name: Multiple Serving > Forms Authentication URLs

Description: With the advent of multiple Crawl and Index > Forms Authentication (Authentication) rules in v6.0, a corresponding change to Serving > Forms Authentication (Authorization) would be very beneficial.  This would allow multiple URLs to be entered on the serving side, enabling the simultaneous serving of content from multiple systems or environments with disparate login mechanics.  Currently, crawling is able to crawl multiple systems or environments, but serving can't keep up.  Workarounds such as Valve Framework are available, but such workarounds would not be necessary with this change.

Date: 10/15/2009

Name: Six Digit Limit for Number Ranges

Description: Number range searches (for inmeta fields) are limited to 6 digits. This limit seems very small and prevents doing number range searches for large financial numbers. This also prevents using numbers as a workaround for lack of date & time searches in the GSA.

Date: 11/15/2009

Name: Time Not Considered For Sort By Date

Description: The time portion of the date/time is ignored for sort by date. It would be nice if it would also sort by time also. Makes GSA less powerful for time sensitive data. It would also be nice if you could do inmeta searches for data and time ranges.

Date: 11/15/2009