Version management

Feature overview

Purpose

Version management maintains the version number and description within the project, and establishes a new modeling version based on the current version; version comparison is used to view the statistical indicators of the two versions.

Easy to understand: Keep separate versions for a modeling round and compare changes in model size.

Main features

• Baseline Copy: When adding, copy the modeling data that supports version copy from the selected base version.
• Version Information: Maintain version number, description and baseline information.
• Statistical comparison: Compare the statistical quantities of Modeling Goals and various model elements.

Scope

The information on this page belongs to the current project and version; entry, editing, deletion and other operations are subject to corresponding authorization controls. After switching projects or versions, lists and associated objects should be rechecked.

Before you begin

Prerequisites

1. You have logged in to qOntology and have obtained the permissions for this page and the required operations.
2. The project has been created in [Basic Management], and the correct project and version have been selected at the top of [Ontology Modeling].
3. The baseline version to be replicated has been confirmed and a new, non-duplicate version number has been prepared.

Navigation path

【Ontology Modeling】 > 【Version Management】

Page overview

The list displays the version number, description, baseline version, creation information and current version mark, and provides operations such as [Version Comparison], [Modify] and [More].

Recommended workflow

Confirm the current project version → add a new version → switch to the new version to check data → continue modeling → view version comparison.

Functional operation instructions

Query and reset

1. Fill in or select the version number in the query area.
2. Click [Query].
3. Click [Reset] when you need to restore conditions.

Result: The list is reloaded according to conditions and can be viewed in paging.

Add project version

1. Start by selecting the project version to base on at the top.
2. Click [Add].
3. Fill in the new version number.
4. Fill in the description if required.
5. Check against read-only baseline versions.
6. Click [OK].

• Version number: It cannot be repeated within the project. It is recommended to use an identifier that can identify iterations. (required)
• Description: Describe this modeling adjustment, up to 200 characters. (optional)
• Baseline version: The currently selected version is displayed when adding a new version and cannot be edited directly in the form. (brought in by the system)

Result: After the addition is successful, a new version appears in the list; the system copies the relevant modeling data according to the baseline version.

After creation, switch to the new version through the top version selector and check targets, objects, properties and other data. Do not interpret new versions as publishing to the application or rolling back data.

Compare two versions

1. Click [Version Comparison] in the target version row.
2. Check the [Baseline Version] on the left.
3. Check [Compare Versions] on the right.
4. Switch between the two versions as needed.
5. View statistical differences.

Result: Display version information and statistical comparisons of Modeling Goals, terms, enumeration, objects, attributes, relationships, axioms, Data Rules, etc.

This page displays statistics and changes. It is not a field-by-field change list, and there is no merge or rollback operation. If the quantity is consistent, there may also be differences in content. You should further go to the business page to check.

modified version

1. Click [Modify] on the target record row.
2. Adjust the fields that need to be modified.
3. Click [OK].

Result: The list will be refreshed after successful saving; reopen the record to check the modification results.

View version details

1. Click [More] on the target row.
2. Click [Details].
3. Check the version number, description, and baseline information.
4. Click [Close].

Result: Read-only display of this version information.

delete version

1. Click [More] on the target record row.
2. Click [Delete].
3. Check the target record in the confirmation box.
4. Confirm deletion.

Result: After the deletion is successful, the list is reloaded and the target record is no longer displayed.

You can also check records and use [Delete] above the list to process them in batches.

Warning

Check the business purpose and related information before deleting. This page does not provide a recycle bin recovery entry.

FAQ

• Can I directly change the baseline version in the new form?
  cannot. First close the window and switch the baseline version at the top, then add it again.

• Why does saving the version number fail?
  The version number cannot be repeated within the same project. Please change the logo before submitting.

• Can version comparison restore the old version?
  cannot. The current page only provides statistical comparison and no restore or merge buttons.

Summarize

Keep separate versions for a modeling round and compare changes in model size. Confirm the current project version → add a new version → switch to the new version to check data → continue modeling → view version comparison.