Shortcut: WD:DEV

Wikidata:Contact the development team

From Wikidata
Jump to navigation Jump to search

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/11.

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

Primary Sources tool down[edit]

After a lot of grant money went into developing the primary sources tool, it seems down at the moment. What's the current status? Will it come back online again in the future? ChristianKl❫ 07:59, 8 October 2019 (UTC)

I just pinged its author. Lea Lacroix (WMDE) (talk) 11:01, 14 October 2019 (UTC)
@Lea Lacroix (WMDE): any update? In case that the original authors won't continue with the tool it seems to me like it would make sense for WMDE to see that it keeps working to not waste the development of it. ChristianKl❫ 12:54, 23 October 2019 (UTC)
I got in touch with one of the developers who told me they were looking at it. Is it still down? Is there a Phabricator ticket giving more details? Lea Lacroix (WMDE) (talk) 16:38, 23 October 2019 (UTC)
It's still down. I'm not aware of an existing Phabricator ticket. To reproduce: If you have the gadget activated and click on Random Primary Sources item on the left side you get shown an error. ChristianKl❫ 10:21, 11 November 2019 (UTC)

Missing sitelinks after merging[edit]

For the second time within a week, User:Olaf Studt has reported an issue regarding apparently lost sitelinks after a merge via Wikidata:Forum. Example is the merge of Q63991526 into Q42724514, and the scenario is:

Any idea what's on here? It seems that some steps of a proper merge are not properly done. I don't have a phab topic yet, but given that this is the second reported incident within a week, it seems we need one here right? (For the record: the other incident happened in Q8325483 on 16 October, but I already tidied everything manually as I thought it might have been a one-time glitch.) —MisterSynergy (talk) 10:57, 22 October 2019 (UTC)

I think this is a regular problem since the end of September; also see Wikidata:Project_chat/Archive/2019/10#Unable_to_edit_Q6308220 and Wikidata:Project_chat/Archive/2019/10#Merged_but_not_attached. Thanks. Mike Peel (talk) 11:44, 22 October 2019 (UTC)
A live example: Category:Paddington Bear (Q9619464) (look at the commons and enwp categories). Thanks. Mike Peel (talk) 19:18, 30 October 2019 (UTC)
Also Q9452943. Thanks. Mike Peel (talk) 19:46, 30 October 2019 (UTC)
Could someone please open a ticket for this? This seems serious and we need to investigate it. (Sorry - in the middle of packing for a trip.) --Lydia Pintscher (WMDE) (talk) 21:29, 5 November 2019 (UTC)

Query no longer working[edit]

The following query was working fine until recently (see history of ListeriaBot updates). Now, there is a systematic timeout error. Could you have a look at it, please?

SELECT (wd:Q5 as ?item)(COUNT(DISTINCT ?item) as ?count)
    hint:Query hint:optimizer "None".
    ?item wdt:P131+ wd:Q142.
    ?item (wdt:P31/wdt:P279*) wd:Q16970
  MINUS { ?item wdt:P625 [].}

Try it! }

Thanks. Ayack (talk) 10:43, 26 October 2019 (UTC)

Bar chart[edit]

I asked if I can force colors in the bar chart view and someone said to me that it's not possible (for now?). I also tried to order by the x-axis, without success (see the query below).
So, I want to know if these features are planned for the bar chart view ?

