🎛️ Admin dashboard UX improvements

[JGreenlee]

Some takeaways from an informal user interview with a program administrator.

A very common use case for program administrators is to inspect the trips taken by a particular user and see which trips were labeled vs. not labeled.

The current flow is not ideal, as the program admin must first use the UUID table to look up the user's user_id by their user_token. Then they switch to the trips table; but since there's no way to filter, they have to sort by user_id and then go through pages and pages of entries until they get to the trips for the user they're looking for.

We see 2 main things to improve this flow.

• Add user_token as a column to all tables. Anywhere user_id is shown, we can insert a column for user_token.
• Add some way to filter the tables by user_token and/or user_id. -- Perhaps ideally, a generic search bar that works on all columns and only shows rows that have the search text somewhere in that row. I think this would be beneficial in a lot of other use cases as well.

[JGreenlee]

Some specific feedback from this user:

It would be helpful if the trip table could include a user token column to find participants easier.

If I could sort by user token in the trip table that would be fantastic.

The Bubble and heat maps don’t work. Are they a work in progress?

(I explained that they don't show when "Modes" dropdown has no selection; we should initialize it to "All modes")

Not all of the participants are included in the drop down box. Is there a way to add them or is there a reason they others do not show up?

Using the map function, when I query the mode for a participant, and then select, for instance, “Unlabeled”, lines are showing up in Florida.

(I asked if it would be better to initialize the map zoomed-out, such that all data is within the initial render area)

[JGreenlee]

After recent changes to OpenPATH and some more feedback we've received:

• Add BLE sensed mode as a filter criterion in the "Maps" page
• Show responses to surveys other than the Demographics survey on the "Data" page

[JGreenlee]

• Instead of just "exclude test users", we want to be able to actually filter specific subgroups (like test, default, or whatever subgroups are in the config)