Page MenuHomePhabricator

Find out how MediaInfo entities are going to be displayed, and what entity data would be needed
Closed, ResolvedPublic

Description

MediaInfo entities might be similar to items in the regard of "displaying" them. Or might not. Find out what is the current idea there.
MediaInfo entities have different elements than items/properties, and this should potentially be considered in the "display" use case of the "migrate from wb_terms" work. The scope of this ticket is to also define what elements would be used for display, and how.

Event Timeline

Vvjjkkii renamed this task from Find out how MediaInfo entities are going to be displayed, and what entity data would be needed to x4aaaaaaaa.Jul 1 2018, 1:04 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 x4aaaaaaaa to Find out how MediaInfo entities are going to be displayed, and what entity data would be needed.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.

I'm going to close this.

MediaInfo entities themselves are not currently using wb_terms table.
items and properties used form commons are currently using the wb-terms table.
The wb_terms table will be killed with T208425: [EPIC] Kill the wb_terms table.
The solution created after that point for items and properties, both in terms of sql storage and bulk lookup from elasticsearch could both work for mediainfo if mediainfo develops that need, but right now I dont think the need is there.