User story: Copy/Paste Wellbore (inter/multi server)

[thomash1972]

As a RT Operator
I want Copy a complete Wellbore from Server A to Server B
so that I can

• safely edit/fix/enhance the data without contaminating the raw data
• Copy a complete wellbore from a service company source WITSML to my Operator Store,
• Duplicate the wellbore on the same server but change to my Company generated UID etc...
  also I need the ability to change UID if I want to as part of the process

Need both copy/paste and copy to server
Need to be able to pick multiple wellbores from the same well to copy

Acceptance criteria

• Complete dataset for all WITSML objects exists on target server after copy
• Ability to Duplicate a Wellbore on the same Server but with different UID, both on the same Well and different Well

Also, here are a few points that need to be addressed:

• Only WITSML 1.4.1.1
• SOAP

Resources

• Resource A
• Resource B

[janburak]

Would require implementation of remaining WITSML objects as per #1956

[robertbasti]

we need to have a very good report for each step

[robertbasti]

copy could be done to another witsml server or within one server (copy paste)

[robertbasti]

if one object fails, it can continue, but it should be reported and be possible to rerun the failed job

[robertbasti]

we need to make sure that witsml explorer supports copying of all attributes on the source server

[robertbasti]

• copy to same well with the different uid on wellbore or to other wells on the same or other servers with the same or different uid

[eliasbruvik]

After checking what missing objects we have data for on the production servers, we at least need to support Attachments first. After that, we should implement this feature with a disclaimer in the modal before ordering the job that lists the supported or not supported objects. This way the users will know/expect that some objects will not be copied.