Support Versioning Data Model with Unique Attributes in Content Management Library Server
Original Publication Date: 2003-Jul-25
Included in the Prior Art Database: 2003-Jul-25
Content Management (CM) supports multiple versions of a document/item by keep tracking metadata of each version in Libeary Server (LS). However, database unique indexes can not set to an attribute or a set of attributes like IndexName(AttributeName) directly any more since the attribute values should be allowed to duplicate within the same document/item but different version. Therefore, versionID is added as part of database unique index like IndexName(AttributeName, VersionID). This updated unique index can prevent duplicate attribute value for different Item with the same versionID, but not for different Item with different VersionID. The approach CM Library Server uses to combine database unique index and application checking together to support unique attributes with versioning. This will guarantee the data integrity for versioning and unique attribute aspects of views.