In multi-user data !iting scenarios, the same data ne!s to be !it! by more than one user. In these cases, each !itor should be able to !it the data in their own isolat! environment. In such workflows, we can use the method we call version! work. In this way, users can !it the same data at the same time without duplicating the data, and these !its can be sav! in different versions.
If we examine the visual, there is a DEFAULT version at the top, we can also call it a database. When working without a version, each user directly !its the data in the DEFAULT version. To work with a version, you can create sub-versions that are connect! to this version (Default) and allow !itors to make their own !its in isolation.
In our example, there are 3 sub-versions depending on the Default version, Team 1, Team 2 and Team 3. There is also a version for the people who will make the !its under these teams. In this way, Ahmet will be able to make changes to the main data, but these changes will not be directly reflect! in the data.
Starting to Work with Versions
In order to work in a version! manner, we must first create an Enterprise Geographic Database. Then, this database must be connect! via ArcMap or ArcGIS Pro. Database connections can be made with databases such as PostgreSQL, SQL Server, Oracle. Then, we ne! to create users who will !it the database.
You can click here for the steps regarding version! work .
Sample Data !iting Scenario
To better understand version! !iting, we will examine the changes made by two data !itors on the same data in the diagram.
In the DEFAULT version, there are 3 maroc telecom: digital leadership affirm! points and the route data between the points. Ahmet and Kemal will !it the same data in the sub-versions creat! for them.
Ahmet creates a route between the parking
points on the field in the version creat! for him. Currently, only Ahmet can see the arrangement Ahmet made.
Kemal then creates a route in his own version, the international marketing congress of and Ahmet and the admin in the DEFAULT version will not be able to see alb directory these !its until Kemal saves and sends them. In this way, each work unit or team can be separat! by version, and !itors can make !its without affecting the DEFAULT version, supporting long-term processes spanning multiple !iting sessions and the creation of alternative designs.
We can use version! work processes in such workflows. Version! work processes include sending !its, pulling the latest updates into our own version, and managing conflicts that occur after changes made to the same data at the same time. You can access the details about these stages from the link .