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

Match Deployment/Receiver statuses with the ETN statuses. #28

Open
4 tasks done
Tracked by #22
aubrivliz opened this issue Nov 14, 2022 · 7 comments
Open
4 tasks done
Tracked by #22

Match Deployment/Receiver statuses with the ETN statuses. #28

aubrivliz opened this issue Nov 14, 2022 · 7 comments
Assignees

Comments

@aubrivliz
Copy link

aubrivliz commented Nov 14, 2022

The Status are being reviewed by OTN. The status names are going to be updated.

  • Update status names
  • Create mapping OTN - ETN
  • Add status definitions
  • Add extra field in deploy layer to hold ETN statuses
@aubrivliz
Copy link
Author

The status imported by ETN from OTN (free text fied):

  • "caught"
  • "failed/lost"
  • "failed"
  • "moved/lost/found"
  • "found"
  • "lost"
  • "lost/found"
  • "moved"
  • "failed/found"

In ETN we have (fixed list):

  • "Active"
  • "Avalaible"
  • "Lost"
  • "Broken"
  • "Returned to manufacturer"

Proposal for OTN to create a fixed list for the status similar to the ETN fixed list.

@aubrivliz aubrivliz changed the title Deployment statuses are still hard to match with the ETN deployment statuses. (more info needed) Deployment/Receiver statuses are still hard to match with the ETN statuses. Nov 16, 2022
@aubrivliz aubrivliz changed the title Deployment/Receiver statuses are still hard to match with the ETN statuses. Match Deployment/Receiver statuses with the ETN statuses. Nov 16, 2022
@diniangela
Copy link
Collaborator

diniangela commented Sep 7, 2023

Potential mapping:

  • caught --> Available
  • caught/found --> Available
  • caught/lost --> Lost
  • caught/lost/found --> Available
  • caught/moved --> Available
  • caught/moved/found --> Available
  • caught/moved/lost --> Lost
  • closed --> Available
  • failed --> Broken
  • failed/caught --> Broken
  • failed/found --> Broken
  • failed/lost --> Broken
  • failed/lost/found --> Broken
  • failed/moved --> Broken
  • found --> Available
  • lost --> Lost
  • lost/failed --> Broken
  • lost/found --> Available
  • lost/moved/found --> Available
  • malfunction --> Broken
  • moved --> Available
  • moved/found --> Available
  • moved/lost --> Lost
  • moved/lost/found --> Available
  • turned off --> Available
  • null --> Active
  • y --> Available

@diniangela
Copy link
Collaborator

diniangela commented Sep 21, 2023

Definitions of ETN receiver status:

  • "Active": receiver in water (null for us)
  • "Available": receiver out of water
  • "Lost": receiver is lost
  • "Broken": receiver is broken
  • "Returned to manufacturer": receiver has been returned to manufacturer

@diniangela
Copy link
Collaborator

Add an extra field with the ETN receiver status definitions

@jdpye
Copy link
Collaborator

jdpye commented Jan 19, 2024

Metric: Re-import and then check that this is working using BTN and STRAITS

@jdpye
Copy link
Collaborator

jdpye commented Jan 19, 2024

TODO: what's going on with BTN, we don't have actives either from them right now.

@diniangela
Copy link
Collaborator

diniangela commented Jan 23, 2024

Added mapping to the OTN Geoserver layers to make more similar to ETN statuses

Feel free to re-pull and let me know if it works

@diniangela diniangela assigned CLAUMEMO and unassigned diniangela Jan 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants