User talk:Waggers

I usually contribute to the en-version of Wikipedia as user Waggers. Please inform me of deletion notifications on my talk page there, not here.

Tip: Categorizing images

---

Hello, Waggers!

Tip: Add categories to your files

Thanks a lot for contributing to the Wikimedia Commons! Here's a tip to make your uploads more useful: Why not add some categories to describe them? This will help more people to find and use them.

Here's how:

1) If you're using the UploadWizard, you can add categories to each file when you describe it. Just click "more options" for the file and add the categories which make sense:

2) You can also pick the file from your list of uploads, edit the file description page, and manually add the category code at the end of the page.

[[Category:Category name]]

For example, if you are uploading a diagram showing the orbits of comets, you add the following code:

[[Category:Astronomical diagrams]]

[[Category:Comets]]

This will make the diagram show up in the categories "Astronomical diagrams" and "Comets".

When picking categories, try to choose a specific category ("Astronomical diagrams") over a generic one ("Illustrations").

Thanks again for your uploads! More information about categorization can be found in Commons:Categories, and don't hesitate to leave a note on the help desk.

CategorizationBot (talk) 11:56, 17 December 2011 (UTC)

• Image:Fleming Arms.jpg was uncategorized on 16 December 2011 CategorizationBot (talk) 11:56, 17 December 2011 (UTC)

A barnstar for you!

	The Original Barnstar
	Thanks for all your help tagging maps in the Mechanical Curator collection - after ten days, we've now done half the books and found 10,600 images! Andrew Gray (talk) 01:03, 11 November 2014 (UTC)

Code issues in User:Waggers/degrandparent.js

Hi Waggers, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

1. You edited User:Waggers/degrandparent.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!

1. ISSUE: line 40 character 59: Missing semicolon. - Evidence: + " and " + cat.title + "</div>")

Your CommonsMaintenanceBot (talk) at 15:00, 6 February 2015 (UTC).

Code issues in User:Waggers/degrandparent.js

Hi Waggers, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

1. You edited User:Waggers/degrandparent.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!

1. ISSUE: line 37 character 17: 'api_url' is already defined. - Evidence: var api_url = "/w/api.php?format=json&action=query&list=categorymembers&cmtype=file&cmtitle="

Your CommonsMaintenanceBot (talk) at 08:22, 8 February 2015 (UTC).

Code issues in User:Waggers/degrandparent dev.js

Hi Waggers, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

1. You edited User:Waggers/degrandparent dev.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
2. Though, that change appears to introduce 3 new jshint issues — the page's status is now having ERRORS. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!

1. ISSUE: line 57 character 6: Don't make functions within a loop. - Evidence: });
2. ISSUE: line 79 character 6: Expected an identifier and instead saw ')'. - Evidence: }); // get files in parent category
3. ISSUE: line 83 character 1: Expected '(end)' and instead saw '}'. - Evidence: }

Your CommonsMaintenanceBot (talk) at 12:59, 9 February 2015 (UTC).

Code issues in User:Waggers/degrandparent dev.js

Hi Waggers, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

1. You edited User:Waggers/degrandparent dev.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
2. Though, that change appears to introduce 1 new esprima issue — the page's status is now having ERRORS. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!

1. ERROR: Cannot parse line 79 column 3: Unexpected token )

Your CommonsMaintenanceBot (talk) at 12:59, 9 February 2015 (UTC).

Southampton church image

I've refined the details of both File:All Saints Church, Southampton, 1852.jpg and the cropped version File:All Saints Church, Southampton, 1852, cropped.jpg because this is not your own work, you need to provide the proper source details plus the correct date of the image and you cannot give a more restrictive licence then the original has, etc. Good luck. Ww2censor (talk) 11:22, 12 November 2015 (UTC)

Many thanks, Ww2censor, I will endeavour to use the Extract templates and correct licencing for cropped images in future. Waggers (talk) 12:47, 12 November 2015 (UTC)

No problem at all. They were easy to fix as you had previously given the original source on the copyright questions page so I remembered that. It's all just more accurate and allows for easier licence reviews in the future is anyone questions anything. Cheers. Ww2censor (talk) 13:06, 12 November 2015 (UTC)

Can we take this script DGP out of commons?

I felt this script would be useful on other projects too, but I don't know how to take it outside? like on mrwiki or enwiki? how I can use this script? QueerEcofeminist ^{"cite! even if you fight"!!!} [they/them/their] 16:37, 10 August 2019 (UTC)

Thanks user:QueerEcofeminist, I'm really pleased you find it useful. I'll explore some ways of making it available to other wikis. It would be fairly easy to copy it across, but there might be a more elegant way to enable all wikis to reference the same source code instead of having a separate copy on each project. Waggers (talk) 11:52, 13 August 2019 (UTC)

Hello, I was just curious about the script, did you get time to look for the possibilities? thanks and regards QueerEcofeminist ^{"cite! even if you fight"!!!} [they/them/their] 17:53, 27 August 2019 (UTC)

Community Insights Survey

Share your experience in this survey

Hi Waggers,

