searchx-framework / searchx-frontend Goto Github PK

A new version of Bootstrap has arrived, so we'd like to migrate and make collaborative features using Cards https://react-bootstrap.github.io/components/cards/

However, Material-UI has become popular in today's web applications. To make users feel more comfortable with the tooling, we may take into consideration migrating SearchX to Material-UI.
This also requires to port our survey engine to the new styles.

Add a button allowing the user to claim completion of the task. The button should redirect to a post-search website (this website should be in the configuration of SearchX).

course_id etc

Currently when a user finishes with incorrect code, the resulting code is undefined. This would not be nice when a user wrongly writes their user code.

Currently each search task is "hardcoded" to work. Since we want to make searchx easily adaptable for a new task, we would need to create an abstraction that would make this achievable.

I found the following points that I think could be improved when going through the instructions.

• The documentation of searchx-front jumps to configuring the backend URL, without explaining that you have to run searchx-api first. This was clear to me, but may no be to a new user. It would be helpful to link to the other repo for instructions on setting up the API.
• After running the development server, the documentation does not explain at what (default) url the user can visit the server. The output of webpack does link to http://127.0.0.1:8080/, however that only shows the about page, so I had to look through the code to find the URL for the search. It would be helpful if the URL where the user can try SearchX is in the documentation, and if the about page links to the search page (or the search page is made the default page).

Hi,

Can you add in some functionality to log the event when a user CLICKS on the query box (focuses on it)? That way we can better time how long someone spends querying.

In addition, can you check to make sure that there are events in place for subsequent interactions on the SERP?

• Add a logging event for when a bookmark is deleted from the saved list. For a collaborative session, this event should note the user ID of the person who deleted it.
• When a user hovers over a widget (and out), can you have events to track that? Like, the parent container should have an event associated with it. At the moment I believe there are events in place that consider when individual elements within a widget are hovered over (i.e. hovering over a document in the saved documents widget), but an overall hover in and hover out for the container box would be awesome.

Thank you!

Check if we can use puppeteer for integration tests.

For collaborative search tasks

• preferably something that is pluggable like facebook chat

Currently the verticals are hard coded in the frontend. It should be changed to be editable on the backend to reflect result types from the search provider.

I cannot reproduce:
Sometimes two instances of Chat appears for user, when that may occur?

Bring intro back. Add intro messages in:

• SearchTaskBar, intro explains the user subject to learn.
• SearchTaskBar, intro explains the counter and the time limit (counter should start after intro is completed)
• SearchBox, explains that it is a normal search system

Issues:

• The use of localstorage is very messy and spread out everywhere
• localstorage should not be used for sensitive data (user code, etc)
• There are different types of stores. Component stores, and global stores
• The current library (flux) is very loosely defined, therefore it's easy to implement bad practices

Possible Solution:

• Adopt a newer state management library which solves the issues in flux (ex: redux, mobx)

Currently users are only identified by a color. To implement additional features regarding user information, we need an id / username to refer a user with. This can be through a prompt in the beginning of a session.

With the username information, we can then implement:

• listing which group members are online
• display information on which users have viewed/rated a document
• etc

Videos use youtube links.

Currently container components and presentational components are separated in the search directory. To ensure the components are receiving the correct props, we should define prop types for at least the presentational components (inside the components directory of each feature).

The button should appear after counting limit.

Add a taskbar on the top right with information about the task. A task id should be part of user current state. It should support getting the task definitions from a file (maybe Json) containing task idand definitions. The filename should come from the configuration file.

We should support logging this interaction.