upquark / newsfreq Goto Github PK

Currently QueryStrings are supported for single variable searches, nut not multivariable. Any query should be able to be represented as a QueryString.

Some infrastructure already in place.

Weighting will work as follows:
Main ajax request for article count is sent. If 'weighted,' then a second request is made for the same time frame and source but with a blank searchTerm. This is the total number of articles for that time frame from that source. The weighted result will be equal to (number of articles for term) / (number of articles total) displayed as percentage. This will be reflected in both graph and table.

Possibly implemented by clicking the name in legend, or adding some sort of "x" out button adjacent to labels.

Add an additional major UI element for auto calculating basic figures such as average article count, % growth rate, and relationship between variables. Somewhat dependent on weighting.

Nebulous task. At the moment, datasets are created with one HTTP request per data point (two for weighted, potentially more for parent company searches). This causes severe slowdown at higher volume which directly affects the usability of the application.

Analysis is needed to see if it is possible to lower the volume of HTTP requests while still extracting all the same data. This is difficult due to the restrictiveness of the backend, but warrants analysis.

Includes major refactor of "draw" methods into objects corresponding to major UI elements, and encapsulation of methods and data to remove it from global namespace.

For the purposes of enabling sharing, a "link" or "share" type button that generates a link with QueryString for the currently displayed dataset should be added.

Uses OOP-Refactor branch. Major overhaul of structure to conform with object-oriented-JS style for better improvability in the future.

Simple UI enhancement to associate the submit / add variable button with "Enter" key listener.

Add a button / option to save the table data set as a .csv or .xslx file. Low priority due to the existing ease of pasting html table into excel, but improves ease of use.

Add a question mark onHover help tooltip for each major UI element as already exists for "search types/increment"