Wikidata:Report a technical problem

Report a problemHow to report a problemHelp with PhabricatorGet involvedWDQS and Search
On this page, old discussions are archived. An overview of all archives can be found at this page's archive index. The current archive is located at 2023/05.

Start a new discussion

Time limit on Special:NukeEdit

The mass delete function only seems to go back less than a month. The documentation suggests that $wgRCMaxAge defaults to 90 days. Are we using a non-default value? It sometimes takes us some discussion to decide to pull the trigger. Bovlb (talk) 16:43, 9 May 2023 (UTC)Reply[reply]

It is 30 days per [1]. In phab:T307328 it has even been discussed to shorten this period further since the recent changes table in Wikidata is pretty large and expensive. —MisterSynergy (talk) 18:01, 9 May 2023 (UTC)Reply[reply]
Thanks. I don't really understand why Special:Nuke is based on RecentChanges. Why can't it just use user contributions? Bovlb (talk) 19:04, 9 May 2023 (UTC)Reply[reply]
phab:T33858.--GZWDer (talk) 06:05, 25 May 2023 (UTC)Reply[reply]

Change data type from url to external-idEdit

Please allow conversion from datatype URL to external-id. Several properties have been created with type URL but are related to one website and have the unique constraint, for those the regular form is to use external-id and create an URL formatter. Effect:

  1. save space in the DB
  2. better controlable, e.g. if base URL changes, a change of only one property statement can change the external links
  3. correct sorting in section external-ids


#P7890 ( URL)
#P1348 (AlgaeBase URL)
#P2488 (Belarus Globe URL)
#P1713 (biography at the Bundestag of Germany URL)
#P2649 (CQ Ranking men's team URL)
#P9519 (Digital Atlas of Idaho URL)
#P1421 (GRIN URL)
#P9908 (Hardy's Guide to Marine Gastropods URL)
#P7294 ( URL)
#P4001 (Latvian Protected Nature Territory URL)
#P1991 (LPSN URL)
#P7707 (PlayStation DataCenter URL)
#P3268 (PORT organization URL)
#P8606 (Stairway To Hell ID)
#P2520 (UNESCO Biosphere Reserve URL)
#P6107 (Winterthur Glossar URL (DEPRECATED))
#P6363 (WordLift URL)

GeoGQL (talk) 16:31, 12 May 2023 (UTC)Reply[reply]

Changing the data type makes sense when the values that were valid for the old data type are valid for the new one as well, e.g. from a string containing an identifier (without any URL formatting) to an external identifier. While changing from URL to external identifier should be technically possible (both have the value type string), it doesn’t make sense, because the values need to be updated anyway, resulting in temporarily broken values (if the property already has external identifier data type, but the value hasn’t been updated, the automatic links contain the domain name and path twice). It’s cleaner to create a new property with the new data type, and move the old values to the new property using a bot, appropriately transforming the value while moving it. —Tacsipacsi (talk) 10:03, 14 May 2023 (UTC)Reply[reply]
@temporarily broken values : Property talk:P7890 - 18 values. How long would "temporarily" last, if a bot or other tool updates the values? GeoGQL (talk) 11:45, 14 May 2023 (UTC)Reply[reply]
How long would it take to just create a new property and copy over the values instead of waiting for the developers to do the conversion? —Tacsipacsi (talk) 13:17, 16 May 2023 (UTC)Reply[reply]
There's probably a reason why these properties were created with datatype URL. URL (P7294) cannot be converted to external-id for example because the URLs are of the format https://$$GAME. So instead of inventing a string format from which the developer and game names can be extracted (using a delimiter perhaps), why not simply use the URLs, which have the bonus of being clickable? Dexxor (talk) 07:24, 17 May 2023 (UTC)Reply[reply]
"There's probably a reason" - yes, for any bug there is probably one as is for any request to remove a bug. RE URL : that is a combination of two external identifiers. Regular conversion would not work, so this could be left out. GeoGQL (talk) 18:00, 18 May 2023 (UTC)Reply[reply]
Is that a useful style of discussion, to not answer a question for how long an issue you mentioned exists, and instead ask question? What is your answer to your own question, since it was your suggestion to go that way? Or are you just opposing because you decided "it doesn’t make sense"? GeoGQL (talk) 18:06, 18 May 2023 (UTC)Reply[reply]
As mentioned by @Tacsipacsi these should not be converted but instead new Properties created as this would be a breaking change for reusers who rely on these being URLs. Lydia Pintscher (WMDE) (talk) 18:04, 18 May 2023 (UTC)Reply[reply]
Tacsipacsi didn't gave a sensible reason. GeoGQL (talk) 18:07, 18 May 2023 (UTC)Reply[reply]
Regarding re-users: they are not properly re-using if they don't take into account change on the property. GeoGQL (talk) 18:10, 18 May 2023 (UTC)Reply[reply]

Page jumbled up in mobile viewEdit

I am getting entity pages as this on Wikidata. All jumbled up.

Please help. Gotitbro (talk) 16:21, 19 May 2023 (UTC)Reply[reply]

Certainly looks borked: --Tagishsimon (talk) 21:27, 19 May 2023 (UTC)Reply[reply]

As in English Wikipedia Aquatic sports redirects to List of water sports Category:Water sports templates (Q115051915) should be merges with Category:Aquatics templates (Q8258017) and so Category:Water sports templates with Category:Aquatics templates.

Category:Water sports templates (Q115051915) is a page that is just made by a robot. Shkuru Afshar (talk) 04:23, 24 May 2023 (UTC)Reply[reply]

DB replica lagEdit 53 hours, and there's no announced maintenance. Issues? Infrastruktur (talk) 10:54, 27 May 2023 (UTC)Reply[reply]

phab:T337446, I suppose. --Matěj Suchánek (talk) 16:47, 27 May 2023 (UTC)Reply[reply]

Wikidata item Høgsteinen Lighthouse (Q1623402)Edit

Can you fix link from Commons Category:Høgsteinen fyrstasjon to Wikidata item Høgsteinen Lighthouse (Q1623402)? Nothing I could do would link them. GRDN711 (talk) 19:32, 28 May 2023 (UTC)Reply[reply]

  Done Infrastruktur (talk) 19:40, 28 May 2023 (UTC)Reply[reply]