You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue covers several minor things that need to be done
We should support excel files
Considerations:
Excel files often have multiple tabs, so when a user uploads an excel file we should prompt them for which tab they want to upload the data from
Excel files often have merged cells, or use the first few cells to hold descriptive data rather than data we need, so when a user uploads an excel file they should be shown a summary of the first few rows and then be asked to input the upper left row and column of data that should be ingested
Excel files should be saved in their original forms and as csvs with the data that was extracted from them. Both of these files should be stored under initial_data/
Dev and Prod should be two separate environments
Considerations:
Devs should verify stories in dev, and work with adesca to decide what to send to prod
This issue covers several minor things that need to be done
We should support excel files
Considerations:
Excel files often have multiple tabs, so when a user uploads an excel file we should prompt them for which tab they want to upload the data from
Excel files often have merged cells, or use the first few cells to hold descriptive data rather than data we need, so when a user uploads an excel file they should be shown a summary of the first few rows and then be asked to input the upper left row and column of data that should be ingested
Excel files should be saved in their original forms and as csvs with the data that was extracted from them. Both of these files should be stored under initial_data/
Dev and Prod should be two separate environments
Considerations:
Devs should verify stories in dev, and work with adesca to decide what to send to prod
Dev should have its own database
Verify data integrity