Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><a href="http://www.zuschlogin.com/?p=40" rel="nofollow noreferrer">A disabled option tells the user</a>:</p> <ul> <li><p>The action is possible. </p></li> <li><p>Just not right now. </p></li> <li><p>But the user can make it possible.</p></li> </ul> <p>Unless there is some simple action the user can do to change his or her rating (e.g., by selecting some other controls in the same window), do not use disabling and do not show the offers. Disabling may confuse some users who will then hunt around the window for something to do to enable those offers. It’s a great idea to use a tooltip to explain disabled objects, but that’s not a standard and not all users will think to hover the mouse over a disabled option (Why should they? It’s disabled).</p> <p>Including offers users can’t have, even when disabled, clutters your display, forces more scrolling, and distracts the users from the offers you actually want them to consider. Furthermore, showing unavailable offers can come across as taunting (“ha, ha, your rating isn’t high enough”) and may diminished the perceived value of the available offers by comparison, resulting in lower user satisfaction. </p> <p>It seems unlikely to me that users are going to go around comparing the offers on their windows, but maybe you have user research saying they do. In any case, you should label the list of offers to make the criteria clear (e.g., “Offers available at your rating” may be sufficient). </p> <p>If you want to encourage users to increase their ratings, then maybe include something advertising the benefits of an improved rating. For example you could have a link "-Improve your rating- by four points and get -five additional offers-." The first -link- tells users how to improve their rating, while the second lists the offers as a motivator. The latter link should only be there if the offers will still be available if the user actually succeeds in getting four more points.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow should I display invalid options?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMichael Zuschlag
    1. USMichael Zuschlag
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow should I display invalid options?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COFirst of all, very nice link and also a very nice explanation. In my case, increasing the rating is a good thing but usually results in less offers. Also, often users create an offer (they can do that) specifically for another user and may set the rating bounds wrongly by accident. In that case, the target user will be confused because he can't find the offer that he was told got created. How would you deal with this situation?
      singulars
      1. PO
      1. USmafu
    2. COHmm. Can you prevent the error at the origin? Maybe if the offer-creating user selects Make Offer to Specific User(s), then the offer is designated to appear available to the target users irrespective of the users’ rating, thus making the error impossible. If you don’t have a feature that allows creating users to specify target users, maybe you need to make one, since that’s one way users are using the product.
      singulars
      1. PO
      1. USMichael Zuschlag
    3. COThat's a good advice. That you very much for your answer and the insight!
      singulars
      1. PO
      1. USmafu
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload