Backoffice - breadcrumbs

[janequist]

Is your feature request related to a problem? Please describe.

Loss of navigation context and relying on Browser Back button.

Describe the solution you'd like

Breadcrumbs are implemented on the Frontsite, but Backoffice also needs same. Even on Frontsite, going back is non ideal - its similar to the Browser back which does a full refresh of Backed up page. It loses context and goes to the top of start search page. Ideally, if you are going back from the Detail page you'd like to go to the specific search results page and scroll region from which the selection was made. There are a few other issues that may also need to be addressed (such as multi-page skip-jump)

[janequist]

Another problem that I've run into is that certain pages become "not navigable" unless you get out of the current navigation chain. For instance, if we go from Book detail to PhysicalItem detail, then at that point the PhysicalItem search page becomes inaccessible. Of course, there are always ways to work around these issues, but the UX becomes less than optimal.

[FlorianCassayre]

Breadcrumbs are implemented on the Frontsite, but Backoffice also needs same.

I like the suggestion of having breadcrumbs in the backoffice, I completely agree that it would improve navigation.

Even on Frontsite, going back is non ideal - its similar to the Browser back which does a full refresh of Backed up page. It loses context and goes to the top of start search page. Ideally, if you are going back from the Detail page you'd like to go to the specific search results page and scroll region from which the selection was made.

That makes sense (that's how non single page apps work), the current behavior is to reload the search because we don't save the search history.

There are a few other issues that may also need to be addressed (such as multi-page skip-jump)

This is specifically fixed in inveniosoftware/react-searchkit#157 and will be available shortly. The browser back/forward button worked everywhere except for the search.

Another problem that I've run into is that certain pages become "not navigable" unless you get out of the current navigation chain. For instance, if we go from Book detail to PhysicalItem detail, then at that point the PhysicalItem search page becomes inaccessible. Of course, there are always ways to work around these issues, but the UX becomes less than optimal.

Excellent point that we probably haven't thought of. The reason why we blocked the link in the menu is a workaround to another issue but it's most definitely far from optimal.