Understanding Object Versions and Checkin/Checkout

This section includes the following topics.

• About Object Versions
  Oracle Life Sciences Data Hub keeps all object definitions and instances under version control, maintaining a record of the user who created each new version, the date and time the version was created, and, for definitions explicitly checked out, an optional comment entered by the person who checked it out.
• Checking Out Objects
  When you check out an object, either explicitly or implicitly, Oracle Life Sciences Data Hub creates a new version of it.
• Checking In Objects
  Oracle Life Sciences Data Hub finalizes an object version when it checks in the version, either explicitly or implicitly, as follows:
• Undoing Object Checkout
  After you explicitly check out an object definition, you can explicitly uncheck it. Oracle Life Sciences Data Hub discards the new version.
• Version Labels
  You can use version labels to identify important versions of objects.
• Version History
  You can see the version history of object definitions (not instances) by selecting View Version History from the Actions drop-down list.
• Versions of Component Objects
  Oracle Life Sciences Data Hub implicitly increments and tracks the version number of components of object definitions such as Source Code, Planned Outputs, Table Descriptors, and Columns that are not contained directly in a Domain or Application Area but only in other defined objects such as Programs or Tables.