An import package is a set of documents or asset information and an accompanying MS Excel workbook that contains metadata about the items in the package. Import packages support external references, hybrid documents, multiple revisions of the same document, and drawing title block data exchange.
Packages can be exported from Meridian Explorer as described in Export a Package. Packages can also be imported into a Meridian Enterprise vault from Meridian Explorer or automatically from a Meridian Portal tenancy. The (export) packages can be created by Meridian Explorer, manually by users, by Meridian Portal, or by some other system and sent to Meridian Enterprise Server.
You import packages into Meridian Enterprise according to a set of rules called an import profile that is created by a System Administrator. Different import profiles can be configured for different sources, destinations, or purposes for the packages.
Meridian Enterprise Server lets you see how documents will be imported before the import is actually performed. You do this by scanning the package. This lets you verify the import configuration before any changes are made in the destination vault.
Meridian Enterprise Server scans and imports packages in the background, which lets you continue working. You can monitor the progress of an import at any time.
The following table lists the minimum steps for importing a package and the corresponding topics in this guide that describe each step in more detail. The steps are listed in the order that they should be performed.
-
A Meridian Explorer client license must be available to work with import packages.
-
The Enable Advanced Project Workflow Module option of the source vault must be enabled for the Export Packages and Import Packages property pages to appear in the Meridian Enterprise clients.
| No. | Step | Topic |
|---|---|---|
|
1 |
Collect the documents into a folder or in an archive (ZIP) file that you want to import. |
Consult a System Administrator |
|
2 |
Create an MS Excel workbook file that includes a worksheet that contains the metadata that you want to import. |
|
|
3 |
Create a copy of the workbook file with empty rows to serve as a template for the metadata. |
Consult a System Administrator |
|
4 |
Create an import profile to specify how you want Meridian Enterprise Server to import the metadata and the documents. |
|
|
5 |
Create a new, open package to associate the source documents, metadata, and import profile together for import. |
|
|
6 |
Start the scanning process. | Scan an Import Package |
|
7 |
Review the scan results and adjust the import actions as necessary. |
|
|
8 |
Start the package import process. | Import an Import Package |
|
9 |
Close the package to indicate that it has been completed. |
Depending on the outcome of the scanning or import processes or for business reasons, you might want to repeat, abort, or skip steps. The preceding steps and the available commands for each step are shown in Route an Import Package and are available in the toolbar.
Import packages are designed so that these steps can be performed by different users who may have separate responsibilities for documents in your organization. For example, one user (such as a System Administrator) might be responsible for creating import profiles; a second user (such as a project team member) for creating, scanning, and importing packages; and a third user (such as a project leader) for approving packages before they are imported and for closing packages. Processes like this can be supported by the security privileges described in Create an Import Profile.
