In the xul client, we averted this issue in the unified editor by creating a new call number behind the scenes and transferring any items being edited to this new call number. This behavior also came into play when using the 'Edit Items/Volumes Per Bib" option in Item Status of the xul client.
However, there were a lot of complaints about this behavior in bug 1040686. We 'fixed' this bug in the web client, but I think it left us in a place where there is no easy way to update the call number for just some of the items attached to that call number. You can create a new call number and then transfer those items to the new call number, but I wouldn't call this workflow easy when compared to the old way of doing it in the Unified Editor.
In the xul client, we averted this issue in the unified editor by creating a new call number behind the scenes and transferring any items being edited to this new call number. This behavior also came into play when using the 'Edit Items/Volumes Per Bib" option in Item Status of the xul client.
However, there were a lot of complaints about this behavior in bug 1040686. We 'fixed' this bug in the web client, but I think it left us in a place where there is no easy way to update the call number for just some of the items attached to that call number. You can create a new call number and then transfer those items to the new call number, but I wouldn't call this workflow easy when compared to the old way of doing it in the Unified Editor.