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

New Task: Update deployment start/end dates in portal when updated in ADR #109

Closed
3 tasks
iwensu0313 opened this issue Oct 22, 2024 · 2 comments
Closed
3 tasks
Assignees
Labels
duplicate This issue or pull request already exists

Comments

@iwensu0313
Copy link

iwensu0313 commented Oct 22, 2024

Who is requesting this?

ATN DAC original funders, manufacturers, & data contributors

What is being requested?

Deployment start and end dates from the hardware by default include times when the equipment is out of water. We need to fix the deployment visualizations in the portal so that they only show the data and location tracking for the periods when the equipment is actually in the water.

What is the requested deadline and why?

No response

What is the current status quo (i.e., what happens if this does not get done)?

If this is not done, users will continue to see data and tracks before and after the equipment is actually deployed in the water, which can cause confusion.

What indicates this is done (i.e., how do we know this is complete)?

Deployment visualizations accurate align with the start/end dates manually inputted in the ATN DAC Registration portal, which should reflect the actual dates of deployment.

  • Enable ATN DAC Registration (ADR) to speak with Axiom data ingestion system
  • Implement time slicing in Axiom data ingestion system based on ADR most up-to-date start/end deployment metadata?
  • Re-run deployments after system changes have been implemented and tested?

NOTE: I need to update the specific steps in this section after confirming with our engineers that this is still the best proposed pathway.

Provide a description or any other important information.

No response

@iwensu0313 iwensu0313 self-assigned this Oct 22, 2024
@iwensu0313 iwensu0313 converted this from a draft issue Oct 22, 2024
@MathewBiddle
Copy link
Contributor

Sometimes there are glitches in this wild internet world. Looks like GitHub created two issues at once.

This is a duplicate of #110?

@iwensu0313
Copy link
Author

iwensu0313 commented Oct 23, 2024

Oops sorry about that I will close this one!

@iwensu0313 iwensu0313 closed this as not planned Won't fix, can't repro, duplicate, stale Oct 23, 2024
@iwensu0313 iwensu0313 added the duplicate This issue or pull request already exists label Oct 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants