Child pages
  • Priority VS Order terms
Skip to end of metadata
Go to start of metadata

Imported From: http://groups.google.com/group/in-portal-dev/browse_thread/thread/642e052b0a65d98c#

In-Portal has Priority column in tables, which data is displayed also on Front-end. This allows to position data in any order, no matter what sorting user has specified. I personally like Priority term, but according to Dmitry's input about user experience it seems, that "Order" term would be more appropriate. 

As a temporary measure we changed translation of "la_col_Priority" and "la_fld_Priority" phrases to "Order" to solve that problem.

Now, when I really need to have column/form field named "Priority" I see "Order" instead. If "Order" term is no longer needed, then I propose to revert that change. If it's still needed, then appropriate "la_col_Order" and "la_fld_Order" phrases should be added and used, when appropriate.

Related Tasks

INP-1667 - Getting issue details... STATUS

26 Comments

  1. Hi Alex,

    Yes, I agree we should revisit this topic and decide where to use one
    and another and make final changes to the Language Labels.

    One of the reasons for this was to have Order term in Catalog where
    it's MORE intuitive in terms of "ordering" the Sections in the Menu.

    I'll talk to our project managers here to see what they have to say
    about this since it was their initiative to do this for User
    Friendliness purpose.

    DA

  2. Hi guys,

    I'm also for using "Priority" because:
    - "Order" word by itself is also part of "in-commerce" lexical field
    - Priority sounds more intuitive to me, the only missing part is a
    contextual help (because highger priority means a lower number)

    I'll open another post  about admin interface, after having reviewed
    other CMS, we really miss an intuitive interface, mainly made of "?"
    hints, to have "on the fly" help when we need.

    p.

    2010/12/12 Dmitry A. <dandre...@gmail.com>:

  3. *- Priority sounds more intuitive to me, the only missing part is a
    contextual help (because highger priority means a lower number)*

    I use negative numbers to get around that. But positive number would be more
    intuitive of course.

  4. this is not a problem itself if we have a clear help about that.
    Also we cannot use negative numbers now, because Order field is a dropdown :)

    2010/12/12 Alexander Obuhovich <aik.b...@gmail.com>:

  5. For categories/section, yes, it's now automated there, since categories now
    represent Front-end menu too.

    For other pages, like language list and link list it's still input text.

  6. right :)

    2010/12/12 Alexander Obuhovich <aik.b...@gmail.com>:

  7. I actually do agree with Dmitry that Order is a better and more intuitive
    term.  From my experience working with customers Order makes more sense to
    them and I had customers ask me what "Priority" means.

  8. However order also means customer order in In-Commerce and that's very
    confusing and especially for translators.

    On Wed, Dec 15, 2010 at 8:25 PM, ky4ep <and...@ky4ep.com> wrote:
    > I actually do agree with Dmitry that Order is a better and more intuitive
    > term.  From my experience working with customers Order makes more sense to
    > them and I had customers ask me what "Priority" means.

  9. I propose "Display order" or "Display Priority". Why should we stick on 1
    word?

    2010/12/15 Alexander Obuhovich <aik.b...@gmail.com>

  10. I believe we just have to have 2 separate words as Alex proposed in
    the beginning:

    Phil, I see NO problem with using 2 words, but it make it quite long
    considering we have 2 digit number there...

    Listing Order & Listing Priority - can be used as Sorting HINTs when we
    mouse over the Field to change sorting?

    DA

  11. if we think about putting hints, then we don't have anymore problem, nowhere
    ! I'm awaiting to have hints I could translate :)

    2010/12/16 Dmitry Andrejev <dandre...@gmail.com>

  12. Putting hints for grid columns is a big problem actually. Dmitry just added
    "Sort By " words in front of each column.

    Sadly, but phonetically it work only in English. When Russian language pack
    is used, then all looks pretty strange. Maybe hint like *Sort By
    "<FieldName>" *will be more usable in other language packs, then *Sort By
    <FieldName>*, that we have now.

  13. Hi Alex,

    Can you please list the most problematic *Sort Bys* here so we can review
    and discuss the options?

    Thanks.

  14. I think that this should be globally renamed back. There are no specific
    place. I just think, that old "Priority" term is more descriptive.

    On Mon, Jan 3, 2011 at 6:59 PM, Dmitry A. <dandre...@gmail.com> wrote:
    > Hi Alex,

    > Can you please list the most problematic *Sort Bys* here so we can review
    > and discuss the options?

    > Thanks.

  15. I guess, let's define which parts of the system MUST have it named *Order *and
    we can change the rest to *Priority *term.

    Do agree on this?

    DA

  16. personnally I'd prefer a single term for the same action, not depending
    where it happens.
    I'd suggest to create hints for column hearders, where we could place few
    words.

    2011/1/3 Dmitry A. <dandre...@gmail.com>

  17. Hi Phil,

    Thanks for suggestion, can you please include your example (actual working
    here?)

    Thanks.

  18. like "alt" value popup, but in a nice way, just like all those rounded
    " ? " we see everywhere by now. This is an :hover contextual help

    2011/1/4 Dmitry A. <dandre...@gmail.com>:

  19. Phil, it's a problem to add "?" everywhere as you described this - at least
    in current Interfaces.

    I have reviewed this again and I have the following thoughts:

    1. *Priority *term WON'T work for us. Priority is NOT a number rather a type
    - normal, urgent, immediate. This means it's NOT a good terms for this role
    in my opinion
    2. *Order *term WON'T work for us. Order terms is TOO common and while it
    can be translated as Default order

    I have reviewed another web cms and found that instead of Priority or Order
    we can use: Sort. term or similar. Please keep in mind that in the end we
    are specifying Default Sorting by a number in this field.

    As to changing Alt text for the fields, I can recommend:

    Sort by: Default Sorting
    Sort by: Name
    Sort by: ANY Field

    I know Alex was against it, but I have checked in Russian too. It would look
    like:

    Сортировка по: Имени

    Let talk this through so we can conclude and start with this implementation.

    DA.

  20. *I have reviewed another web cms and found that instead of Priority or Order
    we can use: Sort. term or similar. Please keep in mind that in the end we
    are specifying Default Sorting by a number in this field.*
    *
    *
    Since both terms don't fit, then what should we do?

    *
    *
    *Сортировка по: Имени*

    This won't help, since phrase for name is called "la_col_Name" and it's
    translation in *nominative case* is "Имя" (and you have used *genitive case*),
    so it becomes: "*Сортировка по: Имя*". This doesn't sound right. Adding
    another phrase just for alt on each column isn't an option too.

  21. about "?", we don't need to have a character, a simple hover on the
    column title could also dispaly the hint; very easy and very
    user-friendly, if before clicking on the column title you know what it
    does .

    the real function is "Display Order", is it too long?

    2011/1/17 Alexander Obuhovich <aik.b...@gmail.com>:

  22. Hi guys,

    I propose the following:

    *1.* In Grids change *Order* / *Priority* term to *Sort. *- yes it might
    sounds a little strange, but after all we define the Default Sorting - which
    would be the number and not a terms, plus it's 100% clear. If you look at
    the Synonyms of Order - it has more than 40+ which means it's confusing in
    any case. Priority is okay, but can't be a number by definition.

    *2. *In Grids when you mouse over the Sort. term or any other term you see
    "Sort by: Name" or "Sort by: Default Sorting". This means that we might need
    to add the ability to specify different terms for sorting hint. The reality
    is that I saw at least 2 times users (mostly clients) asking what these are
    for and why it says the same as text above. In other words, it's NOT 100%
    clear to all of them. For us - yes, we know this with closed eyes, but since
    it's simple to implement I vote for this.

    About issues with having separate label option for Russian Users - I think
    most of them will understand how it works even without doing it, but I would
    add this option for those who really need it.
    *
    *
    *3. *On Add/Edit form have it say "Default Sorting".

    I am just trying to explain where I am coming from with this ideas.

    DA

  23. Dmitry, thanks for summarizing, I'd just say that the :hover text label
    should be more explicit than just 2 words, and I'd recommend this :hover
    contextual in all column titles

    2011/1/17 Dmitry A. <dandre...@gmail.com>

  24. How about "Sorting" in the grid? "Sorting", not "Sort".

  25. Each column in grid on hover shows "Sort By Is Favorite", where "Is Favorite" is that column title. If we name column "Sorting" instead of "Priority" then hover text would say "Sort by Sorting", which is even more confusing.

    Historically we have named column "Priority", because it was empty by default and by putting a number in there a particular record in grid could be promoted/prioritized very easily. Over time some Priority columns started to work more like "Order" columns because:

    • there is no way to put empty value in them
    • all records have ordered by that column
    • actual order is picked from dropdown rather than entered by hand

    When creating a new grid it might not be obvious at first what sorting it will use (manually entered Priority or Order selected from dropdown) and therefore I propose:

    1. always name db column as "Priority"
    2. use "la_fld_SortingOrder" phrase (translation would be "Order") where value is selected via dropdown (the phrase label is picked to avoid confusion, when used in In-Commerce)
    3. use "la_fld_Priority" phrase, where value is entered by hand
    4. review existing grids/editing forms and use one or another phrase appropriately
  26. Found 27 units, where Priority field is used. Not sure which of them actually use "Priority" field as "Order" field.