Wikidata:Tools/Proposals

Propose a new tool or gadget This page is designed for collecting proposals of new tools or gadgets which would be useful for Wikidata users.

Start a new discussion

Tracked in Phabricator
Task T90870

New gadget: monitor items having a specific property

This gadget should add to each property page a button that allows the user to automatically add to his watchlist all pages (items, properties, lexemes) containing this property; moreover, if in the next days/months/years the property gets added to other pages, these pages are automatically added to the watchlist of the user. This would be extremely helpful for my and other users' patrolling. Already proposed to DEV team. --Epìdosis 08:47, 19 May 2021 (UTC)

Could be build on my Wikidata Recent Changes API, which can get you items that had changes (eg "added") recently. --Magnus Manske (talk) 09:32, 25 October 2023 (UTC)

It seems a very good idea. This also allow to phrase my initial proposal in a bit more generic way: instead of just monitoring items having a specific property, it could be phrased as "items appearing as results of specific queries, chosen by the user". --Epìdosis 10:53, 3 November 2023 (UTC)

New tool: monitoring changes for a subset of items as a feed

As an external reuser of data from Wikidata,

I want to monitor changes on a subset of items (probably defined by a query) through a feed/API,

So that I can show the users of my service what is new in the data that is used there.

Sparql rc is close to solve this, but the results are not easily consumed by another service. Ainali (talk) 20:34, 15 September 2021 (UTC)

•  Support--So9q (talk) 08:06, 24 September 2021 (UTC)
•  Comment Try my Wikidata Recent Changes API, the "Query by items" section. --Magnus Manske (talk) 14:27, 25 October 2023 (UTC)

RDF

Hello,

The tool that I recommend:

1. Identify repetition errors that no longer allow you to have structured data. For example, the P131 of P131 in the same Item.
2. The tool must show the touched Item and, side by side, the immediately higher Item already containing the same data.
3. The tool must identify the contributor who has set the repetition, then, by clicking on a button, send a prevention message to the talk page of the contributor. I have to explain several times, even to well-established contributors or administrators, that Wikidata follows the RDF data model.
4. The prevention message must contain the explanatory link to Special:MyLanguage/Help:About data#Linking data.

It is also to avoid repeating the same thing several times to obtuse contributors, to whom the explanation has already been given for a similar case. Structured data is still the foundation of Wikidata that every contributor should know first.

Thanks. —Eihel (talk) 11:06, 30 October 2021 (UTC)

Bulk replace long-hand citations

A tool to bulk replace long-hand citations with an item

Like this diff (20 edits, or over 80 mouse clicks, in all!). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:08, 30 October 2021 (UTC)

Tool to remove all references from an item

Discussion in the (ongoing) "Request a tool" session at WikidataCon suggests that a script to remove all references from an item would be helpful. Use cases include a duplicated item, where it is desired that the structure and values are kept, but citing a new source; and for when one has found an item with a poor or invalid source, and the user ah a better source something better to cite. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:09, 30 October 2021 (UTC)

SPARQL query that shows all of the references connected to a specific item: https://w.wiki/4Jq9 - HT David Fichtmueller. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:03, 30 October 2021 (UTC)

Display latest satellite imagery

There's a python script which possibly could run as a user script on items with geo information. https://github.com/AdrienWehrle/earthspy

A way to conveniently translate Wikidata item and property labels

This has already been discussed in https://phabricator.wikimedia.org/T64695 and in some other places. A recent workshop at the Celtic Knot conference reminded me that this is still needed.

At the workshop, we ran a query that fetches untranslated property names (Example in Hebrew), and then clicked the result links one by one and translated them on property pages.

This is quite inconvenient and inefficient. Most people can translate many property names, and it should be as accessible as possible, but writing a query is something that most people don't know how to do. In addition, the need to open each property in a separate browser tab feels very old-fashioned.

It would be much nicer to use a true, integrated computer-assisted translation tool, similar to the Translate extension. Ideally, it would be integrated with the same extension. Amir E. Aharoni {{🌎🌍🌏}} talk 10:18, 4 July 2022 (UTC)

Request : UI script to show Commons categories linked via P910 + sitelink

Normally one can see if an item has a Commons category by looking to see whether it has a sitelink

But for various (established) reasons, sometimes one needs to follow topic's main category (P910) -> sitelink to get to the Commons category. When this is the case, just looking at in the regular Commons sitelink place can mislead one into thinking an item doesn't have a matching Commons category, when actually it does.

So I would find quite useful a UI script that would show a 'virtual' Commons category sitelink near the where the usual would appear, if an item has a topic's main category (P910) -> sitelink connection to a Commons category.

I mentioned the idea to User:Nikki on telegram the other day, and they thought such a thing should be feasible, at least technically.

