Handling overlapping views UX

[Garbash]

Overlapping views presents a new set of decisions the user needs to take.
Here are the events that trigger a decision point:

(1) A node name is modified to have the same name as an existing node.
(2) A property within a node that appears in other graphs has been modified. This includes change of the node type.

• In case user has created a node with the same name as an existing node, node should automatically inherit the properties of the existing node. If user modified that node type is should be handled the same way as decision point (2).

For trigger event (1) user should be prompted with this pop-up:
"Node [node title] already exists in maps [list of map titles it appears in], what would you like to do:"
-"Merge with existing node"
add text beneath: "This will cause node to inherit data from existing node, overwriting previous information."

• "Create as a separate node"
  Add text beneath: "This will rename the node to [node new name]."
• "Cancel"

If user choses "Merge with existing node":
Modified node inherits the properties of the already existing node, overwriting existing data.

If user choses "Create as separate node":
The modified node is renamed by adding a "(x+1)" next to it's title where x is the existing number or 0 if no number exists. e.g. Dor Garbash duplicate will be Dor Garbash(1), duplication Dor Garbash(1) would create Dor Garbash(2) etc'.

For trigger event (2) the decision point is:
" Node x exists on maps[m1, m2, m3... ], confirm changing property z for this node in all maps?"
Buttons: "Yes" "Cancel".