Adapting collection definitions

All collections and items are listed that are currently defined in the configuration store. You can add items to existing collections or add new collections. You can also delete definitions from the configuration store.

• Add, edit, or remove item types or document classes.
  • To add an item type or a document class to an existing collection, select one of the defined collections and, under the list of defined items, click Add.
  • To edit an item type or a document class, select one of the defined collections. Then, select the item type or document class and click Edit.
  • To remove an item type or a document class from a collection, select one of the defined collections. Then, select the item type or document class and click Remove. Note that this is possible only if more than one item type or document class exist in the selected collection.

  To add or edit an item:

  1. Select a repository connection.
  2. In the Name field, enter or edit the name.
     Important: For FileNet® P8, you must use the symbolic document class name, not the display name.
  3. Email only: Enter or edit the names of the child components that define the subcollections for the instance-specific information of email documents or attachments.
  4. Email only: If you want the item type or document class to be used for a specific period of time, select a start date and an end date.
  5. Click OK to save your entries, click Cancel to leave the window without saving.
• Add or remove collections, or map collection fields to content server properties and text index fields.
  The Defined collections list contains all collections that are defined in the archive mapping. When you select a collection, the item types (IBM Content Manager) or document classes (FileNet P8) that are defined in the selected collection are listed. For all types of archived data access configuration, you can add, edit, or remove collections, and you can map collection fields to content server properties and text index fields. What data you must specify, depends on the type of configuration.

  Option	Description
  Add a collection for archived email	When you add a collection to the archive mappings, you must specify this data: On the Base collection page Specify a collection name and, if applicable, a collection type. Content Collector 4.0.1 fix pack 13 (4.0.1.13): The collection name is set to Db2TS Mail/NSE Mail by default for CM8 repositories. A collection type drop-down has been added for Db2TS/NSE with the following options: IBM Content Manager - IBM Db2TS Services IBM Content Manager - NSE In the Document Type section, select a repository connection. Enter the name of an email item type or document class that is defined in IBM Content Manager or FileNet P8. Depending on the selected collection type, you must enter the names of one or more components that will contain instance information. Tip: Use an item type or document class in one collection only to avoid problems caused by definition mismatches. On the Sub collections page Set up the collection definitions for instance information. Attachment instance collection Select the attributes that contain the attachment file name, the correlation key for attachments, and the reference information to the item type that holds the attachment content. Email instance collection Select the attribute that contains the mailbox ID. On the Collection fields page Map collection fields to content server properties or text index fields.
  Add other collections	When you add a collection to the archive mappings, you must specify this data: On the Base collection page Specify a collection name and a repository connection. On the Collection fields page Map collection fields to content server properties or text index fields. You must at least define the collection field FILENAME. This field is required for retrieving the file name. Map the field to the respective content server property, which must be of the type String. Important: For FileNet P8, you must use the symbolic property name, not the display name.
  Remove a collection for archived email	Select a collection to delete from the archive mappings. Remember to adapt the layout of the Email search page accordingly by modifying the search configuration file.
  Remove other collections	Select a collection to delete from the archive mappings.
  Edit fields in a collection for archived email	Set up collection fields and map these fields to content server properties (for attribute search) and to text index fields (for full-text search). These are the fields for which users can search. To address fields in other collections as required by the data model, define reference fields: Add a collection field of the type reference and, from Referenced collection, select the collection that contains the fields that you want to address. You can define only one field of the type reference for each target collection. Add other collection fields to address the specific fields in the referenced collection. To be able to retrieve archived documents, a basic set of fields must be set up and mapped to content server properties. For reserved keywords, see Configuring the access to archived data manually. You can work only with properties or text index fields that are defined in the configuration store. Existing entries are listed on the Properties page or the Text Index page, respectively.
  Edit fields in other collections	Define collection fields and map these fields to content server properties or text index fields. For reserved keywords, see Configuring the access to archived data manually. You can search on these fields by using IBM eDiscovery Manager. To be able to retrieve documents that were archived from file system or Microsoft SharePoint sources by name, at least the field FILENAME must exist and must be mapped to the respective content server property. The content server property must be of the type String. Important: For FileNet P8, you must use the symbolic property name, not the display name.