Migration Center: Migrating Alerts and Saved Searches

ProQuest Dialog

Migrating Alerts and Saved Searches

Alerts Migration Overview

We know that you rely on Alerts to keep you up to date on key information and are making every effort to ensure successful Alerts migration.

Dialog staff will oversee translation and quality assurance (QA) of all Alerts queries to ProQuest Dialog.

ProQuest Dialog search syntax is a little different and you may need some time to learn how to use it. Therefore, all Alerts and saved searches are being converted for you via automated translation. Dialog customer support staff will then run each Alert to see if it returns expected results, and adjust syntax where needed.

Once the Alerts are translated, reviewed and turned over to you, it will be important for you to check the results yourself.

There may be subtle differences that are difficult for Dialog staff to catch. Also, you may want to review and change the focus of some Alerts. Once your Alerts are turned over to you, please make it a priority to review and edit them if needed.

Alerts will be released to customers starting in October. Please review the timeline for important details on migration.

Phase 1: August-September
Dialog team reviews and edits customer Alerts

Phase 2: October-November
Customers review and refine their Alerts

Learn How to Edit and Manage Alerts

How to create, edit and delete Alerts — Coming Soon
How to create and edit Alert frequency, email addresses and distribution lists — Coming Soon
How to test and edit saved searches
View Module | View transcript

	ProQuest \| About Us \| Site Search \| Site Map


Copyright Notices \| Terms of Use \| Privacy Statement

August-September 2011:

DO NOT USE THE IMPORT FUNCTION OR EDIT ALERT PROFILES IN PROQUEST DIALOG DURING THIS PERIOD.

All existing alerts will be translated from DataStar search syntax into ProQuest Dialog search syntax.

Dialog staff will review and run the translated queries, comparing results on ProQuest Dialog and DataStar. If index fields or other parameters did not translate, staff will edit the ProQuest Dialog search.

Saved searches stored offline or in a software package (e.g., DialogLink or STN Express) will not be auto-migrated. Please save such searches online in DataStar by September 30th if you would like automatic translation to ProQuest Dialog syntax.

DataStar Alerts created or modified after September 30 cannot be reviewed by Dialog staff.

IMPORTANT: Do not use the IMPORT function within ProQuest Dialog. Your alerts and saved searches will be “pre- imported” and are being reviewed. Clicking IMPORT will pull over your original alerts and saved searches a second time, making it impossible to determine which version has been reviewed or edited by Dialog staff. Dialog is not responsible for Alerts that are imported by customers themselves.

October-November 2011:

REVIEW RESULTS AND COMPARE TO RESULTS ON LEGACY AFTER YOU ARE NOTIFIED OF ALERTS RELEASE.

All new Alerts should be created on ProQuest Dialog after October 1st.

After QA, staff will “release” the Alerts to customer by entering the user(s) email delivery address, starting in early October. You will be notified when your Alerts are available for review.

Pre-existing Alerts will continue to run on DataStar. Once your Alerts have been imported onto ProQuest Dialog you will receive and be able to review results from both platforms. Alerts will run on both platforms until you complete migration.

Alerts for customers who have chosen to start the migration process on October 1 receive priority status.

IMPORTANT: Saved searches will be imported along with Alerts but the search syntax for saved searches will not be reviewed by Dialog staff. We recommend that you review and edit the syntax of saved searches as you use them and are becoming comfortable with ProQuest Dialog search syntax, any time after your Alerts are available to you.