Open main menu

Wikidata:Contact the development team

Contact the development team

Wikidata development is ongoing. You can leave notes for the development team here, on #wikidata connect and on the mailing list or report bugs on Phabricator. (See the list of open bugs on Phabricator.)

Regarding the accounts of the Wikidata development team, we have decided on the following rules:

  • Wikidata developers can have clearly marked staff accounts (in the form "Fullname (WMDE)"), and these can receive admin and bureaucrat rights.
  • These staff accounts should be used only for development, testing, spam-fighting, and emergencies.
  • The private accounts of staff members do not get admin and bureaucrat rights by default. If staff members desire admin and bureaucrat rights for their private accounts, those should be gained going through the processes developed by the community.
  • Every staff member is free to use their private account just as everyone else, obviously. Especially if they want to work on content in Wikidata, this is the account they should be using, not their staff account.
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 2019/02.

Development plan Usability and usefulness Status updates Development input Contact the development team


Monolingual string language code ("cnr")Edit

Please add "cnr" for Q7700307#P1705. I found it on the enwiki article about Montenegrin (Q8821).
--- Jura 11:54, 25 January 2018 (UTC)

I've created T185800 for this and patch will follow soon. But before it can be merged, approval by LangCom is needed. Mbch331 (talk) 10:30, 27 January 2018 (UTC)
@Millosh: what do you think ? It's a request for a language code at Wikidata (not a new wiki/interface language).
--- Jura 17:20, 28 January 2018 (UTC)
It's a valid language code (per [1]) and I see no reason why it shouldn't be added. --Millosh (talk) 19:14, 2 February 2018 (UTC)
Is that a personal statement or an official statement from the langcom? If the latter, please add a statement to phab:T185800. Mbch331 (talk) 20:15, 2 February 2018 (UTC)
@Mbch331: thanks for the patch. I think you can go ahead with it @Millosh: is the m:Language_committee#Current member knowledgeable about this language (or closely related ones). --
--- Jura 07:20, 3 February 2018 (UTC)
@Jura1: My part of the work is done anyway. I don't have the right to merge patches. That's only to the WDME devs. I'm just a volunteer dev that submits patches. Mbch331 (talk) 07:23, 3 February 2018 (UTC)
  • It still needs to be addressed.
    --- Jura 10:33, 12 March 2018 (UTC)
    • I've added a comment to the ticket that there is Langcom approval. Mbch331 (talk) 13:02, 12 March 2018 (UTC)
I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. Patch for T185800 has been merged. Next passing of the train it will be live. Mbch331 (talk) 18:42, 15 March 2018 (UTC)

{{Section resolved|1=--Lydia Pintscher (WMDE) (talk) 08:23, 23 April 2018 (UTC)}}

  • Finally, what was it?
    --- Jura 11:14, 24 April 2018 (UTC)
We're still working on solving this issue. It's a tough one. Lea Lacroix (WMDE) (talk) 12:24, 24 April 2018 (UTC)
  • It actually works. So what was needed to make it work?
    --- Jura 09:42, 1 May 2018 (UTC)
    • Still open.
      --- Jura 09:00, 31 May 2018 (UTC) --- Jura 09:42, 1 May 2019 (UTC)

Let's get this section archived. There is nothing won by keeping it here. The ticket is open. --Lydia Pintscher (WMDE) (talk) 12:42, 27 January 2019 (UTC)

  • It somehow illustrates a lack of feedback to the community on arcane interna in the development processes. Can we have a least a summary understandable by a random contributor about what needs to be done and how long that may take? --- Jura 13:14, 27 January 2019 (UTC)

Placement in identifier sectionEdit

