Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Well object - extend support to read "all" witsml well properties in frontend #687

Closed
2 tasks
marmid74 opened this issue Sep 23, 2021 · 3 comments
Closed
2 tasks
Labels
Not prioritised UserStory Highlevel userStory(Epic)
Milestone

Comments

@marmid74
Copy link
Collaborator

marmid74 commented Sep 23, 2021

User story: Well object - extend support to read "all" witsml well properties in frontend

As a user
I want to be able display "all" witsml well properties (metadata)
so that I get all the details about the well.

Acceptance criteria

  • A table view of all witsml well properties in frontend
  • Table containes all properties set as required in the Well properties list
@marmid74 marmid74 added the UserStory Highlevel userStory(Epic) label Sep 23, 2021
@Pascal62223
Copy link
Collaborator

I like the idea here and think it would be very useful. The complexity is going to come from both aspect as far as I can see:

  1. UX: I believe the well page (and any other object editor) must kept as simple as possible with the key information being accessed. Any additional property being accessed only on user request. For example through a "Show Advance" option.
  2. Property definitions : Some well property such as CRS are going to be tricky to handle if editing is being allowed. Are all properties going to be editable ? If not, would the editing capability be a configuration that can be set at deployment time ?

@ThomasHalland
Copy link

The idea is good but we stick to the initial idea of the product to focus mainly on functionality which adds value and is based on real Use Cases. Hence we will extend the Well object support with new features as soon as it is demonstrated that somone needs them.

@eliasbruvik
Copy link
Contributor

Closing this as per Thomas' comment. A new issue should be created when we have a use case.

@eliasbruvik eliasbruvik closed this as not planned Won't fix, can't repro, duplicate, stale Jan 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Not prioritised UserStory Highlevel userStory(Epic)
Projects
None yet
Development

No branches or pull requests

5 participants