Page MenuHomePhabricator

Collect what data of lexemes and forms is needed for the display use case
Closed, ResolvedPublic

Description

What lexeme or form data should be displayed, and how has been defined in form of a google document, and also scatter in a bunch of phabricator task.
Let's have it collected in a single place for the work on "how to display lexemes or forms" use case of the "migrate off wb_terms" work.

Event Timeline

WMDE-leszek renamed this task from Collect what data of lexemes and forms is needed for the display use cxase to Collect what data of lexemes and forms is needed for the display use case.Jun 13 2018, 10:59 AM

Lexemes

Use cases

How to read it:
Lemma: All lemmas defined on a lexeme displayed separated by translatable separator (separator displayed in UI language, including possible language fallback of translation - fallback language indicator not shown).
Language+Lexical Category: Labels of the language and lexical category items, including possible language fallback label(s) (fallback language indicator not shown). Combining of two labels done according to UI language (e.g. in English it could be: English, noun)

Value in statement

Link text: Lemma
Link “title”: Language+Lexical Category

Value in statement, not saved

Text: Lemma

Link/reference in the edit summary on the history page

Link text: Lemma (Language+Lexical Category)
Link “title”: TODO

Link in the diff view

Link text: Lemma (Language+Lexical Category)
Link “title”: Language+Lexical Category

Search result in the “entity selector”, Search result in the “top” search box

First-line text: Lemma
Second-line text: Language+Lexical Category

Recent changes

Link text: Lemma
Link “title”: Language+Lexical Category

Watchlist

Link text: Lemma
Link “title”: Language+Lexical Category

Special:AllPages, Special:NewPages, Special:Contributions, Special:WhatLinksHere...

Link text: Lemma (ID)
Link “title”: Language+Lexical Category

Search result on Special:Search (“standalone” search page)

Link text: Lemma (ID)
Link “title”: Language+Lexical Category
Second-line text below the link: Language+Lexical Category

Forms

Use cases

How to read it:
Representation: All representation defined on a lexeme form separated by translatable separator (separator displayed in UI language, including possible language fallback of translation - fallback language indicator not shown).
Grammatical features: Labels of the grammatical feature items, including possible language fallback label(s) (fallback language indicator not shown). Combining of labels done according to UI language (e.g. in English it could be: nominative, singular)

Value in statement

Link text: Representation
Link “title”: TODO

Value in statement, not saved

Text: Representation

Link/reference in the edit summary on the history page

Link text: Representation (TODO)
Link “title”: TODO

Link in the diff view

Link text: Representation (TODO)
Link “title”: TODO

Search result in the “entity selector”, Search result in the “top” search box

First-line text: Representation
Second-line text: TODO

Recent changes

Link text: Representation
Link “title”: TODO

Watchlist

Link text: Representation
Link “title”: TODO

Search result on Special:Search (“standalone” search page)

Link text: Representation (ID)
Link “title”: TODO
Second-line text below the link: TODO

Vvjjkkii renamed this task from Collect what data of lexemes and forms is needed for the display use case to y4aaaaaaaa.Jul 1 2018, 1:05 AM
Vvjjkkii triaged this task as High priority.
Vvjjkkii updated the task description. (Show Details)
Vvjjkkii removed a subscriber: Aklapper.
CommunityTechBot renamed this task from y4aaaaaaaa to Collect what data of lexemes and forms is needed for the display use case.Jul 2 2018, 1:57 PM
CommunityTechBot raised the priority of this task from High to Needs Triage.
CommunityTechBot updated the task description. (Show Details)
CommunityTechBot added a subscriber: Aklapper.
Addshore claimed this task.
Addshore added a subscriber: Addshore.

Other than what has already been said here, many of the things in T197078 also apply.
As part of my cleanup while looking at T208425 again. im going to close this ticket.