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

Search by Rig #1910

Closed
ThomasHalland opened this issue May 24, 2023 · 1 comment · Fixed by #1962
Closed

Search by Rig #1910

ThomasHalland opened this issue May 24, 2023 · 1 comment · Fixed by #1962
Assignees

Comments

@ThomasHalland
Copy link

ThomasHalland commented May 24, 2023

User story: [User can select to search by rigs instead of by Wells]

As a USer
I want to find all the wellbores drilled by a Rig
so that I can work on the dataset in Rig Context

Acceptance criteria

  • User shall be able to change search criteria from Wells (today) to by Rigs.
  • List all well/wellbores when entering parts of rig name in search bar
  • The results shall still be a listing of the wells (so same hierarchy as "usual")

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

  • UX: Can the generic search bar be used, only that you select that you want to search for RIG instead of the default WELL, or do we need an additional attribute where the user defines what he wants to search by.
  • UX Should should implemented so that it can be further extended in the furture. if you want to search using other contexts (e.g Field, Service Company, etc...)
  • Wildcard support.

Resources

  • Lead resource: [name/company]
  • Contributors: [list names/company]

image

@janburak
Copy link
Contributor

janburak commented May 30, 2023

Name filtering should reuse wildcard functionality from #1917
One would most likely have to fetch all rigs in api and the filter on name there (double check with WITSML api spec).

One way to solve the issue, without increasing the load when connecting to a WITSML server in frontend, would be to fetch all rig names only when the user picks the "Rigs" option from the dropdown. Some feedback should be given to the user to indicate that rigs are being fetches, such as for example reusing WellProgress in both the sidebar and the content view. The fetched rigs-well-wellbore mapping should likely be saved separately in the NavigationState.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants