Progress as of Nov 28.

[ryanvoyack]

Our group is faced with the remaining preliminary decision of how our app will get its data. Either we have to: 1) make the webapp so that the user can import data of his own

• coding for this would be much more difficult and may impose alot of bugs even after. The user may not have an idea of data structures (in R), and may not know the difference between tidy and untidy data.
• the webapp would have to be able to tidy the data (rename variables to fit our functions, for example) - to a degree - by itself for this to be practical at all. This may be possible if we make the app prompt the user in the tidying process.

2) make the data a part of the webapp

• this would result in a finite amount of companies that the user can access. in practice, this MAY be completely fine, considering motivations for use by the user.
• our webapp will instead have to be coded to deal with large data maneuverability, in that all of said data will probably be in one huge data set. This may effect run time of the app and further code would have to be written (potentially) to combat this problem - as opposed to code that would be written to take and tidy user exported data.

what may effect this decision is:

• questions of applications to the practicality of our app
• limitations in our ability to solve problems that arise with each scenario
• the presence and availability of data online (for us and for the user). this also implies a question of practicality

This issue will be solved by our group tomorrow after class, where I will present these problems and brief investigations of mine into each application. The agreement of this choice is required before our project can move forward.

[ryanvoyack]

( i forgot to write this thursday) We have decided to go with option 2.