Last modified: 2011-12-30 19:32:39 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 8298 - Access information from a file description page where the file is used
Access information from a file description page where the file is used
Status: RESOLVED DUPLICATE of bug 25624
Product: MediaWiki
Classification: Unclassified
File management (Other open bugs)
unspecified
All All
: Low enhancement with 6 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
:
: 9616 12497 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-12-17 22:05 UTC by Sherool
Modified: 2011-12-30 19:32 UTC (History)
8 users (show)

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


Attachments

Description Sherool 2006-12-17 22:05:53 UTC
Basicaly __CLASS:[insert class name(s) here]__ (or something along those lines), so by adding for 
example __CLASS:nsd__ to an image (for example embeded via a "no source" template) a class="nsd" 
atribute would be  added to the image tag on all pages that use the image.

This would allow the Wiki's global stylesheet/javascript to be set up to cause such images to be 
"highlighted" in certain ways automaticaly.

I realise this might be slightly tricky to achieve. For example if the keyword is added to a 
template that is transcluded on a number of images all those images would need to have theyr 
class data updated, and that would mean that all articles that use those images would in turn 
have to be re-parsed for the change to actualy have any noticable effect. I guess the first part 
is easy enough as the job que will already work it's way though all pages that transclude a 
changed template, but this would call for all pages that use those images touched by the job que 
to also be added to the job que (preferably if and only if the "class data" was changed to avoid 
a massive "cascade" due to a simple typo fix). Not sure how problematic this would be.

Using a combination of CSS and JavaScript there is almost no limit to what could be done, I'm 
sure there are lots of usefull applications for an ability to asign a class to an image beyond 
highlighting images slated for deletion.
Comment 1 Judson (enwiki:cohesion) 2006-12-17 23:26:31 UTC
This would be very helpful for image tagging. Currently there is no way to
inform all the users that might care about the pending deletion of an image. 

This was also brought up in the mailing list for fair use. We could have a much
more subtle indication that an image is fair use so that people could think
about replacing it if they can.

There are probably many more uses for such an open system that people could come
up with later.
Comment 2 Matthew Fenton 2007-01-30 12:45:22 UTC
Idea is useless and redundant to image description page.
Comment 3 ejsanders 2007-01-30 14:13:44 UTC
Not it isn't Matthew - it provides an in-line alert. People watching a page
don't usually watch all the images on the page as well.
Comment 4 Platonides 2008-01-26 18:35:05 UTC
Keep into mind that having them not only changing the page (just as templates do) but firing a notice on watchlists is harder. You'd need some fake revision trickiness.
Comment 5 Betacommand 2008-01-26 18:40:46 UTC
you would not need to edit the watchlist. This would allow users to highlight images that have problems while viewing the article. not for watchlists
Comment 6 Guillaume Paumier 2009-12-30 21:24:34 UTC
Could you please reformulate this request in terms of what the actual problem is, and what you would like to achieve, rather than on possible solutions? The proposed implementation looks awfully complicated.
Comment 7 Judson (enwiki:cohesion) 2009-12-30 22:30:07 UTC
Restating from my understanding: It would be useful if there was a way to make a visual change to images in article space based on some aspect of the image description page. This would most likely be used to alert people looking at the article that an image was about to be deleted, or had some other urgent issue.
Comment 8 Happy-melon 2009-12-30 22:53:38 UTC
This effect can be achieved with javascript; I use such a script on enwiki (http://en.wikipedia.org/wiki/User:Anomie/linkclassifier.js).  Among other things, it highlights non-free images and images marked for deletion, based on the presence of particular categories.  Recommend WONTFIX for this, or as an extension if people are absolutely desperate to have a server-side solution.  Certainly this is not something that is ever likely to make it into MW core.

And even if the madness does take us, it should be a parser function: {{CLASS:foo}} or {{#class:foo}}.  Behaviour switches (__SWITCH__) are parameterless.
Comment 9 Guillaume Paumier 2009-12-30 23:44:41 UTC
*** Bug 9616 has been marked as a duplicate of this bug. ***
Comment 10 Guillaume Paumier 2009-12-30 23:56:38 UTC
(In reply to comment #7)
> Restating from my understanding: It would be useful if there was a way to make
> a visual change to images in article space based on some aspect of the image
> description page. This would most likely be used to alert people looking at the
> article that an image was about to be deleted, or had some other urgent issue.

Thank you. I have changed the summary accordingly (broadening it a bit). Basically what this request is about is the ability to access information from the file description page on pages where the file is used.

(In reply to comment #8)
> Recommend WONTFIX for this, or as an
> extension if people are absolutely desperate to have a server-side solution. 
> Certainly this is not something that is ever likely to make it into MW core.

I'm not sure. If we manage to somehow structure metadata, we will routinely want to access information such as author, license, etc. and we could use some specific flags for a limited number of cases such as copyright violation.
Comment 11 Guillaume Paumier 2009-12-31 01:11:49 UTC
*** Bug 12497 has been marked as a duplicate of this bug. ***
Comment 12 Krinkle 2011-12-30 19:32:24 UTC
* bug 31257 - File properties storage
* bug 31210 -  Transclude image description from Wikimedia Commons into [[File:]] caption on Wikipedias
* bug 25624 -  Making license and author information api accessible

*** This bug has been marked as a duplicate of bug 25624 ***

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


Navigation
Links