|version 7.7.x||Download Pending|
This article includes advanced Administrator areas for PSIcapture.
This article is meant for PSIcapture Administrators.
The migration module provides options for moving document images and metadata to file folder formats, database formats, and content management systems. There are two types of migration formats that PSIcapture handles as outlined below.
- Direct Write - This type of migration can move images, metadata, and OCR text directly into the target content management system or database. The metadata and OCR text function as index values for image retrieval and Document Management systems. Database migrations create a standard MS SQL Server 2005 database or Access 2003 database where each index field name is a column, the index values are rows in the table, and the final column of the database table is the path to the drive/directory of the image file associated with each row of index values.
- Flat File - This type of migration includes text and XML formats. The user can then take the output files and import them in the ECM of their choice.
The Migration module is the data and image exporting stage of processing a PSIcapture batch. The product currently migrates data in over 60 different formats with many configurable options for each. All levels of index data, scanned images, and OCR output can be sent to a target location in a local or remote document management system, database, or folder, all depending on which migration method is being applied.
Migration to multiple formats or products is supported; when more than one migration target is selected and added to the workflow (see "Migration Settings" below), each migration will be executed sequentially from the top of the list to the bottom. Furthermore, multiple migration stages can be added to the workflow if data needs to be partially migrated, edited or checked, and then completely migrated.
For links to specific details on configuring migrations PSIcapture can process, see the "Available Migration Configurations" list below.
Adding a Migration Workflow Step
The Migration workflow step can be added in the Workflow section of Capture Profile Configuration.
As mentioned above, more than one Migration step can be added, each with its own set of migrations to process with different rules; usually, one Migration step is sufficient for most scenarios.
Fig. 1: Capture Profile Configuration, Workflow section.
In this example, the "Migration" step is selected from Available Workflow Modules.
Clicking the Add button will place "Migration" below "Quality Assurance" in the Workflow list to the right.
Migration Settings Window
The Migration Settings configuration window can be reached by adding it from the "Available Workflow Modules" list in the Workflow section while configuring a Capture Profile. Double-clicking "Migration", or selecting it and choosing "Add" will open and focus the window.
The Migration Settings window (see below) opens immediately after the Migration workflow step is added while configuring a profile (see Fig. 1 above). The General section is always the first to appear, and it lists migrations available to be added alongside currently configured migrations.
This list features all the migrations which can currently be used in the product.
Some migrations have Direct support, and are named as such: this indicates that the PSIcapture product will directly connect to the target system and upload the batch data in that system's native format.
Other migrations have Flat support, and are named as such or simply have a lack of "Direct" in the name: this indicates that the PSIcapture product will migrate a file/folder format that is expected by the target product without establishing a direct connection to that product. That exported data can then be imported by the target product.
This list features all the migrations that have been added to the current Migration step. Some notes on the behavior of this list:
- Migrations to a single product or generic format can be configured multiple times (e.g. you may have two separate FTP migrations in the workflow)
- Migrations can be duplicated with identical settings
- During batch processing, the migrations process in sequence from top to bottom
- Exception Processing alters the way the list behaves when a migration fails
Fig. 2: Migration Settings Window (General Section)
|Adds selected migration to the workflow and opens its Configuration window. Active only when a migration in the "Available Migrations" list is selected.|
|Removes selected migration from the workflow and discards all configuration data. Active only when a migration in the "Migration Workflow" list is selected.|
|Moves selected migration up in sequence in the "Migration Workflow" list. Active when the selected migration is not already at the top of the list.|
|Moves selected migration down in sequence in the "Migration Workflow" list. Active when the selected migration is not already at the bottom of the list.|
|Copies selected migration in the "Migration Workflow" list and all its settings. Opens the configuration window for that migration to confirm settings.|
|Opens configuration window for the selected migration in the "Migration Workflow" list. Can also be reached by double clicking the list item.|
Supported Migration Products
The following is the current list of products that PSIcapture will migrate to. This list will be updated as new migrations are added.
Supported Generic Migrations
Other migrations are not product-specific, but are for situations where a simple flat file or connection to a local or remote database serves as the migration target.
- Database (Access, SQL Server, Oracle, ODBC-compliant databases)
- Folder Export
Exception Processing Section
This subsection handles all settings for all migrations configured in this individual instance of the Migration workflow step – a profile with two or more Migration steps that both require exception processing must have these settings configured separately for both.
|Fig. 3: Migration Settings, Exceptions Processing Section|
Enable exceptions processing
|Activates exception processing for this Migration step. Enables radio button controls below.|
|Stop migrating when Document fails...||While using Automation, a batch will halt in the Migration step if any of the migrations fail.|
|Automatically reject Documents...||An exceptions batch will automatically be generated when a migration fails, and the Migration step will continue processing.|
|Send exceptions Batch...||Move exceptions batch to the listed step. Workflow steps added to this profile (e.g. Capture, Index, QA) will be listed in this drop-down.|
Basic Migration Setup Examples
The Migration Module provides options for moving document images and metadata to file folder formats, database formats, and content management systems. Two general types of migration formats are supported:
The direct type migration options move images, metadata, and OCR text directly into the target content management system or Database. The metadata and OCR text function as index values for image retrieval and Document Management systems.
- Flat file
The Flat file migration types include text and XML formats. The database migration creates a standard MS SQL Server 2005 database or Access 2003 database where each index field name is a column, the index values are rows in the table, and the final column of the database table is the path to the drive/directory of the image file associated with each row of index values.
Text Migration Configuration
The below screenshot is a sample of a PSIcapture migration configuration window. Text Migration contains most of the generic settings available to most other migration. This window will change slightly based on the needs of each different migration. For example, some migrations will require a server connection with user name and password and do not allow you to specify storage location.
Database Migration Configuration
Below is a basic example of a Microsoft Access Migration setup. For more information, see:
PSIcapture Administrator Guide: Database Migration Configuration
Article is closed for comments.