Page MenuHomePhabricator

Implement structure to store entity image
Closed, DeclinedPublic

Description

In order to improve visualization, according to the new UI, each entity is supposed to feature an image just like it features label(s), description(s) and aliases. As there may be cultural differences, it should be possible to specify an image per language and language fall-backs should be resolved. The data type images are stored with should probably be a setting--currently, and in the scope of Wikidata, only "Commons Media" would be a proper type, but for other use cases, some "Image Link" or "Image File" type would probably be more appropriate.
It would be best, to store the image(s) using the same structure like label(s) and descrition(s) adding the image(s) to the "fingerprint".


Version: master
Severity: normal

Details

Reference
bz72524

Related Objects

Event Timeline

bzimport raised the priority of this task from to Needs Triage.Nov 22 2014, 3:51 AM
bzimport set Reference to bz72524.
bzimport added a subscriber: Unknown Object (MLST).

As discussed I think we should be using existing statements and harvest them for the image to show in the header. Adding an additional field introduces a lot of work for the community for very little benefit.

Thanks for pointing out one of the worst possible solutions again. :-/ Still wondering how users are supposed to understand that mechanism.

Lydia_Pintscher removed a subscriber: Unknown Object (MLST).
Lydia_Pintscher removed a subscriber: Unknown Object (MLST).Dec 1 2014, 2:32 PM

Ok what other options do we have?
I do not want users to have to specify a separate image but reuse existing data in the item. And the image should not be defined per language but per item.

Lydia_Pintscher claimed this task.

Closing this until we have options for the issues at hand.