Wikidata:Report a technical problem

Report a problemHow to report a problemHelp with PhabricatorGet involvedWDQS and Search

Start a new discussion

edit

I noticed that the Bluesky DID links being generated are broken because the : is being percent-encoded in the URL. If you look at the link for Jay Graber, for instance, it goes to https://bsky.app/profile/did%3Aplc%3Aoky5czdrnfjpqslsw2a5iclo which gives an Error: handle must be a valid handle message. The correct link is: https://bsky.app/profile/did:plc:oky5czdrnfjpqslsw2a5iclo. —Paul1337 (talk) 23:49, 3 September 2024 (UTC)Reply

@Paul1337:   Resolved. See Special:Diff/2243057416. This is being handled by the Wikidata External ID redirector (Q108047563) (example), but you'll have to wait a little while (~ 24-48 hours) for the new formatter URL to take effect. Regards Kirilloparma (talk) 00:50, 4 September 2024 (UTC)Reply
Thanks so much @Kirilloparma :) —Paul1337 (talk) 02:14, 4 September 2024 (UTC)Reply
You're welcome! :) Regards Kirilloparma (talk) 03:02, 5 September 2024 (UTC)Reply

Protection of items from the Netherlands

edit

Hello, I cannot add interwikis because the pages are protected in: Heusden (Q9845, an:Heusden), Oldenzaal (Q10016, an:Oldenzaal) y Category:Oldenzaal (Q9047867, an:Categoría:Oldenzaal). I wanted to create articles about municipalities in the Netherlands but if the first three items are already protected.... BCN63 (talk) 13:49, 18 September 2024 (UTC) And Hilvarenbeek (Q9846, an:Hilvarenbeek).... And Deaths in The Hague (Q9218753, an:Categoría:Muertos en Den Haag)... BCN63 (talk) 18:52, 18 September 2024 (UTC)Reply

  Done – looks like all the sitelinks were added by others in the meantime. @BCN63: Next time you could also try using the {{Edit request}} template on the talk page (it looks like edit requests are usually processed relatively quickly, though I’ve never done one myself). Lucas Werkmeister (talk) 16:28, 23 September 2024 (UTC)Reply
It won't be necessary. I abandon Wikipedias due to the constant threats of mass deletion of content against the Biquipedia in Aragonese. As I have read on social networks from another former collaborator, hatred against my language is demonstrated here. Bye bye. BCN63 (talk) 18:00, 23 September 2024 (UTC)Reply

Wikidata REST API openapi.json should include components/securitySchemes

edit

I have submitted the current version of the openapi.json (with additional extensions for APIs-guru openapi directory) which is a database of sorts used for developing, validating, and configuring clients using VSCode through Kiota. Kiota has a search feature where "wikidata" currently does not resolve, only "wikipedia".

My PR Adds Wikidata REST API #1299 submitted to them can be reviewed by our Wikidata team, where I added the `components/securitySchemes` along with various `x-` extensions the api directory and Kiota uses. I would hope and expect that the Wikidata team could also add the same or an improved vision of my `components/securitySchemes` to the official Wikidata REST API openapi.json at some point in the future? I unfortunately could not open a Phabricator ticket myself for this task, because I constantly get "too many requests" when trying to access Phabricator main page. -- Thadguidry (talk) 09:09, 4 October 2024 (UTC)Reply

I made a ticket and added it to our backlog: https://phabricator.wikimedia.org/T376703. We'll try to get to it as soon as the main priorities have been taken care of. Thank you! Ifrahkhanyaree WMDE (talk) 09:51, 8 October 2024 (UTC)Reply

Right ascension (property:P6257) and declination (property:P6258)

edit

Right ascension and declination do not accept the formats commonly found in sources. Right ascension should support decimal archours (HH.hhhhhh,,,), sexagesimal archours (HH:MM:SS.sss...), sexagesimal arcdegrees (DDD:MM:SS.sss...); not just decimal arcdegrees (DDD.ddddd...). Declination should support sexagesimal degrees, not just decimal degrees. Without supporting these formats, the reference used to identify the value would be useless to many people who are not consersant in the formulae used to convert between the formats, in order to check against the value found in the reference. Particularly, SIMBAD, the standard astronomical database, uses sexagesimal hours and sexagesimal degrees in its data display; while NED has decimal hours and decimal degrees.

Sexagesimal degrees and hours may be also expressed as (+/-)X:MM.mmm.... with a decimal attached to the minutes instead of a decimal attached to the seconds.

There are 24 hours of arc in a circle, while there are 360 degrees of arc in a circle. There are 60 minutes of arc in an arc hour or arc degree, and there are 60 seconds of arc in an arcminute.

-- 65.92.246.77 16:04, 11 October 2024 (UTC)Reply

Hello, thank you for your feedback! Adding support for these additional formats in the properties is a valid point. However, this would need to be discussed with the community first, particularly at Wikidata talk:WikiProject Astronomy. I encourage you to bring it up there, as community input will be valuable in determining whether and how to expand the accepted formats for these properties. -Mohammed Abdulai (WMDE) (talk) 08:22, 21 October 2024 (UTC)Reply

Property suggestion

edit

On pages about humans, e.g. Marta Binaghi (Q113804335), which have VIAF and GND already, when trying to add a property,

  1. I got property:P7859 as suggestion, which is deleted
  2. I didn't get ISNI, which is very common for items about humans

Please remove P7859 and make ISNI showing up. Lorenz Karsten (talk) 14:45, 23 October 2024 (UTC)Reply

Thank you! I've filed a ticket to address this at T377986. Lydia Pintscher (WMDE) (talk) 16:31, 23 October 2024 (UTC)Reply

Could not add label -mul- without reverting to a version that had such a label

edit

Talk:Q109487867#Label_mul Lorenz Karsten (talk) 09:31, 24 October 2024 (UTC)Reply

Wikibase REST API: misspelled CORS header value

edit

I'm trying out using the Wikibase REST API in a HTML/Javascript thingimagic but I'm having trouble with CORS not letting me complete some requests.

I'm using the Endpoint POST /entities/items/{item_id}/statements to add a new statement to an item and the Access-Control-Allow-Headers value has a misspelled header name: The documentation says I can use the If-Match header, but this is the Access-Control-Allow-Headers response when Firefox sends the OPTIONS preflight request, which results in Firefox not allowing my request to complete:

Accept, Accept-Language, Content-Language, Content-Type, Accept-Encoding, DNT, Origin, User-Agent, Api-User-Agent, Access-Control-Max-Age, Authorization, X-Wikimedia-Debug, If-Mach, If-None-Match, If-Modified-Since

As you might see, it includes If-Mach which I assume is a misspelled form of If-Match. Lokfahrer (talk) 16:20, 24 October 2024 (UTC)Reply

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy