Wikidata:Contact the development team/Archive/2017/02

This page is an archive. Please do not modify it. Use the current page, even to continue an old discussion.

P3503

LombardiaBeniCulturali building ID (P3503) should be external-ID, not string. Is it possible to convert datatype? See Wikidata:Property proposal/LombardiaBeniCulturali ID. Thanks. --M.casanova (talk) 09:31, 31 January 2017 (UTC)

@M.casanova:   Done. Cheers, Hoo man (talk) 15:55, 3 February 2017 (UTC)

Special:ConstraintReport is a nice idea, but quite buggy/incomplete:

  • (Bug) It seems as if it does not handle redirects due to item merges well. Example: Special:ConstraintReport/Q169470 for physicist (Q169470) displays some type violations and indicates that the redirect Q13516667 (and not its redirect target occupation (Q12737077)) is expected as an instance of (P31) relation.
  • (Bug) The links in the constraint columns are quite odd.
  • (Incomplete) A couple of tests wait for implementation for a long time now. Could you please work on this page?
  • (Feature request) Once this page is fully okay, a link to Special:ConstraintReport/Qxxx could be added to the web interface for Q and P namespaces, e.g. in the “Tools” section. It would be a very convenient way to check the formal health of an item or property without browsing through all property talk pages.

Thanks and regards, MisterSynergy (talk) 19:01, 3 February 2017 (UTC)

Léa: Please put the first one in phabricator.
MisterSynergy: We currently have a student working on adding additional constraint checks and integrating them in the item UI. She'll still need a bit of time but is making progress. --Lydia Pintscher (WMDE) (talk) 18:04, 7 February 2017 (UTC)

Constraint violations Q27087831?

I updated page Q27087831 on January 27 and now I'm seeing a bunch of 'constraint violations' under the 'Pages that link to' section. What are all of these? How did they get there? How can I fix them???  – The preceding unsigned comment was added by MNNATL (talk • contribs).

The constraint violation came from this edit where you added a family name instead of a given name. MisterSynergy corrected it [1]. --Pasleim (talk) 09:43, 7 February 2017 (UTC)

Redundant link

Hello.What is the benefit of this text "Cannot revert the edit. The last contributor is the only author of this page."?!It is better to cancel it and the link that we reached by it.Thank you --ديفيد عادل وهبة خليل 2 (talk) 09:33, 7 February 2017 (UTC)

To rollback means undoing all top consecutive edits made by the last editor. If there is only one editor of the page, this action is not possible because this would undo everything including the page creation. --Pasleim (talk) 09:51, 7 February 2017 (UTC)
So, no need for this link if "there is only one editor of the page".Thank you --ديفيد عادل وهبة خليل 2 (talk) 09:54, 7 February 2017 (UTC)
It seems to be trivial but the servers wouldn't agree. Matěj Suchánek (talk) 13:18, 7 February 2017 (UTC)
Please try to fix this error.Thank you --ديفيد عادل وهبة خليل 2 (talk) 15:45, 7 February 2017 (UTC)
You can file a task in Phabricator. Stryn (talk) 15:59, 7 February 2017 (UTC)
I do not know how to participate in that website.I hope that an expert does this (By the way, there are other proposals need to submission).Thank you --ديفيد عادل وهبة خليل 2 (talk) 16:18, 7 February 2017 (UTC)
@ديفيد عادل وهبة خليل 2: that is just mediawiki software standard response. Rolling back from four/three/two/(n+1) edits to zero, is like dividing by zero, it cannot happen, so the system needs to be able to say something. Putting in logic to detect that a rollback cannot take place from the n+1 edit is presumably a complicated process. So as Stryn says, you could try to argue about it in phabricator, or not waste your breath.  — billinghurst sDrewth 05:58, 14 February 2017 (UTC)
@billinghurst, Stryn:Please submit a request because I do not know how to do this.Thank you --ديفيد عادل وهبة خليل 2 (talk) 11:11, 14 February 2017 (UTC)
@ديفيد عادل وهبة خليل 2: You misunderstand. I think that it is a waste of breath submitting a request. It is a mediawiki issue, not a wikidata issue. Totally cosmetic, no change to anything operating.  — billinghurst sDrewth 11:16, 14 February 2017 (UTC)

Addition of qualifier similar to reference addition using API

Hello, is it possible to add all qualifiers in one request like it is possible for references ? Snipre (talk) 22:51, 8 February 2017 (UTC)

