Understand the Forms and recommendations for mapping Forms of IBM® Lotus® Quickr™ with their ECM equivalents.
Forms are a way of associating some relevant information or metadata with a document. This metadata is in the form of several user-defined and system-defined properties that describe a document.
Forms in Lotus Quickr
In Lotus Quickr, a Form contains fields of information that can be associated with a document type. For example, a date or a person field can be added to a Form.
In Lotus Quickr there are two kinds of documents, Page and Document. Before working with metadata mapping, you should understand the difference between a Page and a Document. When a document has a Single Attachment field but no Rich Text field, it is a Document; otherwise, it is a Page. So, when customizing a form, if you add a Single Attachment field but do not add a Rich Text field, the document created from that form is a Document.
When you upload or import a file, it is a Document. Other contents like page, link, Forum Topic and response, comments and list items are all pages. On the ECM server side, you can create a Page from some—but not all—document types in the ECM repository. Not all document types support Pages, but all document types supporting Pages also support Documents. It is OK to map a Document Form to a document type supporting a Page, but if you try to map a Page Form to a document type that doesn't support Page, it will fail.
Not all ECM document types support the Lotus Quickr Page document type. But all document types that support a Page also support a Document. Therefore, you can map a Document Form to a document type that supports a Page Form. If you map a Page Form to an ECM document type that does not support a Page Form a mapping failure occurs.
Property templates in IBM FileNet P8
In IBM FileNet P8, property templates define properties that can be associated with an object.
There are eight datatypes available for the properties that can be associated with an object. These are:
A property template in IBM FileNet P8 provides the Lotus Quickr equivalent of a Form.
For more information about properties and property templates in FileNet P8, see the IBM FileNet P8 help topic Content Engine Administration > Properties.
Attribute groups in IBM Content Manager
In IBM Content Manager, properties are referred to as attributes. An attribute stores units of data (metadata) or values that describe a certain characteristic or property (for example, first name, surname, age, city, and so forth) of an item.
The available attribute types in IBM Content Manager are:
- Variable character
- Short integer
- Long integer
- Time stamp
- BLOB (Binary Large Object)
- CLOB (Character Large Object)
For more information about attributes in IBM Content Manager, see Creating an attribute
Similar to Forms of Lotus Quickr, attribute groups are available in IBM Content Manager. An attribute group is a convenient way to group one or more attributes together.
For more information about attribute groups in IBM Content Manager, see Creating attribute groups
Recommendations for property type mappings
Table 1. Recommended property type mappings between Lotus Quickr, IBM FileNet P8, and IBM Content Manager
|Lotus Quickr||IBM FileNet P8||IBM Content Manager|
|Plain Text||String||Variable character/Char|
|Text Area||String||Variable character/Char|
|Plain Text||Integer||Short integer/Long integer |
|Name Pop-up||String||Variable character/Char|
|Pop-up List||String||Not applicable|
|Time Pop-up||DateTime||Time |
- Not all the property template types available in IBM FileNet P8 can be mapped to the available fields of Lotus Quickr. For example, the Binary property template type of FileNet P8 cannot be mapped to any of the available Lotus Quickr field.
- When publishing Lotus Quickr documents that have a Time property on a Form to IBM FileNet P8, viewing the FileNet P8 document from the Lotus Quickr Connectors will show a timestamp property whose time part is the value from Lotus Quickr and whose date part is Jan. 1, 1970 (or Dec. 31, 1969 if the time specified is before midnight, GMT).
- Not all the attribute types available in IBM Content Manager can be mapped to the available fields of Lotus Quickr. For example, the BLOB attribute type of IBM Content Manager cannot be mapped to any of the available Lotus Quickr fields.
Use the following methods to map the Lotus Quickr fields to those on your ECM repository.
Parent topic: Map Lotus Quickr metadata with the ECM metadata for document publishing
http://www.ibm.com/support/docview.wss?rs=3264&uid=swg21323062|Troubleshooting: Publish to external location updates metadata">Troubleshooting:">http://www.ibm.com/support/docview.wss?rs=3264&uid=swg21323062|Troubleshooting: Publish to external location updates metadata
http://www.ibm.com/support/docview.wss?rs=3264&uid=swg21323056|Troubleshooting: Cannot pass null values to an external location during publish">Troubleshooting:">http://www.ibm.com/support/docview.wss?rs=3264&uid=swg21323056|Troubleshooting: Cannot pass null values to an external location during publish