Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • W Wellbore DDMS Data Loader
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 16
    • Issues 16
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

Upcoming Change to GitLab Pages The GitLab Pages URL is planned to migrate from the current *.pages.community.opengroup.org to a simpler domain: *.pages.opengroup.org. At the same time, HTTPS will be enabled for the server. This change is planned for May 21, 2022.

If you have questions or concerns, please email forum-support@opengroup.org.

  • Open Subsurface Data Universe Software
  • Platform
  • Data Flow
  • Data Loading
  • Wellbore DDMS Data Loader
  • Issues
  • #23

Closed
Open
Created Oct 13, 2021 by Chad Leong@chadOwner

Search for ingested wellbore ID to avoid duplicate wellbore record ID

Currently, user is allowed to create a new wellbore record based on the LAS information.

However, there are cases where the same wellbore contains multiple well log files. In this scenario, we do not want to create multiple wellbores that are the same.

This issue addresses the scenario described above by using search API prior to creating a new wellbore record.

  1. Parse LAS for well name
  2. Run search API (api/search/v2/query) to check for ingested Wellbore with a body. E.g. Searching for Wellbore name NPD-2105.
{
   "kind": "*:*:master-data--Wellbore:*",
   "query": "data.FacilityName:\"NPD-2105\"",
   "limit": 100
}
  1. If wellbore already exists, uses that existing wellbore record ID for the welllog reference.
  2. If search returns null, create a new wellbore record ID.
Edited Oct 13, 2021 by Chad Leong
Assignee
Assign to
Time tracking