select distinct ?législatureLabel (count (distinct ?item) as ?count) ?groupeLabel ?rgb where {
SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". } 
?item p:P39 ?fonction ; 
      wdt:P39 wd:Q15964890 .
?fonction ps:P39 wd:Q15964890 ;
          pq:P4100 ?groupe ; 
          pq:P2937 ?législature ; 
          pq:P768 ?circonscription . 
  optional { ?groupe wdt:P465 ?rgb }
group by ?législatureLabel ?groupeLabel ?count ?rgb
order by desc (?législatureLabel)

Try it!

Simon Villeneuve (talk) 13:25, 28 October 2019 (UTC)

Currently we unfortunately don't have the resources to work on that. Sorry :/ --Lydia Pintscher (WMDE) (talk) 21:31, 5 November 2019 (UTC)

Purge deleted items from Query Service servers[edit]

Hey dev team, there are currently some hundred items which have been deleted, but for some reason the deletion did not happen on the Query Service which still delivers the deleted data; this is not a new problem, it just happens occasionally.

In the past I have consulted User:Smalyshev_(WMF) in his role as WDQS technician (see Topic:Uzprcez2q7vnccvg for instance); Stas was able to purge these items from the Query Service servers using some internal maintenance script. Is there already a successor on his position whom I can contact occasionally for similar requests? Thanks, —MisterSynergy (talk) 22:12, 29 October 2019 (UTC)

Unfortunately not. The WMF is currently looking for someone to fill the position. But there are other people who could give it a try. Could you file a ticket and then Léa and I can poke the right people and push it up their todo list. --Lydia Pintscher (WMDE) (talk) 21:32, 5 November 2019 (UTC)
I wrote a new phab ticket Provide public "reload entity to WDQS" API which is clearly related, although not directly aimed to solve this problem. —MisterSynergy (talk) 10:46, 6 November 2019 (UTC)

Integration of Content translation with Wikidata[edit]

Some months back, ContentTranslation tool was integrated with many languages on Wikipedia. Something similar on Wikidata could be very useful for the translation of labels, descriptions and aliases. Is it interesting to integrate mw:Content_translation with Wikidata? John Samuel (talk) 09:21, 1 November 2019 (UTC)

I'll need to look more into it but so far my impression was that the content translation tool is very much tailored to translating longer texts and isn't really suited for the short descriptions etc. --Lydia Pintscher (WMDE) (talk) 21:34, 5 November 2019 (UTC)
See phab:T64695.--GZWDer (talk) 21:07, 14 November 2019 (UTC)

Please fix the front page[edit]

Screenshot wikidata 2019-11-03-10-44-00-75 anyone can edit

"Anyone can edit" is not properly visible, on Android 10 chrome 78.0.3904.90. 6.37-inch screen. It is not a minor problem, I am talking about the main page of the site. --Eatcha (talk) 05:26, 3 November 2019 (UTC)

This happens on other systems/browsers as well, and there is even more text completely hidden. We can solve it locally without developer input, as all of the code is accessible onwiki in Wikidata:Main Page/Content, Template:Main Page/Header new, and Template:Main Page/Header new/styles.css.
Someone with good HTML/CSS skills willing to have a look? —MisterSynergy (talk) 10:50, 6 November 2019 (UTC)

urn:Wikidata:Q2013 ?[edit]

While experimenting with URN formatter (P7470), I was wondering if it would be worth registering "Wikidata" as a namespace for URNs (see w:Uniform_Resource_Name#Namespaces). rfc8141 describes how it's done.

The main benefit would probably be that it inserts Wikidata's entities in an older scheme of the internet. --- Jura 10:41, 3 November 2019 (UTC)

I'm not sure if it's worth spending time on it to be honest. But I'll ask around a bit if other people think it gets us anything worthwhile. --Lydia Pintscher (WMDE) (talk) 21:39, 5 November 2019 (UTC)
@Lydia Pintscher (WMDE): Sounds good. These days I went through some of the URN documentation (on Wikipedia and elsewhere): lots of stuff seems historic, but there appears to be some regain of interest in this: e.g. Maritime Resource Names are being rolled out for ships and lighthouses, Life Science Identifiers seem common.
Widely used UUID can also be defined as URNs. SPARQL includes features for these. URN formatter (P7470) provides support for others' URNs.
Most of all, the URNs define Wikidata entities fairly well.
From the WMDE side, I don't think that much is required (you'd need to mail-in the form). If we want to go through drafting an (optional) RFC, that would need to be submitted too.
You might want to talk to @EvanProdromou: who seems to be involved in their namespace definitions. --- Jura 22:00, 5 November 2019 (UTC)
@Lydia Pintscher (WMDE): unless you see some issues on your side, I can ask around here and try to develop a proposal. Obviously, if WMF/WMDE wont mail it in, it might not be worth the effort. --- Jura 12:56, 13 November 2019 (UTC)
I don't see an issue right now, no. --Lydia Pintscher (WMDE) (talk) 18:54, 13 November 2019 (UTC)

WQS: Query lag displayed ("data updated a minute ago") doesn't match actual lag[edit]

Not sure what's happening .. --- Jura 08:45, 4 November 2019 (UTC)

Wikidata server locations and power outages[edit]

It seems that some servers of Wikidata (and WMF) are located in regions prone to power outages.

Is there a plan to relocate them? Supposedly WMF doesn't have the funds for a "Getty"-plan to mitigate that. --- Jura 12:46, 4 November 2019 (UTC)

Found --- Jura 06:59, 5 November 2019 (UTC)
I don't know but I trust the operations team at the WMF to be on top of keeping the websites running through things like serving content from several different data centers for example. So not something that currently keeps me up at night (compared to other things ;-)). --Lydia Pintscher (WMDE) (talk) 21:41, 5 November 2019 (UTC)

sitelinks for[edit]

Can we activate that? --- Jura 06:59, 5 November 2019 (UTC)

@Addshore: Is that possible or is wikitech on a different cluster? --Lydia Pintscher (WMDE) (talk) 21:42, 5 November 2019 (UTC)

Place for help for Wikibase[edit]

Currently, it seems that people who want to use Wikibase don't have a good place to turn and as a result some of the questions end up in our project chat for Wikidata where they don't really belong. There should be a central place where people who seek help can be directed. ChristianKl❫ 16:00, 6 November 2019 (UTC)

It seems that for now, the two main discussion channels that are used by people using Wikibase are the mailing-list (no very active) and the Telegram group (very active). Questions about the software can be asked on this page (contact the development team). If we need another place onwiki (eg a Wikiproject), I'm of course fine with that, but I'll let the active community decide what they think is best, and create the page by themselves. Lea Lacroix (WMDE) (talk) 16:55, 6 November 2019 (UTC)
A wiki page to complement the TG group would be nice for better-versioned (and possibly slower + refactorable) collective change over time :) @ChristianKl: want to start something here? Sj (talk) 20:23, 8 November 2019 (UTC)

