Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • D Data Definitions
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 8
    • Issues 8
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • 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
  • Open Subsurface Data Universe Software
  • Data Definitions and Services
  • Data Definitions
  • Issues
  • #12

Closed
Open
Created Feb 19, 2021 by Alan Henson@alan.hensonDeveloper

Seeking clarification on trailing required semicolon for reference fields

This issue popped up recently in storing records via the Storage Service. We're seeking clarification on the format of certain reference fields that require a trailing : whereas the id format of the parent record does not have the trailing : requirement.

Example:

  • Wellbore has an id property format of: ^[\\w\\-\\.]+:master-data\\-\\-Wellbore:[\\w\\-\\.\\:\\%]+$
  • WellLog.WellboreID has a format of: ^[\\w\\-\\.]+:master-data\\-\\-Wellbore:[\\w\\-\\.\\:\\%]+:[0-9]*$

If we play out the example as a workflow of storing data, then we might see the following:

  • Create a new Wellbore record via the Storage API
  • The Storage Service creates an id with a value of opendes:master-data--Wellbore:7fc872cca42047f48725adc005f09705, which conforms to the Wellbore.id format
  • Then create a new WellLog record and set the WellboreID value to the id returned by the Storage service (opendes:master-data--Wellbore:7fc872cca42047f48725adc005f09705)
  • Save the WellLog record via the Storage Service
  • The WellboreID property will fail validation as it lacks the trailing :

Question: Should the WellLog.WellboreID format require the trailing : if the Wellbore.id property does not require it?

Link to Wellbore.id schema definition

Link to WellLog.WellboreID schema definition

Edited Feb 19, 2021 by Alan Henson
Assignee
Assign to
Time tracking