Please enable JavaScript to view this site.

 

Navigation: Scripts

Importing Scripts and Related Data

Scroll Prev Up Next More
For multiple license configurations, it is possible to import or export scripts, and all related data, from one database and/or site to another.

 

Migration File Selection

 

To import scripts, as well as all their related data, click on the admin menu of the main window, then on Data Migration, and finally select Import.

 

A dialog, as shown in the image above right, asks you to enter today's admin code, which you can obtain from technical support.

 

Using the Advanced importation option is NOT recommended

Using the Advanced importation option is NOT recommended

You will then be asked to close any script currently open on your workstation and to have all other users close Q++Studio on their workstation.

 

The dialog shown on the right then comes up letting you select a migration file.

 

The name of the migration files contain the date and time when they were generated (ie. exported), as shown in the image on the right.

 

This ZIP file which contains one or more scripts and all related data, as exported using the data migration export function.

 

Using the Advanced importation option is NOT recommended.

 

Existing Data and Conflicts

 

Default Procedure

 

If you have not checked the Advanced option, as suggested, then the importation will proceed automatically, using the default setting whereby all previously-imported data elements are kept (recommended).

 

This setting means that any data element that was previously imported will not be overwritten by the current import.

 

For example:

 

Suppose one day you import a zip containing script A which refers to, and contains, holidays set X.

Then, a month later, you receive a zip with script B which also refers to, and contains, holidays set X.

Using the default option keep all previously-imported data elements, on the second importation, means that the holidays set X, contained in the second zip, will not be imported.

Concretely, this means that, after the second import, your database will contain scripts A and B both referring to the holidays set X as it was in the first zip export folder of a month ago.

 

This default procedure has the advantage that, if there have been change to holidays set X, at the exporting site, between the first and second exports, then only the newly imported script B needs to be fixed.

 

Using the default suggested method of importation, there is no risk that any of the existing scripts of your database might be affected by the change of any of the data set that they might refer to.

 

Advanced (step-by-step validation of conflicts)

 

If you have checked the Advanced option then the dialog on the right asks you to confirm that you wish to use the Advanced importation options.

 

This is not recommended at all.

 

If you nonetheless confirm your choice of the Advanced importation, then a series of dialogs will appear, such as in the example below, each one letting you decide if a specific type of previously-imported data elements should be ignored or overwritten.

 

Use the Skip button to exclude all data elements shown in the dialog, from the importation (ie. keep the existing data).

Use the Replace button to replace all existing data elements by those shown in the dialog.

Once you click on the Skip All or the Replace All button, this dialog will no longer appear and all further conflicts will be skipped or replaced, accordingly.

You can decide for each type of data (ie. every time this dialog comes up) whether to Skip or Replace, but in each case your choice applies to all the data records currently displayed in the dialog (for example, in the screenshot above, it is not possible to ignore some of the imported macros sets and have some others replace the existing ones in the database). It's all or nothing.

If you specified a prefix in the data migration export, then for those data set elements, that prefix will appear in the exported name column, as shown in the image above.

 

Summary

 

At the end of the importation, a summary dialog appears, listing all the data elements, QuarkXPress files and/or InDesign that will be imported, as well as those data elements which will be skipped.

 

No changes have yet been made to your database.

 

You can use the Export button, at the bottom of the dialog, to export the displayed summary into an Excel file.

 

Confirmation

 

If the list of skipped and imported data elements is as you wanted it to be, then click on the OK button to copy the merged data back to your database.

 

In some cases, after you click OK and the data is merged back to your server, a message might appear, informing you that there is a problem with the zip file containing the related QuarkXPress, InDesign and PDF files.

 

This does not mean that there was a problem with the importation of the script and related data tables. For instructions on how to address the issue flagged by this message, see the topic corresponding to message 185185.

 

Re-starting Q++Studio

 

At the end of the Data Migration Import, Q++Studio will need to close down and restart.

 

See also: data migration export.

 


Topic 181430, last updated on 26-Apr-2021