Note: Due to RPF server demands, this process can take a while. Click Next and click Save as Draft if you want to perform other tasks in the application and return to this advanced import later.
Ringtail notifies you when the inventory is complete and the import fields are ready to be mapped. Click Next to view the custom mapped fields. To change the mapping of an import field, click a field in the Action column, and select one of the following options. For example, you can only map text fields to text fields, or Boolean fields to Boolean fields. One-to-many import fields can only map to one-to-many case fields.
To set a default value for a blank field in an imported document, click the field in the Default value column and type a value. Use the side scroll bar to view all fields. After you change the field mappings, click Next. Use this option to do the following:. The Load from SQL option is based on four tables that a user manually creates in the SQL database for the case before performing the import.
The following four tables match the structure and data standards of a Ringtail. For details on the structure and data standards for these four tables, see the Ringtail Import and Export Data Standards document.
Name all four tables with the exact same special prefix. Specify this prefix on the Import page. For example, if the prefix for tables is BigImport3-, name the tables as follows:. After you create the tables, a user with SQL access and permissions copies the import data into the tables. You can create multiple sets of four specially prefixed tables in the same SQL database, to use with different advanced imports, as long as each set of tables uses a unique special prefix.
Use SQL to copy data into the four specially prefixed tables. Enter the special prefix used for the tables to be used as import data.
Set any other import options, as required. Note : Administrators performing the first two steps must have access and permissions to the case database in SQL. Use the following procedure to copy an import job and modify the job to suit your requirements. For example, you can run a test import job, make simple adjustments, copy the test job, and perform the actual import job.
In the Imports list, hover over a row and click Duplicate , as shown in the following figure. In the Import dialog box, modify the settings, and then click Next. Continue to click Next on the subsequent pages and modify the settings as needed.
Note: Once you copy an import job, Ringtail prepends the words "Copy of" to the name of the import job. Use the following procedure to delete import jobs from the Imports list. This feature is useful if you save an import job as a draft and then decide to discard the draft import job. Note: When you delete a job, Ringtail removes the job from the list. The job is still in the database. You can customize the template as needed to create a case-specific load file template.
These templates provide the attributes of individual documents. In the database, each record, or row, in the document load file represents one document. These templates provide the attributes of individual pages. In the database, each record, or row, in the page load file represents one page.
Only case administrators can create or modify load file templates. After setting the delimiters, use this page to search for fields in the flat files. You can proceed to the next page only after the field search. In the Column - fields list, select the delimiter character for columns and fields. For example, if the flat file is delimited by commas, select , In the Text qualifier list, select the text qualifier character, if required.
To search the flat file for available fields, click Get fields. Note: Due to RPF server demands, this process can take a while.
If you select an incorrect delimiter, an error message appears. If you change the import details or delimiters, click Get fields again to run the search again. On the Map Files page, configure the location from which the application copies the associated native or full-text files. If you are copying source files, in the Native path list, select the field to access native files. This option appears only when you select Copy source files to the server on the Source Files page.
Note: The selected field must contain the relative path to the source files that you set on the Source Files page. Under Full text , select one of the following options:. The application uses the selected field values to create associated text files for searching. On the Existing Documents page, to determine how the application handles the import of existing documents, select one of the following Import action options, and then click Next.
Note: This page is similar to the Import documents feature. For more information, see Import documents. If you select Update existing documents only or Import new documents and update existing documents , additional options appear.
See the following table for descriptions of the options. For example, if a load file contains a document with a null value as its title, then the existing document is updated or overwritten with the null title. Only new documents contain import fields. Do not update fields: Deletes all field values for documents in the import data set. When selecting this option, none of the updated documents will have import field values.
Note: This option only clears field values for documents in the import data set. For example, if a case contains existing documents A, B, and C, and the import data set contains documents C, D, and E, selecting Delete all field values does not affect documents A and B. It clears the metadata only for document C. This applies only to mapped fields.
All other fields remain the same. This only applies to mapped fields. Do not update parties: Deletes all parties data values for documents in the import data set.
When selecting this option, none of the updated documents will have parties data values. This option applies only to mapped parties data in the target data set. Does not update pages: Deletes all pages data values for documents in the import data set.
When selecting this option, none of the updated documents have pages data values. This applies to both mapped pages data and all other pages data values in the target data set. On the Levels page, set the levels into which the application imports documents.
By default, the maximum number of documents is 1, per level, but this is configurable. The application truncates level names that are longer than 20 characters. To set the maximum number of documents per level, in the Max documents per level list, select a number. You must select at least one level for the document.
0コメント