Commons talk:Tools

From Wikimedia Commons, the free media repository
Jump to navigation Jump to search

Taxonomy/"Bread crumbs"[edit]

Because sometimes there is a need to create a chain of categories ("bread crumbs"), as, for example, here, I tried to find a tool to speed up the process (something like breadcrumb widget), as well as the ability to compare with other projects' chains. From {{Category tree all}} it was possible to make only {{Taxonomy}}. But it has disadvantages: 1) statically located only on 1 page; 2) it is inconvenient to enter category names; 3) the category name does not appear if you start typing it; 4) can not be compared with other projects. So I tried to make a small tool that would be devoid of these drawbacks. While in it there is an opportunity to use only categories of Commons. I plan to add the opportunity to compare with Wikidata items, with Wikipedia category chains and other. --Fractaler (talk) 07:52, 12 September 2018 (UTC)Reply[reply]

GeoCodingTodo gone?[edit]

Hi, does anybody know what has happened to the GeocodingTodo Tool? Page returns 404 not found... i miss it badly! --Fl.schmitt (talk) 15:42, 27 August 2020 (UTC)Reply[reply]

Coolest Tool Award 2022: Call for nominations[edit]

The fourth edition of the Coolest Tool Award welcomes your nominations! What is your favorite Wikimedia related software tool? Please submit your favorite tools by October 12, 2022! The awarded projects will be announced and showcased in a virtual ceremony in December. SSapaty (WMF) (talk) 12:05, 10 October 2022 (UTC)Reply[reply]

Redesigning this page[edit]

This page is not looking very nice and it is hard to find the tool you are searching for. Additionally this page is very outdated. So I would propose to update this page. The design and structure I have in mind for the new design is the design of the tools page on Wikidata d:Wikidata:Tools. As the first step I would propose to redefine the categories for the tools. Tools can be added to multiple categories(Commons:Tools/category). To make this in an easy way ever tool should have a own subpage (Commons:Tools/toolname) that is then inserted into the category pages. I would stat with the following categories:

  • Uploading
  • Findung what to photograph
  • Categorization
  • Editing structured data
  • Finding files
  • Downloading and external reuse
  • Mass editing
  • Administration and patrolling
  • Statistics
  • Developing

GPSLeo (talk) 13:44, 1 January 2023 (UTC)Reply[reply]

The tools should also be color coded to the different types "MediaWiki feature/extension", "Gadget", "User script", "Toolforge", "Other". And there should be a warning on outdated/unmaintained tools/currently broken tools. GPSLeo (talk) 13:49, 1 January 2023 (UTC)Reply[reply]
many tools do have their own pages. all gadgets should have their own. external tools are like com:F2C com:v2c...
i wanted to clean up part of this page a long time ago but it's not a priority. RZuo (talk) 14:10, 1 January 2023 (UTC)Reply[reply]
(edit conflict) Examples on how the short tool descriptions could look like:

Cat-a-lot[edit]

Gadget

Cat-a-lot is a JavaScript gadget that helps with moving multiple files between categories or adding categories to search results or files in galleries.

Activate the Gadget in your preferences

Documentation: Help:Gadget-Cat-a-lot

Categories: Categorization, Mass editing

Maintained

GLAMorgan[edit]

Toolforge

GLAMorgan shows where files of a specific category are used in Wikis in the selected month and how often these articles where viewed during this month.

glamtools.toolforge.org/glamorgan.html

Documentation: missing

Categories: Statistics

Broken
GPSLeo (talk) 14:23, 1 January 2023 (UTC)Reply[reply]

Proposal: Improve Toolhub coverage of Commons tools by improving on-wiki tool documentation[edit]

Toolhub is a community-managed catalog of software tools used in the Wikimedia movement. Technical volunteers can use Toolhub to document the tools that they create or maintain. All Wikimedians can use Toolhub to search for tools to help with their workflows and to create lists of useful tools to share with others. You can read more about Toolhub in general on meta.

The Technical Engagement team is interested in talking with you about finding more ways for the Commons community to use Toolhub. We are interested in having more tools that are helpful for workflows on Commons listed in Toolhub, and for those tools to also be more discoverable to folks who are contributing to Commons. For example, this query for user scripts known to work on Commons has only one result and there should be more.


