Last modified: 2011-12-14 17:37:20 UTC
When one clicks on a Commons image in Wikipedia, one gets a page of metadata along with a note that says "This is a file from the Wikimedia Commons. Information from its description page there is shown below." Most of the information in the Commons file is copied over, but the Commons categories are not and I often find I need to go to the Commons file to see those categories. It would save me a lot of time if the Common category links could be shown on the initial Wikipedia image page, perhaps in the same box as the "This is a file from the Wikimedia Commons..." note to distinguish them from the Wikipedia category links.
This makes sence, but I think there is a similar but to this one here already... dont have time to look for it now though.
I'm not sure about the interface for this. I can't think of a good ui for this. I think putting it in the "this is from commons" box would be weird.
Re interface, it could be a collapsed list in the "this is from commons" box (click on the + to expand). Or the commons categories could be listed at the bottom of the page, possibly with a level 1 heading that said "Image's categories on Commons" or some such. Or place it where categories normally go, but prefixed with "Commons categories:" instead of just "Categories:". I don't see much problem with user confusion. They click on a link add see a bunch of images related to the one they started with. Ok, they're now in Commons, but they can always use their back button to return to Wikipedia. Having users discover the Commons this way be a good thing.
Moving component to Images, as it is really an issue with the foreign filerepos, not wikimedia specifically. If this was to be done, I think the best approach of the one's you've thought of would be to add "Commons categories:" to the standard categorylinks box (would need a generic term for commons when the repo is not commons, foreign categories would probably work). (how easy to insert something in that point in the skin is something I'm not sure about though)
*** This bug has been marked as a duplicate of bug 18752 ***
