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

User story: Import log from .csv #174

Closed
4 of 6 tasks
thomash1972 opened this issue Feb 16, 2021 · 2 comments
Closed
4 of 6 tasks

User story: Import log from .csv #174

thomash1972 opened this issue Feb 16, 2021 · 2 comments
Assignees
Labels
High Priority UserStory Highlevel userStory(Epic)

Comments

@thomash1972
Copy link

thomash1972 commented Feb 16, 2021

As a Data Manager
I want to be able to Import log data from a defined .csv file format to a WITSML server in the context of a selected wellbore.

Acceptance criteria

  • on an existing log object , import additional log data from a pre-defined .csv format (same format as Export log user story.)
  • If the import .csv format is not in the correct format, WE will inform me about this without trying to import the data

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

  • The target Log need to exist before importing the data from right clicking on the Log Object
  • alternatively the import function will create the Log if needed (Log name then need to be specified in the .csv file ?
  • Alternatively you could allow the import to be initiated from a generic menu item, but require that the well, wellbore as specified in the .csv must exist, and prompt the user for which existing Log the data should be imported to
  • If a curve does not exists in log, the solution must resolve the datatype upfront. This can be done based on unit. If unitless, the solution must resolve if the datatype is string, numeric or date
  • If a curve does not exists, solution must add values on mandatory properties on curve (datatype, unit, uid?, description?).
  • Witsml servers Datapoint limitation - maximum 10 000 rows for each updateInStore, so .csv with more rows, need to be divided into multiple updateInStore operations.

Resources

  • Development: TDE
  • Lead: Equinor
@marmid74 marmid74 added this to the Import Multiple Logs to .csv milestone Feb 18, 2021
@marmid74 marmid74 added the UserStory Highlevel userStory(Epic) label Feb 18, 2021
@HoldampfIldiko
Copy link

DEV- TDE @aszalos-roland

@marmid74 marmid74 changed the title User story: Import Multiple Logs to .csv User story: Import Multiple Logs from .csv May 12, 2021
@marmid74 marmid74 changed the title User story: Import Multiple Logs from .csv User story: Import log from .csv May 20, 2021
steinsiv added a commit that referenced this issue Jun 29, 2021
steinsiv added a commit that referenced this issue Jun 29, 2021
@marmid74
Copy link
Collaborator

This user story is named VERSION 1, of Import log from .csv. Implemented by TDE Group.
Extended features, named VERSION 2, of Import log from .csv is specified in user story #554

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
High Priority UserStory Highlevel userStory(Epic)
Projects
None yet
Development

No branches or pull requests

4 participants