Last modified: 2014-10-28 08:34:19 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T74524, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 72524 - Implement structure to store entity image
Implement structure to store entity image
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
WikidataRepo (Other open bugs)
master
All All
: Unprioritized normal (vote)
: ---
Assigned To: Wikidata bugs
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-10-26 08:01 UTC by Henning
Modified: 2014-10-28 08:34 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Henning 2014-10-26 08:01:46 UTC
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".
Comment 1 Lydia Pintscher 2014-10-27 23:34:11 UTC
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.
Comment 2 Henning 2014-10-28 08:34:19 UTC
Thanks for pointing out one of the worst possible solutions again. :-/ Still wondering how users are supposed to understand that mechanism.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links