Our first idea is to update this page so that a bot can parse the page and produce a toolinfo.json file that can be read by Toolhub. Templates can be used as a source of structured data for the bot. This is simpler than using Wikibase or another structured data store. We have previously built a tool which reads en:Template:User script table row records from en:WP:USLIST to produce a toolinfo.json file documenting the English Wikipedia's user scripts. It is possible to add to this tool once we have templates on Commons to read from.

We would like to try to make a generic "Template:Toolinfo" that can record any data that toolinfo.json supports. This template would use a Lua module to decide how to render itself based on the values of various parameters such as tool_type. This would also be a good opportunity to add some visual cues for type and known status as suggested previously by GPSLeo. We would like to work with folks here on Commons who typically document tools to design and apply the template.

  • Does this sound like a good approach?
  • Would you like to help with anything?
  • Do you have different ideas to improve the documentation and discovery of tools you use with Commons?

Please share them here. Udehb-WMF (talk) 15:24, 31 January 2023 (UTC)Reply[reply]

a catalog is good. i was just thinking of something similar: https://commons.wikimedia.org/w/index.php?title=Commons:Village_pump&oldid=729100298#Commons_Developer_Group？ . hopefully this makes it easier for users to learn how to use each individual tool. RZuo (talk) 16:49, 31 January 2023 (UTC)Reply[reply]
I have heard that some folks are reading this proposal (and possibly Toolhub itself) as expecting only tool builders/maintainers to edit the information for their tools. This also came with the associated feedback that maintaining quality documentation takes a group. I wanted to clarify that I and the Toolhub team agree that collaboration is important in maintaining documentation.
Features have been added since the initial release of Toolhub which make collaborative editing of the majority of the fields in a toolinfo record possible. As of 2023-02-07 there are 19 fields which are community editable. Five of these fields (wikidata_quid, audiences, content_types, tasks, subject_domains) are only available in the "annotations" layer that the community maintains. The other 14 are duplicated from the core toolinfo standard and exposed as community editable fields only if the core toolinfo data does not include data for that field.
Toolhub does still have an "ownership" model where the initial creator of a record has more control than the community including the ability to edit 13 core toolinfo fields (name, title, description, url, authors, license, etc) which are currently denied to the general community. This proposal is to collaboratively maintain the core toolinfo data for Commons tools here on-wiki which would allow community editing of all of this source information. When this data is ultimately imported into Toolhub by its web crawler, it will be seen as owned by a single user within the Toolhub database and interface. That owner is relatively unimportant however as toolinfo records managed by the crawler cannot be edited via the Toolhub UI or API. Instead edits are expected in the origin data which will be picked up by a future run of the crawler. -- BDavis (WMF) (talk) 17:53, 7 February 2023 (UTC)Reply[reply]

VFC[edit]

Hi, In last August, I wrote a request for Adding the source in display preview. It would be very helpful to have the source shown in the display preview, i.e. to detect copyright violations.

There wasn't any reaction then. Yann (talk) 17:22, 31 January 2023 (UTC)Reply[reply]
It was also suggested to add support for {{Wrong license}} into MediaWiki:Gadget-QuickDelete.js and MediaWiki:Gadget-VisualFileChange.js. Yann (talk) 17:28, 31 January 2023 (UTC)Reply[reply]
@Yann, can you help me understand how your feature request for VisualFileChange.js is a sub topic of improving documentation of Commons tools on-wiki and in Toolhub? I am not yet understanding the connection. -- BDavis (WMF) (talk) 17:40, 31 January 2023 (UTC)Reply[reply]
Well, it is not a request to improve the documentation, but some of the tools. Yann (talk) 18:03, 31 January 2023 (UTC)Reply[reply]
Would you object to moving it from an H3 under our proposal to its own H2 so that it is clear that you are asking for help with a separate issue? -- BDavis (WMF) (talk) 18:29, 31 January 2023 (UTC)Reply[reply]
OK, fine. ✓ Done Yann (talk) 19:10, 31 January 2023 (UTC)Reply[reply]
Retrieved from "https://commons.wikimedia.org/w/index.php?title=Commons_talk:Tools&oldid=730939262"