Search History Table
The Search History table appears at the bottom of the Advanced Search and Search History pages for all product databases. Whenever you perform a search, the results of your search display in the Search History table.
When performing an All Databases search, the Search History table appears at the bottom of the Search History page.
What Does the Search History Table Display?
Displays the number of the search set (#1, #2, #3, etc.). Search sets are listed in reverse chronological order with the most recent search set at the top of the table.
Displays the total number of results retrieved, along with a link that takes you to the Results page.
Search History Details Column
Displays field tags, search terms, timespan, and other information in the Search History table.
The phrase "Refined by" will appear before each set that you create using the Search within Results, Refine Results, and Analyze Results options.
The search sets are listed in the Search History table in reverse numerical order - the most recently created set is at the top of the table.
To combine two or more sets:
Set Combination Examples
#1 AND #2
Finds all records that appear in both set #1 and set #2.
#2 OR #3
Finds all records that are in set #2 and all records that are in set #3, including records common to both sets.
#1 AND #2 AND #4 AND #6
Finds all records that are common to all sets (#1, #2, #4, and #6).
Save History / Create Alert
Save History/Create Alert gives you the option to save search queries and open them later.
Click Save History / Create Alert to save your search and create an alert (only available from the Core Collection database). If you want to save a search query to your local drive, click Save search history to a local drive; you can always import the file later from the Searches and Alerts page.
You can save up to 40 search sets from the Search History table. A search history contains the search query and selected settings for each search query.
At this time, alerts are not available for Compound Searches.
See also Save Search History
Open Saved History
From the Search History or Advanced Search page:
Dependent Sets: After you click Delete, the product checks for dependent sets. Selected sets that are not referenced in other sets are deleted. If, however, a set is referenced in a set that is not selected for deletion, the product returns the following error message.
In this instance, the product marks the Delete Sets check box of both the original set marked for deletion and the referenced set. You can either delete both sets or neither set.
Example 1: You create a set combination (set #3) that includes sets #1 and #2. You cannot delete set #1 because set #3 (the referenced set) is dependent on set #1. You can, however, delete both sets #1 and #3.
Example 2: You create a set (set #2) by using the Refine Results option from the Results page. You cannot delete this set because it is dependent upon the original parent set (set #1). You can, however, delete both sets.
About SAME and Saved Searches
When you open a search history file created from a previous version of the product, your search may yield more results if you had used the SAME operator in your query. In the current version, the SAME operator works exactly like AND in most fields (such as the Topic and Title fields).
For example, the search query:
TS=Bird Migration SAME TS=South America*
Is automatically translated in the current version of the product into:
TS=Bird Migration AND TS=South America*
and produces a larger set of search results than the original query.
When opening a saved search history file from a previous version of the product, consider revising your query if you had used the SAME operator in the query.
Note: The exception to the rule discussed, here, is the Address field where SAME operator rules still apply.
Saving Search Queries
You can save up to 40 search sets from the Search History table. If the table contains more than 40 sets, then a message appears above the 40th row indicating that the sets below this point can be saved, but those at row 41 and above cannot be saved.