The Wikimedia Foundation is asking for your feedback in a survey about your experience with Wikimedia Commons and Wikimedia. The purpose of this survey is to learn how well the Foundation is supporting your work on wiki and how we can change or improve things in the future. The opinions you share will directly affect the current and future work of the Wikimedia Foundation.

Please take 15 to 25 minutes to give your feedback through this survey. It is available in various languages.

This survey is hosted by a third-party and governed by this privacy statement (in English).

Find more information about this project. Email us if you have any questions, or if you don't want to receive future messages about taking this survey.

Sincerely,

RMaung (WMF) 01:14, 10 September 2019 (UTC)

Reminder: Community Insights Survey

Share your experience in this survey

Hi Waggers,

A couple of weeks ago, we invited you to take the Community Insights Survey. It is the Wikimedia Foundation’s annual survey of our global communities. We want to learn how well we support your work on wiki. We are 10% towards our goal for participation. If you have not already taken the survey, you can help us reach our goal! Your voice matters to us.

Please take 15 to 25 minutes to give your feedback through this survey. It is available in various languages.

This survey is hosted by a third-party and governed by this privacy statement (in English).

Find more information about this project. Email us if you have any questions, or if you don't want to receive future messages about taking this survey.

Sincerely,

RMaung (WMF) 15:24, 20 September 2019 (UTC)

Reminder: Community Insights Survey

Share your experience in this survey

Hi Waggers,

There are only a few weeks left to take the Community Insights Survey! We are 30% towards our goal for participation. If you have not already taken the survey, you can help us reach our goal! With this poll, the Wikimedia Foundation gathers feedback on how well we support your work on wiki. It only takes 15-25 minutes to complete, and it has a direct impact on the support we provide.

Please take 15 to 25 minutes to give your feedback through this survey. It is available in various languages.

This survey is hosted by a third-party and governed by this privacy statement (in English).

Find more information about this project. Email us if you have any questions, or if you don't want to receive future messages about taking this survey.

Sincerely,

RMaung (WMF) 20:04, 3 October 2019 (UTC)

Abount the COM:DGP

When I use it, it will show Error: API returned error code "badtoken": Invalid CSRF token.. Can you tell me what happen for this? 轻语者 (talk) 14:27, 18 June 2020 (UTC)

Catting an artist's work

Did you make this deletion] and this deletion using a bot?

The origins or place associations of an artist is a completley different catting branch from the contents of a picture. One is not the grandparent of the other... Broichmore (talk) 13:23, 19 February 2022 (UTC)

Hi, I was using a user script (linked in the edit summaries). I agree, there's a distinction between works of someone born in X and works where the subject is X. However it is true to say neither of these were categorised correctly - instead of Category:Portsmouth / Category:Plymouth they should be in an appropriate subcategory - in these cases, I would suggest Category:Old Portsmouth / Category:Ships in Plymouth. Waggers (talk) 21:54, 19 February 2022 (UTC)

Indeed. So why didn't you make those assignments.

However File:Old Portsmouth RMG PV4700.jpg was perfectly catted as Portsmouth, because it shows both Portsmouth Point and Old Portsmouth. Why have two cats when one will suffice?

As for Category:Ships in Plymouth aside from your making a good point; that was buried away almost ridiculously in Category:Vehicles in Plymouth, which in turn was obtusely hidden away in Category:Transport in Plymouth. In some perverse way, of course that kind of over catting can't be criticised as strictly wrong.

The overall schema for Plymouth doesn't even conform to the so called esablished way, there are many inconsistencies to the norm there.

Given that Plymouth's main claim to fame to fame centres on, and is anchored on shipping, catting against Plymouth seemed correct.

It's a disease here, that this kind of over nesting and diffusion of images hides files away from sight.

Its unfortuneate and I think unnecessary for Ships in Plymouth to be buried away like it is. Daft schemas like this are commonplace here. It's barely the case that H.M. ships qualify as transport or even vehicles. It's certainly an ugly way of doing it.

I don't know how this script works in practise , but it doesn't seem to be sympathetic to bespoke catting. Using 'Search all subcategories looks dangerous to me. It's how this mess with Artist's birthplace and subject matter came about. Your relying on a machine to do your thinking, when in a reality images such as these need to be assessed indivdually on their own merits. If search within a single subcategory were used this error would not have come about.

Are you now going to correct past instances where this confuson has happened elsewhere?

Forgive the rant, I spend my time uncovering files too difficult for the average person to cat. As fast as I find lost files and make them known, someone comes along and hides them away again.

Only recently I came across some (potentially) 400 or more files given wrong artist attribution. The user using hot cat managed to do it in under 2 minutes. They assigned each file (photographs) with two different creators, despite correct attribution within the descriptions against each of those files. Now they won't take responsibility for making the corrections, presumably because its too difficult. Broichmore (talk) 13:27, 20 February 2022 (UTC)

