After a meeting with our faculty advisor, we settled on beginning the process of a user study. But, before we can progress with that we have to focus on cleaning up the UI to make sure it is user friendly and consistent, adding more datasets, and establishing a process for our user study.
For the frontend, we compiled a list of things we needed to accomplish before having a testable website. And so we began implementing and crossing tasks off of the list.
[ ] Switching out json printing view with table designed from scratch.
[ ] When removing object from the “black box” selection div. Make sure to remove that object in the “black box” once placed in rank div to represent that the user changed that object.
[ ] Fix Pairwise view for ranking. Remove “Enter object here” on rank div. Add icons for ui.
[ ] Shuffle button
[ ] Search through objects in build
[ ] Submit button in the right of build view and search bar in the middle of the build view.
[ ] Black box border for div containing a…
Addressing the feedback we received last week, my team and I began to redesign the UI.
Firstly, in order to make the functionality of RANKit clearer, we updated the landing page to include a tutorial.
Furthermore, to address the problem of not being able to see the ranking boxes until scrolling down, we redesigned the Build UI such that the datasets is to the left of the ranking box as opposed to the top of.
As this is the last week of the term, we met up to discuss plans for the winter. Below are the list of tasks we need to accomplish. Build view functionality fixesPairwise view dataset pool keeps a copy of the removed objectDataset pool is not preserved between views Rank button should rank only the objects in the specific tab Build view UI fixesOption to pick a view once first landing on the Build viewFix Instruction placement in build view, info buttonExploreRedesign Explore UI such that you can view the attribute weights on ratingOptimizing Explore rendering timeMachine learning s…
The week started off with many ideas swirling about, a couple of tasks that needed assigning, and a lot more questions to answer than was physically feasible to wrap around your head. Yet, despite the confusion, many ideas began to solidify by the end of the week.
Over the summer, our graduate student advisor, Caitlin, discovered an open source tool that has functionality of what my team and I are trying to achieve: Lineup. After diving into the GitHub code, analyzing the paper Lineup:Visual Analysis of Multi-Attribute Rankings, following through the tutorial, and cloning the repository onto our personal machines, we concluded that Lineup would be useful to our project.
From then on, liking the idea of Typescript, but also arguing for t…