Searching and Retrieving

It is very important to use action-oriented syntax when searching. Rather than trying to "hack" the right URL to make a call to the EDS API as users select facets or limiters, use actions to indicate the action that the end user wants to take. Please don't "hack" the URLs. Using actions takes advantage of our state-aware API and will result in faster responses. Faster responses result since actions augment the existing search instead of issuing a whole new search of the central index. For jumping page numbers, the action-oriented syntax GoToPage() is required to get past result #250.

For more information on improving search and retrieve requests please refer to the links below:

Learn more about search requests

Learn more about action-oriented syntax

Storing Results in the Session

If you go into a detailed record and then come back to the results list, instead of issuing that search all over again, store the results in the session and update that session variable as the user wants to change their search results. When you store the results, you can just use the results in the session variable as they go into and back out of detailed records. Even if a "next result" feature is used to jump from detailed record to detailed record, you will only need to issue a new search request when trying to jump to a record that wasn't in the original list of results.

Improving Application Speed Points to Remember

• Use action oriented syntax.
• Make as few calls to the Search method as possible by storing a user's search results in the session. Use that session set of results until the user does something that changes the search.