Understand the property sheets and recommendations for mapping property sheets of IBM® Lotus® Quickr™ for WebSphere Portal with their ECM equivalents.
Property sheets 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.
In Lotus Quickr, a property sheet 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 property sheet.
There are two types of property sheets in Lotus Quickr – local and shared. Local property sheets are available to documents only in the library in which the property sheet resides. Shared property sheets can be shared across libraries of a place.
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 property sheet.
For more information about properties and property templates in FileNet P8, see the IBM FileNet P8 help topic Content Engine Administration > Properties.
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 property sheets 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
The following are 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|
|Multi-line Text||String||Variable character/Char|
|Number||Integer||Short integer/Long integer |
|Single Selection||String||Variable character/Char|
|Multiple Selection||String||Not applicable|
|Date and Time||DateTime||Timestamp|
- Not all the property template types available in IBM FileNet P8 can be mapped to the available property sheet types of Lotus Quickr. For example, the Binary property template type of FileNet P8 cannot be mapped to any of the available Lotus Quickr property sheet type.
- When publishing Lotus Quickr documents that have a Time property on a property sheet 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 property sheet types of Lotus Quickr. For example, the BLOB attribute type of IBM Content Manager cannot be mapped to any of the available Lotus Quickr property sheet type.
Use any or both of the following two methods to map the Lotus Quickr property sheet types to those on your ECM repository.
Use the Configuration Services: qp85
Make appropriate configuration settings from the WebSphere® Application Server administrative console to map the existing IBM Lotus Quickr for WebSphere Portal property sheets to their ECM equivalents.
Use the Custom Class: qp85
Write a custom exit class to further tailor your property names and data.
Parent topic: Map Lotus Quickr metadata with the ECM metadata for document publishing: qp85
Troubleshooting Publish to external location updates metadata
Troubleshooting Cannot pass null values to an external location during publish