@Snipre: Yes, this is indeed possible (for both references and qualifiers), via the wbsetclaim API and also via the very general wbeditentity, which allows editing all of an Entity at a time. Cheers, Hoo man (talk) 08:09, 9 February 2017 (UTC)

Undo don't check for duplicate

Undo don't check for duplicate (label+description), see the history of Q8303734 and Q5827287 about fr label. It is a known bug? --ValterVB (talk) 11:02, 11 February 2017 (UTC)

Although this is a bot edit, it seems to be related to an error that prevents editing: "Could not save due to an error. Item Q300226 already has label "AWN" associated with language code en, using the same description text." when editing Q28753806 ("Awn")? Because this isn't case sensitive it will prevent addition of links such as the one above. Some disambiguation pages differ only by capitalisation, such as Q7389843 and Q350070. Peter James (talk) 17:04, 12 February 2017 (UTC)

Also rollback permit to create duplicate: example. Q4115189 and Q13406268 check italian label and description. --ValterVB (talk) 18:53, 13 February 2017 (UTC)

Adding family name (P734) to presented properties for P18|human (Q5) combination

Would it please be considered that where we have instance of human that one of the offered properties is family name (P734). Thanks.  — billinghurst sDrewth 01:18, 12 February 2017 (UTC)

@billinghurst: The suggestions are computed based on the actual data. While we can remove individual suggestions (like deprecated properties), we don't really have a way to boost certain suggestions. If the property in question gets used more often on items about humans, it will start showing up in the suggestion for these. Cheers, Hoo man (talk) 07:03, 14 February 2017 (UTC)
Thx Hoo. Damn and drat! Presumably those doing bot additions will skew things in that regard too.  — billinghurst sDrewth 09:32, 14 February 2017 (UTC)
So we just need to add it to a few hundred thousand examples, then it will automatically show up... That said, the information is probably available in DEFAULTSORTs on wiki pages and any Persondata templates that still survive. So a bot might well be able to do a job that was really pretty good. Jheald (talk) 23:15, 16 February 2017 (UTC)

Query result shortlink is a tinyurl... and it's forbidden in Wikipedia

Tinyurl is forbidden in Wikipedia, so we can't insert links to results of query.wikidata.org in pages or articles. This is a problem, as results can be interesting for cartography, graphics... -Theklan (talk) 19:54, 16 February 2017 (UTC)

A wikimedia specific short url project is in play (phabricator tickets exist, primarily Wikimedia needs a URL shortener (tracking) and Review and deploy UrlShortener extension to Wikimedia wikis), maybe that is something that should be leveraged for this. Probably worthwhile adding your needs to one of the relevant tickets.

Whitelisting components is too open to abuse unless we have access to a string that is reserved and could not be abused.  — billinghurst sDrewth 04:13, 17 February 2017 (UTC)

Addendum: most url shorteners are actually globally blacklisted, so it is broader than the WPs.  — billinghurst sDrewth 04:14, 17 February 2017 (UTC)
Thanks for the insight! -Theklan (talk) 10:35, 17 February 2017 (UTC)
You should use the full URLs on the wikis. We're not running out of bytes any time soon. Nemo 13:07, 23 February 2017 (UTC)
For some (complicated) queries full URLs are quite long, some older browsers may have problem with these. --Jklamo (talk) 14:34, 23 February 2017 (UTC)
I would have thought that ideally that query.wikidata could actually host its own url shorteners. Anyway, I did add a note about this topic to one of the phabricator tickets that I mentioned above.  — billinghurst sDrewth 01:23, 24 February 2017 (UTC)

It's an interesting question, possibly, as to whether we want to encourage mass use of WDQS, by putting live query links on user-facing pages with potentially a very large readership.

It's one thing to put a tinyurl.com/pqrstuvxy link on a talk page, where only a dozen people may click it copy-paste it; or an SVG or a Listeria table up on a wiki that might (at most) get updated by a script once a day. But a link to a live query on a wiki page could have the potential to really hammer the server.

(On the other hand, I've started doing exactly that on some Commons category pages: diff) Jheald (talk) 10:22, 24 February 2017 (UTC)

Tinyurl is blocked because it is insecure and no to reduce the workload on the server. To link to a query result just link to the full URL instead of using the hackish tinyurl.com/abcdefgh. --Pasleim (talk) 10:40, 24 February 2017 (UTC)