Skip to content

DIVE Update (3/10/16 - 3/17/16)

Compare
Choose a tag to compare
@kevinzenghu kevinzenghu released this 18 Mar 01:34
· 829 commits to master since this release

The latest development version on staging (please use this to test):

Staging: staging.usedive.com. (password: macro)

For access to all projects, login with the credentials (username: admin, password: password)

For any bug reports or feature requests, please e-mail us personally or at dive@media.mit.edu.


[Redesign] Within-project design and structure

DIVE has looked the same for several months now. While it was good to focus on infrastructure and feature development, it's time for a new face. We aimed for a redesign that:

  1. Makes the work flow and structure of DIVE more apparent for new users
  2. Visually separates different concerns (e.g. changing configuration vs. changing entire modes)
  3. Lends itself to an intuitive walkthrough system
  4. Is more visually appealing

We've spent a while thinking through a design that meets these criteria. The structure is: all project-level navigation is on the left (what are you doing), all content-level options are on the top (what do you see), and all configuration is on the right (how are you seeing it). It's not radically different or novel, but we had to change a lot under the hood, which gives us a better base to build from. While there's still more work to do, we're happy to say that this is now what DIVE looks like:

Full project flow
redesigned flow

Dataset Inspection
image

Visualization Exploration
image

Correlation
image

Narrative Composition
image

Next up is to continue iterating on the project pages, and to redesign the landing page.


[Feature] Authentication and Accounts

We've put off user accounts and authentication for a while, but it's finally here! It's a thankless job, and prone to mistakes, but we bit the bullet and now have the base of a secure system implemented. We are associating projects to users with varying levels of access. Users can create private projects and also have access to specific preloaded projects. Preloaded projects themselves are either public or scoped to users.

Full login flow
login

Login Page
image

Registration Page
image

There's still a lot to do here:

  • Implementing access groups
  • Implementing anonymous users that can create projects but must register after a certain point
  • Allowing users themselves to allow access to different parts of their projects
  • Integrating OAuth

Next Up

In preparation for beta user testing in the coming weeks, we aim in the next few weeks to:

  • Allow exporting of analyses
  • Redesign the landing page flow
  • Allow editing projects (name, description, access, etc)
  • Finally include a shareable link to exported visualizations
  • Begin working on a visualization builder

Other items on the docket include:

  • Designing and implementing a workflow for detecting and fixing dirty datasets
  • Speeding up field selection on the visualization page
  • Including more models on the regression page
  • Fixing bar chart axis sorting bug
  • Allowing users to export visualizations with configuration and conditional changes
  • Allow users to select the maximum number of points shown on scatterplots

In terms of use cases, we're really looking forward to working with the full clinical dataset, and possibly build bespoke visualizations.