-
Notifications
You must be signed in to change notification settings - Fork 7
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
Handling of data ranges #624
Comments
I somewhat disagree. Data amount would grow or shrink, but only if NO RANGE was selected correct? |
Regarding the columns: think you are right, range should not change.
|
In my opinion, the user should perform work on the source file before importing I agree that if no range is selected, the data should extend with the number of rows Does data extension by column make sense at all? I know it's possible to construct such case but do we really need this? |
I think indeed, we don't need this |
During creating of import configuration user can optionally select a data range to be used for import.
For the use case described in #785 (Update of existing observed data) and #622 (import of new datasets based on a given import configuration): relevant data range might grow or shrink in the new data source.
Proposal for the handling in case of update:
The text was updated successfully, but these errors were encountered: