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

add new vespawatch db dataflow #123

Open
SanderDevisscher opened this issue Apr 16, 2024 · 6 comments
Open

add new vespawatch db dataflow #123

SanderDevisscher opened this issue Apr 16, 2024 · 6 comments
Assignees
Labels
automated workflow enhancement New feature or request

Comments

@SanderDevisscher
Copy link
Collaborator

SanderDevisscher commented Apr 16, 2024

When the new vespawatch db is ready w'll need to replace iasset part of the dataflow.

  1. disable the iasset dataflow
  2. work out the mapping for the new vespawatch db
  3. integrate the mapping into the existing automated dataflow
  4. test the modified dataflow
@soriadelva
Copy link
Contributor

This is done already in issue #124

@soriadelva
Copy link
Contributor

I'll add more info after the PR is merged and the new version can be uploaded.

@SanderDevisscher
Copy link
Collaborator Author

@soriadelva this concerns the switch to the dataflow from the database (inclu. frontend) currently under construction to replace iAsset. What you are talking about is the modified flow from the iasset db (+gbif + old vespawatch db) 😉.

@soriadelva
Copy link
Contributor

@soriadelva this concerns the switch to the dataflow from the database (inclu. frontend) currently under construction to replace iAsset. What you are talking about is the modified flow from the iasset db (+gbif + old vespawatch db) 😉.

aaah 😅

@soriadelva
Copy link
Contributor

@soriadelva this concerns the switch to the dataflow from the database (inclu. frontend) currently under construction to replace iAsset. What you are talking about is the modified flow from the iasset db (+gbif + old vespawatch db) 😉.

aaah 😅

Not fixed in 5 min unfortunately 😬

@SanderDevisscher
Copy link
Collaborator Author

@soriadelva this concerns the switch to the dataflow from the database (inclu. frontend) currently under construction to replace iAsset. What you are talking about is the modified flow from the iasset db (+gbif + old vespawatch db) 😉.

aaah 😅

Not fixed in 5 min unfortunately 😬

nope 🤣

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automated workflow enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants