Q: I am looking for some clarification on best practice for “back to top” links: When should they be used and how? Jakob Nielsen is against them, but this is not a universally held view. They can be very useful for FAQs. What do you think?
It’s very rare that we’d say a particular solution is all good or all bad. In a NN/g anchor links, Nielsen writes:
On the Web, users have a clear mental model for a hypertext link: it should bring up a new page. Within-page links violate this model and thus cause confusion.
But a US government: anchor links in which anchor links were used at the top of the page found the following:
On a long page with a large amount of information, having the content headings as links at the top of the page allows users to click to information directly, reducing scrolling and scanning. In our usability tests, users often got frustrated when they had to scroll or scan a lot to find information. Also important, these anchor links let users grasp immediately what information the page contains.
Based on our own research, anchor links, including “back to top” links, are often fine, where the following conditions exist:
Certain populations, such as the elderly or novice Web users, may have more issues with anchor links. If you have any doubts about whether this is the right solution for your users, test it and see!
One of the unique features of OrientDB is Clusters, which allow you to specify how the data in each class (vertex) is grouped on the physical disc. By creating a separate cluster for each class per tenant, you can physically isolate one tenant’s data from another.
One major drawback to using this methodology is that due to the class inheritance structure you will also need to logically isolate that tenant’s data. This means that you must explicitly include that tenant’s cluster identifier in each query. The added need for logical isolation increases the developmental complexity of this method but allows for additional flexibility.