Revise frontend based on Dan's suggestions

[istwu]

Dashboard (rename to Home?) (pushed to next semester)

• [ ] link to query page
• [ ] page/section for saved queries (persistent)
• [ ] create display for statistics about overall database (eg records added in last 24h, total records added, etc)
• [ ] add charts, cumulative numbers

Results (pushed to next semester, a lot of it relies on backend/AI teams)

• [ ] each query should have title, url, source time (all clickable), NLP/ML generated synopsis, actor, latitude/longitude,
• [ ] create filter/sort by for time, lat/long, number of actors, etc
• [ ] add feature to select rows and save articles into workspace
• [ ] generate query id based on query itself (hash title)
• [ ] search widget?

Workspace(s) (pushed for next semester)

• [ ] make them unique for every user; each user can have multiple workspaces
• [ ] users can make, rename, edit, delete
• [ ] export articles into some form of dataset?
• [ ] incl widgets from results page???

[joegenius98]

Current TODOs:

• [x] Separate MVP tasks vs. non-MVP
• [x] Create issues/sub-issues for MVP tasks

[joegenius98]

Notes from meeting with frontend on 11/2/2022:

Vision for MVP: pagination, add columns to the synopsis, make the home page a bit more aesthetically pleasing (e.g., replace placeholder text), (maybe) add filters for search results (by date, query, name, authors)

Notes: Pagination for the frontend & backend. Pagination is about having different pages so that the sources and results are split up on other pages.

Map and adding latitude, longitude data can also be done for later. We could implement basic sorting for now—sort by date, query, title, etc.

So, the querying in the backend is done alright; it's just that the frontend needs to increase its pagination size so that all the results are actually displayed.

"Show only selected ones" for next month, which won't be useful until workspaces are implemented.

Dashboard widgets can be implemented later; for now, we can just put in a description of how to use SCOPE.

Dan wants "queries" and "results" to be buttons you can click, instead of just "queries" now.

Placement of the button for the "GitHub" maybe.

Look into pagination for the backend -- when a user enters. a new page, should a new request be made to handleSubmit or not? Response from backend -- a request to handleSubmit should not be made. Once the backend serves data to the frontend, that should be a once-in-all-done task. The frontend should be able to filter out that data, and therefore be able to separate that data into pages, using the paginated backend-retrieved data.