Report:Delphion/Search History Interface/Editing Saved Queries
|Report||Patent Coverage Map||Ratings||Comments|
|This search system report was created by the Intellogist Team and is available for viewing only. If you'd like to share your knowledge on Intellogist, please visit the Best Practices, Glossary, or Community Reports pages. Registered users may be notified of any substantial changes to this report by placing a "watch" on the Revisions page, which is the last page listed in the table of contents. To learn more about using the Intellogist "watchlist," see the Watchlist Help page.|| |
|DWPI on Delphion is no longer available, as of March 31, 2012. DWPI data is available on the Thomson Innovation platform.|
Editing Saved Queries
As stated in the section above, Delphion offers “edit” and “clone” options alongside its search queries. These two functions both allow the user to edit the query and re-run it: the difference is that “Edit” will allow users to edit the specific query without preserving its original form, but clone will create a totally new query using the “cloned” query as a starting point (and which can be saved separately from the original string). The “edit” function allows the user to fix a strategy error or correct a typo, (for example, so that a mistake will not show up in the final history); “clone” allow the user to experiment or add-on to an original query, and save the result as an independent string.
Both the “edit” and “clone” functions, when selected, will take the user to the query editing page. Queries must be edited in a text box, where they appear as they were translated into the CLI language by the search algorithm (even if they were first run in the database via a search form). The collections to be searched, as well as display options for the results, may also be set from this page.
From the edit window, a test run of any changes can be performed by selecting the “test run” link at the bottom of the page. This allows users to test that their edits return the expected results. If the user has selected “edit,” instead of “clone,” it’s a good idea to use the test run, especially when the query language is complex: once edits are saved, the old query language is lost, so testing any changes before saving is a prudent step.
After the needed edits are completed, the form allows the user to save the new query (but not to save and run it simultaneously); this means that all edited queries must be first saved to the saved strategy page before they can be run through the database. The browser will return to the Saved Strategies page, where selecting “run” will calculate the search results.