The User Interface for File Import

The File Import user interface is accessed by selecting the File Import tab in the Dynamic Import application.

FieldDescription/Procedure
MapUse to select and display a previously saved map file.
  1. Click the drop down arrow to access the list of map files. (There are no delivered map files—if no map files have been saved the list is empty).
  2. Select the map file to use.
Save AsUse this button to save a map file. Map files are saved with a .dim extension in Contenta_home/encaps/di/MapFiles.
  1. Click Save As... then specify the file name in the resulting window. Do not specify the file extension.
  2. Click OK.
DeleteUse this button to delete a map file.
  1. Click the drop down arrow to access the list of map files.
  2. Select the map file you want to delete.
  3. Click the Delete.
Directory to importIndicate the top level of the directory path to import. This is the directory on your file system, not the path in SDL Contenta. You can enter the path name in the field, or you can select it from a file system display by clicking the ... button.
Handle SubdirectoriesIgnore this option if you do not want the subdirectories or the files in the subdirectories to be processed.
flattenSelect this option if you want files in the subdirectories to be processed but do not want the subdirectories processed. Only the data files in the subdirectory are imported - the directories are ignored.

The structure, or hierarchy, established in the directory you are importing is not maintained.

createSelect this option if you want the subdirectories and the files in them to be processed. The structure (hierarchy) established in the directory you are importing is maintained. In the create field, enter the name of the Contenta container object that you want created if File Import encounters a directory without a valid object-type extension.

If the directory has a valid object-type extension, the object specified in the extension is created.

ExtensionIndicate the extension(s) of the file(s) you want to import. If a file’s extension is not listed here, the file is ignored.

Type the filename extension only, do not include the dot (.) before it.

PCM Object Map the extension indicated in the Extension field, to the Contenta object you want created and into which you want the data imported. For example: In the example above, module objects are created for files with a .txt extension and FixedFormat objects are created for files with a .doc extension. The data in the file is imported into the specified object.
Click to configure access to the database, files, the location in the Contenta hierarchy to import files, and other global information used by the import process.

The User, Password and Doctype information must be supplied unless they are specified in the digui.cfg file. Other fields are auto-populated with data that you can edit if necessary.

Global SettingsComments the description for use of this File Import (optional).
Pcmloadloc

The target location—that is, the container or hybrid object in SDL Contenta into which the directories and/or files should be imported.

The path must begin with /Global/sysadmin — this is followed by the container on the sysadmin’s desktop, then the containers from there down the hierarchy to the container into which you want to import.

Workdir

The directory path of Dynamic Import programs. To protect confidential files, edit the WORKDIR directory and specify a secure location for storage of temporary files during the import process.

User

Enter a valid Contenta username. The user must have permissions to use Dynamic Import.

Password

Enter the password for the user specified in the User field.

Server

Enter the name of the Oracle server—that is the server where your Contenta database resides.

Database

Enter the name of the database into which you want to import the data.

Socket

Enter the socket (Portal) number over which your system communicates with the Oracle server. If you are uncertain of the socket number, check the Socket field in the application’s login Options window.

DoctypeSpecify a document type (user defined). The data in this field populates the object’s Document Type property sheet. If your document is not XML/SGML, this field may not be significant except to be identified for reports or in searches.
SecuritySpecify the security level for the objects. The data in this field populates the object’s Access Level property sheet field. Valid entries are:

nobody 
secure 
sysadmin