nhadlaw
commented
2 years ago So in this example that you gave, when a user moves from Brassicales to Zingiberales, should this history look like: Biota < Plantae < Brassicales < "Zingiberales" (in red)?
Also just to clarify this is the idea you were thinking: A user is at a node, in the navigation history we ALWAYS show the nodes above it and the curr node (in that order) and ONLY show the nodes below it if we traversed them to get to the curr node. For exampe, if the order a user proceeds through nodes looks something like this: Biota, Plantae, Brassicales we should only show these in the navigation. Versus, if a user proceeds through nodes such as Brassica oleracea, Brassica, Brassicaceae, Brassicales then show Biota, Plantae, Brassicales, Brassicaceae, Brassica, Brassica oleracea?
touretzkyds
We want to maintain a clickable navigation history display in the area at the top of the screen where the search box and mode buttons are located. Suppose the user starts at "Collard greens" (Brassica oleracea) and navigates upward three steps so that the current node is Brassicales. (We'll be adding navigation buttons to move around; see #24.) This is what the nav display should look like: we show all the nodes above the current node (easy, since this is a tree), and nodes below the current node if they are on the path that brought us here. So if the user moves to a subling of the current node the downward part of the history will be cleared because we didn't reach that sibling by traveling upward.
So if the user is at Brassicales and they move laterally to Zingiberales, we'll display Zingiberales in red and there will be nothing below it in the history, but we'll always show the nodes above it.
All the concepts shown in the history should be clickable, allowing the user to make that concept the current concept.
This history thing will become more complicated when we start developing a relationship display mode (as opposed to this taxonomy display mode). @deyaliao will help with that.