Sarai-WMDE added a comment.
Terminological mismatches: Request for feedback on designs
----------------------------------------------------------
Like in the case of {https://phabricator.wikimedia.org/T313467}, this task
requires redesigning of the Mismatch Finder's results page and/or table to
display new types of mismatches. In this case, said mismatches are related to
terminological data: labels in all languages, aliases, potentially descriptions.
Some initial concerns to keep in mind regarding the overall initiative of
collecting term mismatches:
1. Looking for textual differences between free, human-produced text might
generate a lot of noise. This might be specially noticeable when it comes to
descriptions. We'd need to understand the benefits and usefulness of including
this type of mismatches.
2. When searching for terminological mismatches, we'll of course have to take
all languages into account (and indicate this in the results)
The initial design exploration aimed at being explicit, and presented
terminology mismatches in a separate table under the same item. This allowed to
clearly differentiate these different kinds of mismatches from the property
(and qualifir) mismatches.
**Initial proposals to visualize term mismatches on the results page (see
designs in Figma
<https://www.figma.com/file/giI7PSmAju8t80OE65jBfZ/Mismatch-Finder-v2?node-id=3307%3A5504&t=TYLOYSpD3xFR9j7U-0>)**
F35794305: T313469.png <https://phabricator.wikimedia.org/F35794305>
Description: The Mismatch finder generates a separate table to display
mismatches in labels, aliases and descriptions.
The term table would be
displayed below the properties’ table.
This approach was tentatively abandoned in a following iteration, where it
was decided to try to group all mismatch types (properties, qualifiers and
terms) in a single:
**Latest iteration (see designs in Figma
<https://www.figma.com/file/giI7PSmAju8t80OE65jBfZ/Mismatch-Finder-v2?node-id=3361%3A4397&t=TYLOYSpD3xFR9j7U-0>)**
This unified solution corresponds exactly to what's documented in
{https://phabricator.wikimedia.org/T313467}.
| **Option 1**: A new column specifies the type of mismatch (two possible
placements)
| **Option 2**:
Descriptive text provides mismatch type inside the Mismatch column
|
| 1a F35794129: T313469.png <https://phabricator.wikimedia.org/F35794129> 1b
F35794133: T313469.png <https://phabricator.wikimedia.org/F35794133>
| F35794168: T313469.png
<https://phabricator.wikimedia.org/F35794168>
|
| Description: A new column is introduced in the mismatch table to document
the ‘type’ of the listed mismatches (or 'where' they are). In option 1a, the
new ‘mismatch type’ column is placed to the right of the mismatch column. In
option 1b, the column is placed at the beginning of the table. | Description:
In this version, a subtle descriptive text indicates the type of mismatch from
within the Mismatch column. |
|
**Questions regarding the latest design iteration**:
1. For label mismatches: Could we link to the item’s termbox?
2. In general, as mentioned in this comment
<https://phabricator.wikimedia.org/T313467#8405263>, the unified approach might
be weaker in case all or the big majority of mismatches are going to be related
to statement properties: using a whole new column to indicate their type will
feel redundant.
TASK DETAIL
https://phabricator.wikimedia.org/T313469
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: Sarai-WMDE
Cc: Sarai-WMDE, jmkeil, Aklapper, Lydia_Pintscher, Astuthiodit_1,
karapayneWMDE, Invadibot, maantietaja, Mattia_Capozzi_WMDE, ItamarWMDE,
Akuckartz, Nandana, Lahi, Gq86, GoranSMilovanovic, QZanden, LawExplorer,
_jensen, rosalieper, Scott_WUaS, Wikidata-bugs, aude, Mbch331
_______________________________________________
Wikidata-bugs mailing list -- wikidata-bugs@lists.wikimedia.org
To unsubscribe send an email to wikidata-bugs-le...@lists.wikimedia.org
