stale[bot]
commented
2 years ago This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Context
Our users mostly import Flow datasets to Lumen to analyze and visualize. The beauty of this connection is in the update option.
Salim creates all the transformations and visualizations he wants on a dataset. But maybe new data has been submitted. With the update option, Salim clicks on one button and Lumen brings in the Flow data and automatically applies all the transformations and visualizations on it. Effortless.
Opportunity
It is indeed effortless, but Salim still needs to click to update. However, often with Flow data, the data comes in over the course of days, months even (over the duration of a project or programs). This means Salim had to always go back to Lumen to click to update. This is less effortless.
How might we remove the need for Salim to manually update a data if he knows that that particular one will have data coming in over a course of time?
Today we have a task that we can define per specific data to update it daily. We (the dev team) set it up for our users. Could we bring this task to the users? So Salim can define that for this dataset I want the update to be automatically run once a day (maybe even for a set timeframe so we do not update the data if it is no longer needed?)
Why not just as a setting for all datasets to take away the user decision? Because for some Flow dataset the data collection is done and there would not be much to update.
We could track the usage of this change to see how many datasets are being updated regularly from all the datasets to decide if even more automation makes sense.