(Yes, such categories can be indicated by Commons category (P373), but (i) that property isn't prominent on the page like the sitelink is, so isn't as immediately apparent in the same way; (ii) P373 hasn't been systematically maintained for quite a long time, so often will not be present even when it maybe should be; (iii) quite a lot of people wish P373 would go away (see eg most recent PfD -- one of several for it), or at least be deprecated, so we should probably be trying to rely on P373 less rather than more). Jheald (talk) 11:06, 19 August 2022 (UTC)

Request : UI script to show destination of a badged redirect (rather than immediately linked page)

It's good to see progress being made on phab:T278962, to make it easier for humans and bots to mark sitelinks that link to redirects.

One UI assist that would be nice would be to be able to see what item redirected links ultimately lead to, rather than the name of the redirect.

So eg at the moment The Hubs (Q15261108) currently shows "en:Sheffield Hallam Student Union building ->" as its en-wiki sitelink. It would be quite nice if instead by default get the link to appear as "-> en:National Centre for Popular Music" instead, that being where the link currently actually resolves to. Jheald (talk) 11:26, 19 August 2022 (UTC)

提案

管理者伝言板にスムーズに報告可能なガジェットを提案します。（日本語版ウィキペディアには既にあります。なお、私はガジェットの制作は出来ません。）--GALAXYライナー (talk) 22:44, 25 October 2022 (UTC)

New tool or gadget: Add an item as a main subject to selected scholarly articles

Use case: When I create or improve a Wikidata item for a concept, I want to search for scholarly articles about that concept and add my Wikidata item as a main subject (P921) with the reference based on heuristic (P887) = inferred from title (Q69652283). I need to be able to view the potential matches to be sure they are actually about the concept I am working on.

Background: I do this today using a long manual process:

• Edit and run a saved query (details below)
• Export the resulting list of scholarly articles
• Put them in Google Sheets and strip the item link to just the QID
• Review the article titles (and sometimes the Wikidata items) and remove any bad matches from the Sheet
• Pop the remaining QID list into another Google Sheet that formats a QuickStatements input list to add the main subject with reference based on heuristic (P887) inferred from title (Q69652283)
• Copy-paste the QS input from Sheets and run the QS batch

Existing query: https://w.wiki/6Heo This must be manually edited every time I use it to add the string I want to search for today in two places. The search string is the EN label of the Wikidata item I am working on. If the item is not brand new, I also need to add its QID so any search results that already have this item as main subject are excluded from the search results.

How the tool should work:

• From a Wikidata page, select "Add as Main Subject" (or similar) from the tools menu (or via a button, or whatever)
• The tool will find the EN label for the item and save that label as a search string
• The tool will search for any item with instance of (P31)=scholarly article (Q13442814) (ideally, or any of its subclasses) that have the search string in their EN labels. The search will be case-insensitive.
• The tool will display a list of the search results with a checkbox, linkable QID, and English label for each scholarly article found. The list can appear in a pop-up or window or similar. Note: I have had hundreds of results on some subjects, so allow for a long list. (This can be functionally similar to the results page in authorDisambiguator.)
• The tool user will be able to select/deselect the checkboxes for items where they want to add/not add the new main subject.
• A button/link marked "run" or "do it" or similar will add the QID of the new subject as main subject (P921) with the reference based on heuristic (P887) inferred from title (Q69652283) to each selected item and will report successful completion.
• There will be an option to close the pop-up or window when done.

Comparison to existing tool: This tool is similar to Wikidata:AddScholarTopics Script except that my proposal does an exact match on multi-word strings (so finds fewer matches), allows the requestor to remove individual matches that are incorrect before running, and does not require the intervention of a bot operator.

Conversely, Wikidata:AddScholarTopics Script, once set up, will be rerun for all searches whenever the bot is run (or that is my understanding). The proposed tool would need to be rerun by a user to catch any new matches. PKM (talk) 01:57, 18 June 2023 (UTC)

Neues Helferlein: ScrollUp Button

Bitte installiert einen neuen Button auf der Wikidataseite, um von jeder Stelle der Seite zum Kopf der Seite zu gelangen, ähnlich Commons "ScrollUp Button: Add a button to scroll up to the top of the current page." oder DE-Wikivoyage "Das „Pfeil-hoch-Helferlein“ fügt zu Kapitelüberschriften einen Rücksprunglink zum Anfang der Seite hinzu."

Bei Wikidataseiten mit vielen Einträgen ist es sehr mühsam, an den Kopf der Seite zu gelangen.

Ermöglicht allen Benutzern einfach und schnelles Bearbeiten Eduard47 (talk) 11:10, 8 October 2023 (UTC)

เพิ่มคำใหม่

ไลฟ์บล๊อก Rcyomtv (talk) 06:11, 2 March 2024 (UTC)