Overview
In the editing of geographic database, it usually takes 1-2 hours for a task, and sometimes it may take several days to process the data. You may want to perform operations with complete quarantine, and you can undo or undo a single edit if a mistake is made during a long edit. When the same object is updated by another user, you can be reminded of the conflict to resolve it, rather than having subsequent changes directly overwrite previous changes.
The Version Control function can adapt to the needs of multi-user editing and long transactions. There is no need to lock or copy data, and multiple users can edit the geographic database at the same time without affecting each other. When you are working under Edit Personal, other users will not see data that you have not yet committed. You can edit for weeks or months. Commit changes to the parent version as you see fit. This function is applicable to scenarios such as geographic Produce Data allocation and field and office collaboration.
Version Control Main Workflow
When you use the Version Control function, you will mainly go through the following operations:
- Register Version: To use the Version Control feature, you must first register the DatasetRegister Version. The process of registering is called versioning. Currently we support versioning for points, lines, surfaces, text, property sheets, CAD Dataset.
- Create version: The version represents a snapshot of the entire Datasource at a certain point in time. The data of a version contains the All Data set under the data source, including versioned and non-versioned data. After a version is created, it can be distributed for editing by multiple people.
- Version editing: You can add and Delete Object records in the created subversion, and edit the attributes and Geometry Info of a single object. However, it is not allowed to edit field values in batches under the sub-version. Currently, it is only supported to edit field values in batches under the default version, and there are no unsubmitted changes in the sub-version.
- Version reconciliation: You can Commit Changes to the default version at any time. Before submission, version coordination is required to prevent conflicts caused by other users' changes to the same data.
- Version Commit: Merge the data changes under the current edit version to the Target Version. The commit operation can be completed only if no modifications have been made to the Target Version after the reconciliation operation.
Related topics
Version Control Basic Vocabulary