| |
Home | Concepts | API | Samples |
Concepts > Versioning > Editing Workflows | |
Surrogate Default Version | |
A variation on the two-tier approach is to use a surrogate DEFAULT version as a
reconcile and post target for all other versions. This is another way of
protecting the DEFAULT version from direct editing and unauthorized or
unintentional modification. A new named version, in this case called
Mapping_DEFAULT, is created as a child of the DEFAULT version; all other
versions are then created from this new version as required. This isolates the changes made to the published version of the geodatabase until such times as it is considered appropriate to integrate these changes. A database administrator or project supervisor can reconcile, resolve any conflicts, and post the Mapping_DEFAULT version to the DEFAULT version without affecting other database users. Pros
Cons
|
feedback |
privacy |
legal |