About Collection Types

Collection Type

A Collection Type defines a given Collection. It specifies the format of a document that will be imported into the product.

A Collection Type is identified by a name and a version and is described by:

  • The list of Object Types it can handle. Several Collection Types can use the same Object Type.
  • A reader that defines the procedure to import documents and creates a Collection instance.
  • Dictionaries that define the translation of labels into several languages.
  • User properties that defines properties of the Collection.
  • Function calls to add custom behavior when importing a Collection.
  • Header and footer optional parameters are used to define the first and the last Object Types (must not have any sub-elements).

Collection user properties

You can define custom properties on Collections. These properties can be set:

  • During import - the user properties must be provided in an XML file or in a property file in addition to the data content file.

Import settings

To import a Collection, you must specify the Reader service that you are going to use. You can also specify import conditions in the Collection Type selection table.

Import Reader

A Reader is a service that you use to import a document into the product's database.

From the set of readers provided, you can choose the reader that is most suited to your needs:

  • Variable flat file reader: Each line of the file contains an Object or an Element. Errors can be stored at the end of each line. Property values as well as error properties are delimited with a separator.
  • Fixed flat file reader: Each line of the file contains an Object or an Element and property values are stored in fixed-size fields.

Collection Type selection table

You can define in the Collection Type selection table the file import conditions that must be met. When a file is imported, the system accesses the corresponding Collection to retrieve the information that is necessary to read the file: format, reading procedure, reading configuration, and so on. Conditions can be validity dates or any other selection criteria.

Example: You can use the the AccCollType Collection Type if the current date is contained between [1/1/2009 and 1/1/2010] and the 'targetApplication' = "FAD".

Related Links