qdrant-web-ui
qdrant-web-ui copied to clipboard
[Web-UI] UX visualization improvements
The Web-UI (http://localhost:6333/dashboard#/collections/<collection>/visualize) is very useful for quick exploration of a collection.
However, the UX might need some minor improvements. I guess that the most common use case is free exploration i.e., you take a look at your points and see which topics seem to form some kind of cluster. By doing so, currently when you hover over the points, first the raw JSON is displayed. Displaying the embeddings here is not needed.
When you click on the point, an overlay appears in a nice tabular format. The embeddings are hidden by default.
I think what would be better suited is an integration of the overlay table in the right side bar as there is lots of available space. Maybe two tabs would be good, one for the request and one for the point info?
If the tabular format was displayed for each point on hover in the right side bar, one could much easier explore a collection.
Anyway thanks a lot for providing the tool - much appreciated! :)
The embeddings are not visible for me on hover, only the payload. Are embeddings part of the payload in your example?
Yes indeed they were - thanks for the hint! The JSON overlay looks already much better this way. The only problem I have with it - especially when you have overlapping points - is that you sort of lose track of either the mouse/point you queried and the meta info you're interested in, e.g. the title as the overlay "jumps" up/down when there is more than one entry.
Yes, your solution is definitely cleaner. When selecting a point, we can highlight that point in the visualization and a table in the sidebar can show the info of the selected/highlighted point.
I don't want to feature creep but that would also allow for a possible future batch selection with the mouse, e.g. drawing a rectangle/free polygon and selecting all points within. I think such a feature could possibly be useful when you'd like to create topic clusters manually. Based on the clustered points you could calculate an average embedding and then have some ground for automatic classification. Maybe it's going too far however.
A bit off-topic but is there a way I could somehow export the 2D-coordinates along with the metadata? I guess all the variables/processed data are kept isolated in the worker.js right?
I would like to visualize the data in a different tool for some tests.