Categorisation on Commons generally needs a lot more time and effort put into it - as you say, there are inconsistencies all over the place and it can be frustrating. Categories like Plymouth and Portsmouth are very broad and require a lot of diffusion - ideally there should be no files directly in those categories at all. If something shows both Portsmouth Point and Old Portsmouth then it should be in both of those categories, not Portsmouth. That's the "Modularity" principle in the COM:CAT policy. Waggers (talk) 11:25, 21 February 2022 (UTC)

Hiding an image that was on display

In this case File:Henry Sargeant - The Portsmouth chain ferry on a stormy day, 1889.jpg when deleting Gosport, why didn't you per your own creed, create a History of cat to put this in. It's an important historical image now buried in "Gosport Ferry". Where it's not likely to be found or used. Broichmore (talk) 12:41, 22 February 2022 (UTC)

I am simply trying to clear overpopulated parent categories, either by moving items to subcategories or, if they are already in a subcategory, just removing them from the parent category. In this case, the item already existed in subcategory Gosport Ferry and therefore could be removed from Portsmouth.

The file was not "on display" in Category:Portsmouth. It was one of over 2000 files in that category and therefore arguably more "buried" there than in the 22-item Category:Gosport Ferry. Waggers (talk) 14:31, 22 February 2022 (UTC)

For me at least, 2000 files in a category is not a problem, thats only 4 pages on the max thumbnail setting. Whats more important than tidying up nesting is making images accessible to search and find. If we are going to delete a cat then we should replace it with better, rather than simple delete.

This image is so much more than just a ferry. Research is already a difficult and time consuming excercise and requires imagination. Like I said before. I spend most of my time uncovering hidden images, Images of Historical Gosport for example, hiding in some minor cat like that of a provincial ferry. Broichmore (talk) 11:55, 24 February 2022 (UTC)

Shemara

Hi, there's a problem cataloguing this image, it keeps getting catalogued as Queen Mary 2 when that is not the subject of the picture, just part of the background. Shemara is a ship in Southampton, not a cruise liner and certainly not the QM2. I don't know why this keeps getting changed. Doesn't anybody actually look at the picture when deciding which category to put it in? Murgatroyd49 (talk) 18:58, 2 March 2023 (UTC)

Waggers and others are correct. There are two ships in the image. Broichmore (talk) 19:58, 2 March 2023 (UTC)

Debatable that a bit of the ships stern counts as as an image of the ship. The big problem with categorising the image as QM2 is that editors then remove the category "Ships in Southampton" as the QM2 is a subcategory. This means that anyone searching "Ships in Southampton" is not going to find Shemara thus defeating the point of the category system. And yes I know it shows the scale, I took the photo with exactly that in mind! Murgatroyd49 (talk) 09:22, 3 March 2023 (UTC)

The solution is to create a "Shemara in Southampton" category and add the image to both that and the "QM2 in Southampton" category. Waggers (talk) 09:46, 3 March 2023 (UTC)

No, unnecessary. There is only one image of Shemara, to create another category is overkill. You dont do it for one image, it needs many, over catting hides files. We want them used. Broichmore (talk) 15:45, 3 March 2023 (UTC)

You asked for a suggestion, I gave you one. If any file is in both a category and a subcategory of that category, I make not apologies for removing it from that parent category; that's the policy. There's absolutely no problem with creating a category for a single file - the policy says quite clearly: "The category structure should reflect a hierarchy of concepts, from the most generic one down to the very specific." (my bolding).

The notion that files become "hidden" when added to a specific category but are somehow "visible" when they are in an overpopulated parent category comes up a lot, and is a load of bull. Categorisation has nothing to do with how "visible" a file is, and as for "we want them used" - who's we? I don't see that aspiration written anywhere in Commons:Project scope. If particular files do need to be made more visible and showcased, that's what gallery pages and projects like featured images and good images are for. Categories aren't way of making files more or less visible. They're just categories.

You also mention overcategorisation. Again, the definition from the policy: "Over-categorization is placing a file, category or other page in several levels of the same branch in the category tree." That's precisely what you seem to be advocating, and I am trying to prevent. Waggers (talk) 10:02, 6 March 2023 (UTC)

Another fairly obvious solution would be to create a more general subcategory of Category: Ships in Southampton such as Category: Motor yachts in Southampton and place the file in there. Waggers (talk) 09:53, 7 March 2023 (UTC)

DGP

Please take it slowly when "degrandparenting" files, in particular when they come from currently busy categories such as "City of Leeds". In most cases there are several ways of categorizing files. There are - for lack of better words - object categories and geographical categories. Some of the first are fairly easy to find, the second need some time because in some cases it is necessary to look at several maps for the proper location, and the boundaries of e.g. suburbs are not always clear. Hence, files may temporarily remain in the main category and one of its object subcategories while awaiting geographical categorization. If you "degrandparent" such files in a hurry, I (and whoever may also be busy cleaning up these overpopulated categories) won't find them again in the second run. Note that I am not advocating overcategorization; I also believe that your script is useful in the long run; I only ask that you give editors time to do their work. Maybe you can exclude the recent geograph.org.uk uploads from being automatically processed, at least for a while? Due to the nature the upload process, there is lot of clean-up work to do. Schlosser67 (talk) 09:23, 15 March 2024 (UTC)