Creating the concept of a dataset within the application

[J-avery32]

Purpose

The purpose of this feature is to create the ability to import spreadsheet data (either through copy/paste or uploading spreadsheets). We should also be able to plot the data using different charts. This should then be able to be saved to the server.

Design thoughts

We will probably use plotly in tandem with x-spreadsheet. The save button will need to save the spreadsheet to the server in some sort of JSON format. In this JSON document the key data is meant to reference this data. We should probably use a 2 dimensional array to store this data. There will also exist a config key which will hold an array of objects that hold the configurations for the types of plots we have created associated with the data.

Finally, we also need to mirror the UI flow we have for when there is a conflict in etags that we have for the pages editing.

[dylanmcreynolds]

Since submitting, this issue has had a lot of discussion. I can see implementing this in phases.

Requirement

I think I might restate the purpose here as

• allow users to easily import tabular data (as in copying from google sheets / excel and pasting into form)
• once stored, give users the ability to view the data in a table
• where possible, give users the ability to construct a plot of the table

Iniitial Phase

• a text area that allows paste from excel/sheets
• when the user pastes, display the data in a table, optionally allowing them to identify the first row as a header
• attempt to create a line plot of that data...figuring out how to identify axies and labels
• a text field to provide annotations (what is this data, why is it important, etc.)

Future Phase

• more chart types
• allow users to edit in an online sheet editing tool (like ag grid

Access

I think this needs to be thoroughly thought out, but a proposal:

• the collections we store here should have a field in splash_md (called "accessGroups") where that stores the group or groups that can see these new documents
• by default, only the user who created the document can see or edit
• once the user has given access to a group (like, say, the whole MWET team is a group), then others can see it...but nobody else can edit anything about it.