Page MenuHomePhabricator

[Story] investigate solutions for items with a large number of aliases
Open, MediumPublic


Items with many aliases (Barack Obama in Spanish for example) don't look good when every alias is on a new line. We need to find a solution for them.

Related Objects

View Standalone Graph
This task is connected to more than 200 other tasks. Only direct parents and subtasks are shown here. Use View Standalone Graph to show more of the graph.

Event Timeline

Here are some quickly drawn alternatives just to have some options. Might want to have one or two options sketched out in more detail (-> edit mode). I really like the Grid option as it uses space most efficiently and the component is very mobile-friendly. Would be kind of a step back- and sideward but had that in mind at some point already. Might be a bit nasty to implement with proper semantics though.

Listeasy to scan due to alignmentrequires most vertical space and may cause losing orientation when there are many aliases
Floating (Boxes)all aliases are visible within little amount of vertical spacenot easy to scan
Collapsedflexible (threshold may be set via some setting)rather awkward to use
Scrollableflexible (threshold may be set via some setting)awkward to use
Gridefficient use of space, very mobile-friendly, very flexible in terms of Entity header changesrather uncommon layout arrangement though very contained in that use-case
Horizontal Tablegood scan quality, mobile-friendly, very flexible in terms of Entity header changesinformation overhead (repetition of labels)

Other ideas:

  • Horizontal table with headers in the left column (below language, maybe right-aligned)
  • Horizontal table without the headers at all

Why is the description between aliases and label? To me it seems like aliases and labels are of the same kind, just different weight. I can also imagine something like this:

Schöneweide (also known as Schweineöde, Da bei der HTW, Berlin-Schöneweide )

Ein Stadtteil von Berlin

Probably bad for editing, though. Collapsed and Scrollable is not nice for editing, too.

Oh, sure, aliases position is wrong.

+1 to what @adrianheine suggested, but I would modify it like that:

also known as Schweineöde, Da bei der HTW, Berlin-Schöneweide

Ein Stadtteil von Berlin

Added a few more alternatives. It would be good to have as few redundant information as possible. Consequently, I am not in favour of repeating "also known as" in every section. How aliases are separated visually (boxes, pipes, considerable amount of white-space etc.) should probably not be defined yet although there are some alternatives in there already. The first outcome should be the sole arrangement of language, label, aliases and description.
I kind of like the direction Adrian was heading into and tweaked it even more resulting in the bottommost mock-up. Actually, the term "aliases" in particular is kind of misleading (explained at Aliases, in fact, are alternative labels. One could even argue that the implementation of label should be a list rather than having separate aliases. That's another story though.

Stuff I wanted to write down for quite some time regarding that subject in general:

Thanks for making those!

I think we should narrow it down to:

  • floating
  • traditional piped
  • no aliases, just labels

Potentially also (but not super convinced):

  • collapsed
  • grid

I am quite strongly against splitting the label and description by the aliases. The label and description together establish the identity of the item, whereas the aliases (which is indeed a bad term) are used to facilitate finding the item. No further meaning should be associated with these things.

The label and description are a semantic unit, whereas the aliases are outside of those. Aliases are not just more labels for the entity, or alternative labels. Instead, aliases are meant to help with the search, but not for establishing identity. E.g. 'George Bush' might be a decent alias for Q207, and the description could be 'US president', but it would not be a good label because label+description do not establish identity in that case. The alias is only there because we assume that users might search for 'George Bush', and then can select between the relevant items based on their actual label+description.

So, please put the label and description together again. This is also how it works in the entity selector (for good reasons), and this visual unity also sells the concept of the label and description being the identity providers for items.

I think something like traditional or traditional piped would be good. Such layout would also better on items with lengthy labels, descriptions or aliases.

(e.g. "Krung Thep Mahanakhon Amon Rattanakosin Mahinthara Ayuthaya Mahadilok Phop Noppharat Ratchathani Burirom Udomratchaniwet Mahasathan Amon Piman Awatan Sathit Sakkathattiya Witsanukam Prasit" on the Bangkok item)

imho, it would also be more suitable for responsive design.

I also tend to agree with Denny, regarding position of the aliases (between label and description).

Since the top line is not directly editable anymore anyway, also an option could be to set the Label in big letters in the top, description next to it (not under it), and the aliases below. This should also be pleasing aesthetically, and keeping the semantic unity of label+description.

I talked about this with @Snaterlicious some more. His goal is to in the end just have one input field for labels and aliases. The first one could for example be bold/bigger to indicate it is the main name for the entity. From a usability standpoint I think this makes a lot of sense.

@Lydia_Pintscher, please note that this contradicts the original intention and meaning of labels and aliases. Which is: label + description identify an item. Aliases are for searching only. Aliases are not meant to be some kind of "alternative labels".

@Lydia_Pintscher curious to see a mockup of "one input field for labels and aliases". otherwise, I don't quite understand and not convinced it's a good idea to combine these like that.

@Lydia_Pintscher I'm in favor of that approach, too. In practice (i. e., entity suggesters), labels and aliases identify items, not descriptions. Also, as you said, they are of the same kind, while label and description just serve the same purpose, but are different things.

This comment was removed by adrianheine.
Snaterlicious changed the task status from Open to Stalled.Jun 26 2015, 6:38 AM
Snaterlicious removed Snaterlicious as the assignee of this task.
Lydia_Pintscher changed the task status from Stalled to Open.Sep 15 2015, 12:17 PM

We will move forward with the "floating" option as a next step. We will keep the order "label, description, alias" as it currently is since label and description is what people should see first to make sense of the entity.

JanZerebecki renamed this task from investigate solutions for items with a large number of aliases to [Story] investigate solutions for items with a large number of aliases.Sep 25 2015, 8:38 PM
JanZerebecki added a project: Story.