An item checked out for modification can be checked into the repository. This operation applies the changes to the content stored in the repository.
Content Server maintains a history of the changes applied to objects using versions. When a checked out object is checked back in, a new version is created. Each version is a separate object (content and metadata) but is aware of the object from which it was created. A version tree is a visualization of multiple versions derived directly or indirectly from the same root object. Duplicate versions are not allowed in a version tree, since the purpose of the version tree is to enable distinction among objects based on their versions. Versioning is described in detail in the following section.
Applications such as Webtop offer several options for altering the behavior of checkin:
1. The user can choose not to create a new version and replace the existing content with the content being checked in.
2. The user can choose to increment...