To detail a point brought up earlier, is it possible to add an option to place statements of a few properties (e.g. P1036, sample use: Q64#P1036) in the identifier section of pages (in the sample Q64#identifiers). Currently the sort seems to be based exclusively on datatype.
--- Jura 06:52, 17 February 2018 (UTC)

Why not simply change P1036 to external-id datatype? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:51, 17 February 2018 (UTC)
Dewey Decimal Classification (P1036) is not an identifier but classifier. An identifier identifies an unique instance of class. In contrast, a classifier is used to tag all instances of a class. For example the code 813.54 means American narrative prose from 1945 to 1999. If P1036 is an identifier, we would add that code to the item about the class of American narrative prose from 1945 to 1999. But since P1036 is used as classifier, we add the code to all instances of that class. --Pasleim (talk) 14:10, 17 February 2018 (UTC)
would be more useful to have such classes on Wikidata and to use this property only on the class item. This would allow us to encode the class definition as statements in Wikidata and to infer instances automatically, for example with {{Implied instances}}. Or to add automatically the statements in the class item to the explicit instances of it without having to put the logic into the bot (or an out wiki inference rule). author  TomT0m / talk page 14:17, 17 February 2018 (UTC)
In one sense, certainly; but we have plenty of other external-id properties on Wikidata that "identify" classes of things. Do we really add Dewey codes to every item about a book with that code? The examples on the property page certainly do not suggest that. I also note that, in the property proposal, User:Merrilee of OCLC said "The Dewey identifiers are just that -- identifiers... I had an in depth conversation with the Dewey Editor, Michael Panzer, last week and this use of Dewey identifiers as free for all to use lines up with his understanding as well.". Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:17, 17 February 2018 (UTC)
  • I think the datatype of one or the other properties for which this can apply should be discussed elsewhere. I think there is a general need for this.
    --- Jura 08:24, 20 February 2018 (UTC)
  • It is currently possible to create a section based on a list of datatypes or on a list of properties but not both. And I don't think we can spend time on it without having a good reason why these properties can't just be converted to external identifier. --Lydia Pintscher (WMDE) (talk) 16:26, 7 March 2018 (UTC)
    • What could we do about exact match (P2888)? There are obviously some that could be converted, but others that can't. There is also the group of identifiers that emerged during the conversion discussion and remained with string datatype.
      --- Jura 08:54, 13 March 2018 (UTC)
      • I'd say as a next step the discussions about the remaining ones need to be concluded. I am not sure what they are held up on. --Lydia Pintscher (WMDE) (talk) 10:45, 15 March 2018 (UTC)
        • Even for the ones that are already in the "not to be converted section", some are identifiers and have formatter urls. BTW exact match (P2888) has url datatype and I think it should be in the identifier section.
          --- Jura 11:34, 15 March 2018 (UTC)
          • @Lydia Pintscher (WMDE): can we move ahead with this?
            --- Jura 07:01, 19 April 2018 (UTC)
            • I am not sure what I can do. It needs editor consensus and then I can move ahead with scheduling the conversion. Or am I missing something? --Lydia Pintscher (WMDE) (talk) 08:25, 23 April 2018 (UTC)
              • What would you want to convert exact match (P2888) into?
                --- Jura 11:15, 24 April 2018 (UTC)
                • It seems fine to me as it is but I might be missing something. In general this is a decision I'd like the editors to come to rough consensus on and if that doesn't work I can make a decision but only then. It takes me time to get into the details of the discussion and make the right overall decision and I'd rather not do that if not absolutely needed. --Lydia Pintscher (WMDE) (talk) 09:45, 26 July 2018 (UTC)
                  • Other than you, I don't think anyone wanted to convert exact match (P2888) to another datatype (currently URL). The request here is to place it in the identifier section. The same goes for some of the properties with string datatype. It seems fairly trivial as a request. I get the impression that Wikidata development might have been absorbed by lexemes.
                    --- Jura 07:56, 27 July 2018 (UTC)
  • Seems this is still open.
    --- Jura 09:05, 31 May 2018 (UTC)
    --- Jura 11:15, 24 April 2019 (UTC)

Can you please formulate a clear request that is left over here now? I am a bit lost as to the exact issue we're still trying to solve. --Lydia Pintscher (WMDE) (talk) 12:45, 27 January 2019 (UTC)

  • Whatever their datatype, it should be possible to place P1036 and P2888 in the identifier section (i.e. under the Heading "identifiers" on entities). --- Jura 13:16, 27 January 2019 (UTC)

Formatter url and string datatypeEdit

A problem brought up further up on this page. It seems that this works sometimes and sometimes it doesn't. What's is the development status on this? I think ideally this would work as for "external id"-datatype when the url is set on a property.
--- Jura 08:30, 20 February 2018 (UTC)

I checked and it is possible to do. Can you give me 2 or 3 examples where this would hold and not be an external identifier? I need to look into some of the details because of the RdF export before someone can work on it. --Lydia Pintscher (WMDE) (talk) 10:59, 15 March 2018 (UTC)
Full list:
--- Jura 11:41, 15 March 2018 (UTC)
Ok should be doable. Can you open a ticket for it? Or Léa? --Lydia Pintscher (WMDE) (talk) 14:34, 13 April 2018 (UTC)
Léa? That would be helpful. Apparently, I can't write tickets. Besides, I surely wouldn't find it if someone had already opened one.
--- Jura 14:53, 13 April 2018 (UTC)
done, phabricator:T192188 --Pasleim (talk) 00:25, 14 April 2018 (UTC)

I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. --Lydia Pintscher (WMDE) (talk) 08:26, 23 April 2018 (UTC)
  • The point that might be missing in the phab ticket is that when the formatter url is qualified with a regex, then this should be taken into account. What would be the next steps?
    --- Jura 11:17, 24 April 2018 (UTC)
  • Seems this is still open.
    --- Jura 09:05, 31 May 2018 (UTC)
    --- Jura 11:15, 24 April 2019 (UTC)
    @Jura1: to update signature to hold up bot auto-archiving you can just replace the old one, learn me. --Liuxinyu970226 (talk) 11:02, 29 September 2018 (UTC)

Let's get this section archived. There is nothing won by keeping it here. The ticket is open. --Lydia Pintscher (WMDE) (talk) 12:41, 27 January 2019 (UTC)

Userrights list ?Edit

Where could I find a list of avaible user rights for Wikibase Repository ? Thank you --CreativeC (talk) 21:50, 1 February 2019 (UTC)

@CreativeC: You mean Special:ListGroupRights? Bencemac (talk) 08:29, 2 February 2019 (UTC)
@Bencemac: I mean a page of documentation that includes all User rights I can give to usergroups through $wgGroupPermissions['group']['right'] = true; in Localsettings.php (i.e. property-create) --CreativeC (talk) 17:23, 2 February 2019 (UTC)
@CreativeC: Check out mw:Manual:User rights. It might be a bit messy, the help for some special rights links from MediaWikiWiki mw: to Meta m: (or rather, that's how it was in 2016). As long as there are no red links on Special:ListGroupRights here the local explanations are relevant, apparently various policies here. The technical stuff incl. the precise PHP user right name is always on mw:. – 15:06, 5 February 2019 (UTC)
@CreativeC: From
	// rights
	// names should be according to other naming scheme
	$wgGroupPermissions['*']['item-term'] = true;
	$wgGroupPermissions['*']['property-term'] = true;
	$wgGroupPermissions['*']['item-merge'] = true;
	$wgGroupPermissions['*']['item-redirect'] = true;
	$wgGroupPermissions['*']['property-create'] = true;
	$wgAvailableRights[] = 'item-term';
	$wgAvailableRights[] = 'property-term';
	$wgAvailableRights[] = 'item-merge';
	$wgAvailableRights[] = 'item-redirect';
	$wgAvailableRights[] = 'property-create';
	$wgGrantPermissions['editpage']['item-term'] = true;
	$wgGrantPermissions['editpage']['item-redirect'] = true;
	$wgGrantPermissions['editpage']['item-merge'] = true;
	$wgGrantPermissions['editpage']['property-term'] = true;
	$wgGrantPermissions['createeditmovepage']['property-create'] = true;

--GZWDer (talk) 17:52, 9 February 2019 (UTC)

Thank you --CreativeC (talk) 18:20, 9 February 2019 (UTC)

additional mwapi:endpoint - de.wikisource.orgEdit

is it possible to add as additional mwapi:endpoint for the wikidata query service? thanks in advance --Mfchris84 (talk) 10:32, 6 February 2019 (UTC)

@Smalyshev (WMF): *poke* :) --Lydia Pintscher (WMDE) (talk) 19:50, 10 February 2019 (UTC)


Are there plans to add Wikimaniawiki / wmania: (in the wikimedia family) to WD? Or has the wiki specifically excluded on policy grounds?

Noting that this wiki is being added to carry the 2019 WM, and will eventually house the earlier wikis as they work out the plan to merge those. And asking as the wiki is now starting to be populated, and it should be part of our thinking as we design for the persisting nature of this wiki, and managing its content namespaces. Thanks.  — billinghurst sDrewth 11:45, 9 February 2019 (UTC)

I don't think there is anything generally preventing it. I'd need to check if they're on the right servers. However keep in mind that if they are all merged together into one wiki then you'd likely have different articles that would be connected with the same item, which isn't possible in the same wiki. --Lydia Pintscher (WMDE) (talk) 19:53, 10 February 2019 (UTC)
@Lydia Pintscher (WMDE): As there are no wikimania wikis existing in the OTHER group, I don't think that this will be an unresolvable or overly problematic issue. It is intended that the "by year" content is going into unique namespaces by wikimania (named by YYYY:,) and each event at a WM is a unique event/edition, so would have its own item, though may be part of a series, or have some common parent unit that ties them together.

Otherwise leaving the other namespaces as standard, that is one each of main, project, user, template, help, etc.  — billinghurst sDrewth 11:44, 18 February 2019 (UTC)


As you can see here [2] I'm struggling to edit Wikibase repository's sitelink. Where to edit them ?

--CreativeC (talk) 17:23, 11 February 2019 (UTC)

I am not a developer, however, these are all Mediawiki: ns messages, so just create/edit the message names in namespace to force them to exist. That said, looking at api allmessages if you were looking to get them natively, then they are not appearing through your configuration, just WP is showing.  — billinghurst sDrewth 00:10, 14 February 2019 (UTC)

wrong edit summariesEdit

Hey, in this edit the statement native language (P103)=Spanish (Q1321) was removed but the edit summary states native language (P103)=Russian (Q7737). --Pasleim (talk) 09:04, 15 February 2019 (UTC)

@Pasleim : your "this edit" is not a link to an edit, but new section.  — billinghurst sDrewth 12:12, 18 February 2019 (UTC)
Oops, wrong link copied. Now corrected. --Pasleim (talk) 13:12, 18 February 2019 (UTC)
Thanks. Have you seen this happen anywhere else already or is this the only case? Either way I'll have a look. --Lydia Pintscher (WMDE) (talk) 16:20, 18 February 2019 (UTC)