Surplus of coordinates - T198078[edit]

Right now I'm getting 2 rows from this query where I expect 1 (the item Lennoxlove House (Q6522893) has only one coordinate). From discussion at Wikidata:Request_a_query#Surplus_of_coordinates this is possibly akin to phab:T198078, on which I've left a note.

SELECT ?item ?itemLabel ?stat ?lat ?long 
  VALUES ?item {wd:Q6522893}
  ?item p:P625 ?stat. ?stat psv:P625  [wikibase:geoLatitude ?lat ; wikibase:geoLongitude ?long ]  . 
  SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". }

Try it!

Auchendinny House (Q17567523) has the same problem; I suspect I can come up with others is needed. --Tagishsimon (talk) 18:25, 6 November 2019 (UTC)

This query results in a number, several hundred, of statements where there are multiple values for lat or long, mostly for both. The query is limited to objects with country (P17) equals Germany (Q183) to prevent a timeout, but the problem appears to be "global".
SELECT ?item ?itemLabel ?stat ?lat ?long WITH {
SELECT ?item ?stat (COUNT(?lat)+COUNT(?long) AS ?count) WHERE {
VALUES ?countries { wd:Q183 }
?item wdt:P17 ?countries;
      p:P625 ?stat. ?stat psv:P625  [wikibase:geoLatitude ?lat ; wikibase:geoLongitude ?long ]  . 
GROUP BY ?item ?stat
} AS %i WHERE {
  include %i
  ?stat psv:P625 [ wikibase:geoLatitude ?lat; wikibase:geoLongitude ?long ] .
  SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". }
ORDER BY ?item
Try it!
One of the values in a "pair" seems always to be rounded to 4 decimals while the other value is not rounded.
--Larske (talk) 19:55, 6 November 2019 (UTC)

Image not shown in suggester when typing exact name[edit]

I reported this bug a while ago, it was corrected (I can't find the phabricator ticket), but it's back again. I want to add image (P18): "Eglise Notre-Dame-de-l'Assomption.JPG" on Q73864980, so I paste this exact string, but none of the files displayed below were the right one. At least, I was able to save it, but it's really strange. Ayack (talk) 09:24, 7 November 2019 (UTC)

Yes, I remember this ticket! Let me dig in the deep waters of Phabricator and reopen it ^^ Thanks for reporting and sorry for the trouble. Lea Lacroix (WMDE) (talk) 09:59, 7 November 2019 (UTC)
Merci Léa. Ayack (talk) 10:37, 7 November 2019 (UTC)

Configurating months with SI time unit[edit]

Hello, given this query, months appear to not having a SI time unit defined. I know there is no SI definition for months but it would be helpful to have something that helps calculations for the p:P2047/psn:P2047/wikibase:quantityAmount to work ? Would it nevertheless be possible to store in the Query Server config a value as following : 2629746 seconds? (based on an average) or 2592000 seconds (based on a simple calculation * 30 days) ? Bouzinac (talk) 11:46, 9 November 2019 (UTC)

Query server keeps lagging (> 6h)[edit]

It seems to go up and down for days now. Would you look into it? --- Jura 13:04, 10 November 2019 (UTC)

Thanks for reporting, we are monitoring it. FYI our colleagues at WMF are looking into deploying a new updater, with the hope of reducing these lagging phases: phab:T231411. Lea Lacroix (WMDE) (talk) 16:55, 11 November 2019 (UTC)
Looks like they hired someone .. --- Jura 09:43, 13 November 2019 (UTC)
Did they?
There was an email sent to the wikidata-l mailing list yesterday by User:GLederrey (WMF), with some new background. According to the email, now they “are trying to share the responsibility of WDQS more across the [Search Platform] team”. For me it sounds as if they are not looking for a successor for User:Smalyshev_(WMF) and longer, and are trying to distribute his work within the existing team.
WDQS lag is meanwhile at steady 11 hours on the two most used servers Face-sad.svgMisterSynergy (talk) 12:59, 13 November 2019 (UTC)
To me it was never really clear why this isn't being done in the same team as the reminder of Wikibase. They also work on Commons though.
Obviously, it is a good idea to share it among several people. I came across this. Maybe you want to add some stuff there ;) --- Jura 13:05, 13 November 2019 (UTC)
Indeed, the work is split between WMF (infrastructure) and WMDE (GUI). We're working together on the Query Service. An email got sent with more information. Thanks for your patience. Lea Lacroix (WMDE) (talk) 10:35, 14 November 2019 (UTC)

Suggestions for the next iteration of item value value suggestions[edit]

It might be worth doing another of the annual (?) iterations to improve the suggestions one gets when adding statements manually to Wikidata.

Here a few:

  • (1) When adding statements, we currently get suggestions from "one of constraints" on properties. The same could work when adding qualifiers (e.g. P5102#P2302 for qualifier nature of statement (P5102)). Also, it might be worth being able to restrict that by a specific constraint on the property the qualifier is being used on (see the experimental one-of qualifier value property constraint (Q52712340)).
  • (2) Similarly, units could be suggested from units in property constraints.

I'm sure we could come up with a few more. --- Jura 13:04, 10 November 2019 (UTC)

Hello, the page Wikidata:Suggester ranking input is still open for suggestions, feel free to add them there. Lea Lacroix (WMDE) (talk) 08:47, 11 November 2019 (UTC)
Sounds good. Could you update the page with more recent plans? It reads "currently" and links to an email from 2017. --- Jura 10:12, 12 November 2019 (UTC)

Commons link should exist 201911[edit]

Has there been a phab ticket? The bug is still bugging users: c:special:permalink/374564932#debugging_a_creator_page.

A previous report: Wikidata:Contact_the_development_team/Archive/2019/06#Commons_link_should_exist.--Roy17 (talk) 17:14, 10 November 2019 (UTC)

Thanks for reporting the issue and for your patience. Lea Lacroix (WMDE) (talk) 08:34, 11 November 2019 (UTC)

make constraint conflicts more timely/prominent[edit]

After editing WD for some months I'm starting to get an overview and identify weak spots, for example, property constraint conflicts. The value of WD is dependent on how well constraints are enforced. I think feedback from a wrong edit needs to be instantly (always directly after input not mostly after page reload), or if that's not possible, there should be a page per user showing the conflicts caused by her edits, together with some notification. At the moment, if I'm not actively seeking the info by comparing conflict queries before/after, the system depends on others doing that. BTW, it seems the conflict info on the properties' discussion pages does not get synced at all, and of the >3 SPARQL queries offered per constraint only one gives timely info. Which can create the illusion everything is fine, while other people already are reacting. In summary, more clarity with constraints, their violation, and the right tools would be very helpful and increase the value of the database. --SCIdude (talk) 17:29, 10 November 2019 (UTC)

Hello @SCIdude: and thanks for your feedback.
As a logged in user, you should have the constraints extension activated. This extension displays a little icon in front of a statement as soon as the edit is saved, in order to inform you about a constraint (see the different icons here). Do you see these when editing? This is our last up-to-date system to check on constraints.
If you want, you can also access the constraint reports (attention, the page is long to load), updated by bot, and not always exactly synchronized.
Could you point me to examples of discussion pages and where queries are not up to date? Lea Lacroix (WMDE) (talk) 14:26, 11 November 2019 (UTC)
I have the constraints extensions, they do not always show immediately: often after a few seconds, often after a reload. For the reverse (i.e. disappearing after fixing the constraint) there is often an additional message saying it may not be in sync for several minutes. So I have doubts about your statement. As for wildly different reports/queries see e.g. the single value constraints of Property_talk:P683: the ready-made report has 1656, the first SPARQL query gives 154 (after removing the LIMIT 100), and the SPARQL (new) query results in 6 hits. I think the middle one is the most current. Can you please fix such discrepancies in general? That would be a good first step. --SCIdude (talk) 16:16, 11 November 2019 (UTC)

Reset my bot password[edit]

I have forgotten my bot User:AVMbot password and I did not set any email address in its settings. How can I reset its password? (I have already asked at Wikidata:Administrators' noticeboard#Reset my bot password). --Albert Villanova del Moral (talk) 18:12, 10 November 2019 (UTC)

Two ways:
  • Contact T&S (ca at to request password reset (this is not always granted)
  • Create a new bot account, and you may request to usurp your old bot username at m:SRUC (recommended)

--GZWDer (talk) 18:18, 10 November 2019 (UTC)

Label doesn't display on collection (P195)[edit]

On some, but apparently not all items for works of art, where Property collection (P195) should read "Collection" only "P195" is displayed (at least in English). See for instance the missing label at Mona Lisa (Q12418), but the correct label at Peasants on the cart (Q28062102). I've checked on two different browsers, signed in and not, and the problem persists. I mentioned the issue at property talk and was told to "file a bug." Can someone more savvy than I look into this (and file a more more formal bug fix if needed}? I'm not a computer programmer. Thanks -Animalparty (talk) 18:41, 10 November 2019 (UTC)

I can reproduce your issue. I tried a purge on the page but it did not help. See also phab:T172776. Bovlb (talk) 23:05, 10 November 2019 (UTC)
Thanks for reporting. I created a new task. Lea Lacroix (WMDE) (talk) 14:28, 11 November 2019 (UTC)
Hello @Animalparty, Bovlb: The issue should be solved now. Can you have a look at the items where you noticed the issue (and maybe purge them once) and let me know if it still appears somewhere? Thanks! Lea Lacroix (WMDE) (talk) 15:28, 12 November 2019 (UTC)
@Lea Lacroix (WMDE): Thanks! I no longer see any problem on Mona Lisa (Q12418). I'll leave the rest to Animalparty as the original reporter. Bovlb (talk) 16:18, 12 November 2019 (UTC)
@Lea Lacroix (WMDE): Thanks for looking into this. While purging cache on its own doesn't seem to fix it, adding or editing a property seems to make collection (P195) display correctly. Hopefully over time all instances will display correctly. 19:47, 12 November 2019 (UTC)-Animalparty (talk)

I still cannot edit truncated text in the Also_known_as field[edit]

See Old Rhinebeck Cemetery (Q74584948) for example. I reported before and it seemed to be fixed, but no longer is. I cannot edit truncated text in the Also_known_as field. The field is very short because of space and if the text gets truncated it becomes uneditable. Some users say they can edit it others say they cannot. --RAN (talk) 13:16, 12 November 2019 (UTC)

I can edit all entries except "Old Rhinebeck Cemetery (Geonames)", in which a cursor fails to appear. Odd. -Animalparty (talk) 19:51, 12 November 2019 (UTC)

Problems with P735 (given name) label[edit]

@Lea Lacroix (WMDE), Bovlb: Well now that the collection (P195) issue is solved, given name (P735) fails to display on some items. See for instance George Richardson Proctor (Q1508177) and James E. Purdy (Q18673008). Edits and purging caches doesn't seem to help. It looks like the issue has been brought up at phab:T237984. -Animalparty (talk) 01:39, 13 November 2019 (UTC)

Deleted items still on query server[edit]

Please check Wikidata:Database_reports/to_delete/empty_category_items, some of the redlinks were deleted weeks ago, but still live on query server. --- Jura 09:30, 13 November 2019 (UTC)

This is the same problem as #Purge deleted items from Query Service servers on this page. I have much more items to be purged from the WDQS servers than listed on that report page, in case someone want to help here. —MisterSynergy (talk) 12:46, 13 November 2019 (UTC)
Oh, indeed. In addition to developing an API, it would be good to address the root cause and, at least, regularly do the necessary purges. The later doesn't seem that complicated, maybe a reasonable compromise in terms of resources. --- Jura 12:53, 13 November 2019 (UTC)

Presentation of bounding coordinates[edit]

We have the properties coordinates of northernmost point (P1332), coordinates of southernmost point (P1333), coordinates of easternmost point (P1334), coordinates of westernmost point (P1335) that identify extremal points of a particular area of the world; and which are also currently used to record the bounding box of the area depicted in a map.

When each of these are present, we show four little maps on the wikidata page for the item, eg as at Dundee Combination (Q74766757). But it's not easy to get a sense of the area that together they indicate. I particularly got this from another map person at WikidataCon, User:Librarian lena, that one can't actually *see* the bounding box for the area the map covers, to confirm the sanity of the coordinates -- especially if, like Q56759863, some of the points are in the middle of the sea.

So, when all four of the properties are present, is there any way they could be shown together on the same map -- eg like for Dundee Combination (Q74766757), or for Q56759863 ?

Perhaps the combined map could be shown on the first property, and then suppressed on the remaining three? Or be presented as an additional virtual/'calculated' statement on the wikidata page, immediately before the P1332 to P1335 statements?

Does this seem even remotely possible? It would make the P1332 to P1335 values much more immediately visually accessible. Thanks, Jheald (talk) 13:01, 14 November 2019 (UTC)

Thanks for your request! This looks like something that a gadget or user script could do.
Could you create a Phabricator ticket describing your need? Maybe it can be picked up by a volunteer during a hackathon. Lea Lacroix (WMDE) (talk) 17:14, 14 November 2019 (UTC)

query not in sync[edit]

The item pyraclofos (Q27118010) was merged into Pyraclofos (Q22808806) 19 days ago, but the query server still sees them as distinct. There are more of them, you can check those that I found with the query:

SELECT DISTINCT ?item1 ?item1Label ?item2 ?item2Label ?value 
       ?item1 wdt:P683 ?value .
       FILTER( ?value in ('38876', '16797', '58307', '30067', '30068', '10330', '32044', '18073', '80711') ) .
	?item2 wdt:P683 ?value .
	FILTER( ?item1 != ?item2 && STR( ?item1 ) < STR( ?item2 ) ) .
	SERVICE wikibase:label { bd:serviceParam wikibase:language "en" } .

I can work around it but not very long so it would be nice if this could be fixed (and I mean in general). --SCIdude (talk) 15:04, 15 November 2019 (UTC)

SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". } to output lemma?[edit]

When using ?entity ?entityLabel, this gives the label for items (and properties), but nothing for lexemes. I wonder if it shouldn't output the (or a) lemma. --- Jura 10:20, 16 November 2019 (UTC)

@Jura1: that's very very strange. In effect, this idea is that "label" is - more or less - same as "lemma". This doesn't sound a good idea for many reasons which boild down to "label and lemma are not the same" and they doesn't even behave in the same way : item have usually a lot of label, lexeme only have few lemma ; label exist usually in a lot of language on an item, lemma are usually in a few languages on a lexeme, and so on. In a nushell, my point of view is that label and lemma are too fare different to be called the same.
Plus, the service label syntax is very expensive (causing a lot of time out) and is actually a shorcut for the long syntax of quarying the label but the syntax for lemma is very short, why wanting a shorcut longer than the actual syntax?
Cheers, VIGNERON (talk) 18:59, 17 November 2019 (UTC)
?entityLabel is simple .. much more than some complex UNION query. --- Jura 19:11, 17 November 2019 (UTC)


Hey! How can I remove a user's access to suggestededit-add? I am really tired of fixing the misspelled or completely wrong descriptions from this user. Furthermore, how can I revert contributions in once? I strongly feel that I will not have the strength to fix them one by one. Thanks in advance! Bencemac (talk) 09:15, 17 November 2019 (UTC)

Wikidata:Suggestededit-add 1.0 offers some information. --Matěj Suchánek (talk) 12:09, 17 November 2019 (UTC)
@Bencemac: see also m:User:Hoo man/Scripts/Smart rollback.--GZWDer (talk) 19:38, 17 November 2019 (UTC)

phab:T225856 / phab:T232194[edit]

@Alaa Sarhan (WMDE), Addshore, Adam Shorland (WMDE), Lydia Pintscher (WMDE): Are these two tasks still useful?--GZWDer (talk) 19:37, 17 November 2019 (UTC)