Wikidata:Report a technical problem/Archive/2022/12
|
This page is an archive. Please do not modify it. Use the current page, even to continue an old discussion. |
Merge BR-365
There are two codes for item BR-365, Q115580103 and another in portuguese wiki, I ask you to please merge them, as I don't know how to do it. 2804:14D:5C87:8C5D:383F:EDA7:5D79:2619 12:02, 4 December 2022 (UTC)
2 questions
Hi
How can I nominate Homayoun (Q5887790) for deletion?
What is the correct instance for Homayoun (Q31070680)? Referring Homayoun, should it be an instance of a name?
Cheers Shkuru Afshar (talk) 03:40, 26 November 2022 (UTC)
- @Shkuru Afshar: You may nominate items for deletion at Wikidata:Requests for deletions. To discuss the content of items, please go to Wikidata:Project chat. -Mohammed Sadat (WMDE) (talk) 09:22, 5 December 2022 (UTC)
This ID is coming from VIAF, but apparently they changed their numbering system, so the link doesn't work anymore. For example at d:Capitaland: https://www.wikidata.org/wiki/Q3272868 the VIAF says the NLB number is 18559528 https://viaf.org/processed/NLB%7C18559528 but it's generating an error message because it's all numbers now. However, in VIAF there is a link to CapitaLand at HistorySG: Capitaland is formed ‡u http://eresources.nlb.gov.sg/history/events/174a8972-8331-4aa2-ba25-2a5001da890d I don't know how to fix this, and would appreciate any help, thanks! Funandtrvl (talk) 05:41, 4 December 2022 (UTC)
- @Funandtrvl: They did mention that they'd be launching new services in December. The community can resolve the URL formatting within the property itself, so please keep an eye on the talk page for updates. - Mohammed Sadat (WMDE) (talk) 12:29, 12 December 2022 (UTC)
- @Mohammed Sadat (WMDE) thank you! Funandtrvl (talk) 19:57, 12 December 2022 (UTC)
Wikidata blocks my access
Wikidata has logged me out and now won't let me log in with my account. It tells me the following: "There seems to be a problem with your login session; this action has been canceled as a precaution against session hijacking. Please resubmit the form.". Could you help me? Thanks. Ps. I have created this account for the report. Questapasando (talk) 12:33, 13 December 2022 (UTC)
- @Questapasando: Might be this issue - https://phabricator.wikimedia.org/T325056 - which seems to be resolved in the last few minutes. Are you still having issues? --Tagishsimon (talk) 12:36, 13 December 2022 (UTC)
- Yes, it seems that it already lets me log in. Ugh, my alarms went off. Ps. What do I do with this account? --Questapasando (talk) 12:40, 13 December 2022 (UTC)
- @Questapasando: It's not a problem to have two accounts for legitimate purposes. Optionally, note on your user page that a second account exists & identify it. Don't use it until the next odd outage. --Tagishsimon (talk) 14:20, 13 December 2022 (UTC)
Central login and Wikidata
I’m wondering if anyone in the know knows how Wikidata is doing its central login differently. I’m asking because every time my browser crashes (or I have to reboot after a blackout, etc.) Wikidata (aside from Phabricator) seems to be the only Wikimedia site that needs me to do a separate login.
I had a blackout today and I checked. I logged into one Wikipedia, then went to Meta (domain wikimedia .org), which told me to reload (i.e., central login was successful). I went to the Scrubunto docs on mediawiki .org, and I was logged in. But when I went to Wikidata I was not logged in.
Given these sites all have different domains, Wikidata must be doing something differently that prevented central login from working (on some browsers). I know to be careful these days, but I’m just wondering if anyone knows the root cause of this. Thanks. — Al12si (talk) 23:11, 13 December 2022 (UTC)
Request terminates with SIGILL
The following request was previously terminating with a server-side SIGILL and a blank screen:
SELECT (wd:Q21715205 as ?entity) ?label ?altLabel ?description ?type ?startDate ?coord ?location ?administrative ?country ?endDate ?hashtag ?website ?organizer ?participatingTeam ?participant ?winner ?speaker ?guestOfHonor ?openedBy ?partOf ?follows ?followedBy ?sport ?applies_to_jurisdiction ?dayInYear ?typeLabel ?locationLabel ?administrativeLabel ?organizerLabel ?participatingTeamLabel ?participantLabel ?winnerLabel ?speakerLabel ?followsLabel ?followedByLabel ?sportLabel WHERE {
?entity (rdfs:label|wdt:P2561) ?label. FILTER(lang(?label) = "en"||lang(?label) = "de"||lang(?label) = "es"||lang(?label) = "fr"||lang(?label) = "nl")
OPTIONAL { ?entity (skos:altLabel|wdt:P1449|wdt:P742) ?altLabel. FILTER(lang(?altLabel) = "en"||lang(?altLabel) = "de"||lang(?altLabel) = "es"||lang(?altLabel) = "fr"||lang(?altLabel) = "nl")}
OPTIONAL { ?entity schema:description ?description. FILTER(lang(?description) = "en"||lang(?description) = "de"||lang(?description) = "es"||lang(?description) = "fr"||lang(?description) = "nl")}
OPTIONAL { ?entity wdt:P31 ?type. }
OPTIONAL { ?entity (wdt:P580|wdt:P585|wdt:P619|wdt:P577) ?startDate. }
OPTIONAL { ?entity wdt:P625 ?coord. }
OPTIONAL { ?entity (wdt:P276|wdt:P1427|wdt:P1444) ?location. }
OPTIONAL { ?entity wdt:P131 ?administrative. }
OPTIONAL { ?entity wdt:P17 ?country. }
OPTIONAL { ?entity wdt:P582 ?endDate. }
OPTIONAL { ?entity wdt:P2572 ?hashtag. }
OPTIONAL { ?entity wdt:P856 ?website. }
OPTIONAL { ?entity (wdt:P664) ?organizer. }
OPTIONAL { ?entity wdt:P1923 ?participatingTeam. }
OPTIONAL { ?entity wdt:P710 ?participant. }
OPTIONAL { ?entity (wdt:P991|wdt:P13469|wdt:P1346) ?winner. }
OPTIONAL { ?entity wdt:P823 ?speaker. }
OPTIONAL { ?entity wdt:P967 ?guestOfHonor. }
OPTIONAL { ?entity wdt:P542 ?openedBy. }
OPTIONAL { ?entity wdt:P361 ?partOf. }
OPTIONAL { ?entity wdt:P155 ?follows. }
OPTIONAL { ?entity wdt:P156 ?followedBy. }
OPTIONAL { ?entity wdt:P641 ?sport. }
OPTIONAL { ?entity wdt:P1001 ?applies_to_jurisdiction. }
OPTIONAL { ?entity wdt:P837 ?dayInYear. }
SERVICE wikibase:label { #BabelRainbow
bd:serviceParam wikibase:language "[AUTO_LANGUAGE], en, de, es, fr, nl"
}
}
(Now I'm getting the following error message: Unknown Error: cause=com.bigdata.btree.EvictionError: com.bigdata.rwstore.sector.MemoryManagerOutOfMemory, state=HTreeHashJoinUtility{open=true,joinType=Optional,joinVars=[entity],outputDistinctJVs=true,size=1450370,considered(left=0,right=0,joins=0),joinSetSize=0}
My first suspicion was that someone vandalized one of the participant's labels since I got a successful query by removing the line querying for `wdt:P710` - but I also got results when I remove everything but that line. 78.142.140.66 15:54, 14 December 2022 (UTC)
- MemoryManagerOutOfMemory sounds much like the query being simply too big. I don’t know where you use the query results, but I suggest you to split it up if you can. —Tacsipacsi (talk) 09:13, 16 December 2022 (UTC)
- There are two main things wrong with this query: 1. setting (wd:Q21715205 as ?entity) in the SELECT does not constrain ?entity in the query to wd:Q21715205; so the query will try to find the OPTIONALS for all items whch meet the mandatory clauses - e.g. that they have a label. Which is to say, everything. That can be fixed by using a VALUES statement in the body of the query - VALUES ?entity {wd:Q21715205} . 2. The query will now return the Cartesian product of all of the variables - 120960 results - which is more than the label service has time to find labels for within the 60s runtime window. Removing the label service call will at least return the values, as below. But an entirely different style of report is required if you want a simple one row per property statement. An approach to this is shown in the second query, below, which fetches all BestRank property statements & their values. If you want to add some specific other values as additional rows - such as rdfs:label values, do so by adding more clauses within a UNION, as per the this query below.
SELECT (wd:Q21715205 as ?entity) ?label ?altLabel ?description ?type ?startDate ?coord ?location ?administrative ?country ?endDate ?hashtag ?website ?organizer ?participatingTeam ?participant ?winner ?speaker ?guestOfHonor ?openedBy ?partOf ?follows ?followedBy ?sport ?applies_to_jurisdiction ?dayInYear ?typeLabel ?locationLabel ?administrativeLabel ?organizerLabel ?participatingTeamLabel ?participantLabel ?winnerLabel ?speakerLabel ?followsLabel ?followedByLabel ?sportLabel WHERE
{
VALUES ?entity {wd:Q21715205}
?entity (rdfs:label|wdt:P2561) ?label. FILTER(lang(?label) = "en"||lang(?label) = "de"||lang(?label) = "es"||lang(?label) = "fr"||lang(?label) = "nl")
OPTIONAL { ?entity (skos:altLabel|wdt:P1449|wdt:P742) ?altLabel. FILTER(lang(?altLabel) = "en"||lang(?altLabel) = "de"||lang(?altLabel) = "es"||lang(?altLabel) = "fr"||lang(?altLabel) = "nl")}
OPTIONAL { ?entity schema:description ?description. FILTER(lang(?description) = "en"||lang(?description) = "de"||lang(?description) = "es"||lang(?description) = "fr"||lang(?description) = "nl")}
OPTIONAL { ?entity wdt:P31 ?type. }
OPTIONAL { ?entity (wdt:P580|wdt:P585|wdt:P619|wdt:P577) ?startDate. }
OPTIONAL { ?entity wdt:P625 ?coord. }
OPTIONAL { ?entity (wdt:P276|wdt:P1427|wdt:P1444) ?location. }
OPTIONAL { ?entity wdt:P131 ?administrative. }
OPTIONAL { ?entity wdt:P17 ?country. }
OPTIONAL { ?entity wdt:P582 ?endDate. }
OPTIONAL { ?entity wdt:P2572 ?hashtag. }
OPTIONAL { ?entity wdt:P856 ?website. }
OPTIONAL { ?entity (wdt:P664) ?organizer. }
OPTIONAL { ?entity wdt:P1923 ?participatingTeam. }
OPTIONAL { ?entity wdt:P710 ?participant. }
OPTIONAL { ?entity (wdt:P991|wdt:P13469|wdt:P1346) ?winner. }
OPTIONAL { ?entity wdt:P823 ?speaker. }
OPTIONAL { ?entity wdt:P967 ?guestOfHonor. }
OPTIONAL { ?entity wdt:P542 ?openedBy. }
OPTIONAL { ?entity wdt:P361 ?partOf. }
OPTIONAL { ?entity wdt:P155 ?follows. }
OPTIONAL { ?entity wdt:P156 ?followedBy. }
OPTIONAL { ?entity wdt:P641 ?sport. }
OPTIONAL { ?entity wdt:P1001 ?applies_to_jurisdiction. }
OPTIONAL { ?entity wdt:P837 ?dayInYear. }
}
- Try it!
SELECT ?entity ?propertyLabel ?value ?valueLabel WHERE { VALUES ?entity {wd:Q21715205} ?entity ?predicate ?value. ?property wikibase:directClaim ?predicate. SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". } }
- --Tagishsimon (talk) 12:25, 16 December 2022 (UTC)Try it!
SELECT ?entity ?propertyLabel ?value ?valueLabel WHERE { VALUES ?entity {wd:Q21715205} {?entity ?predicate ?value. ?property wikibase:directClaim ?predicate. } UNION { ?entity rdfs:label ?value . filter(lang(?value)="en") BIND("rdfs:label" as ?propertyLabel) } SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". } }
Río Trinity/Río Trinidad
the Spanish Wikipedia has 2 articles es:Río Trinity (Q1969490) and now a new one, es:Río Trinidad (Q22395603). I tried to conect correctly but it doesn't work. Can any one take a look to the problem?. Thanks in advance, Juan Villalobos (talk) 13:18, 17 December 2022 (UTC)
- @Juan Villalobos: One of the ES links is a redirect, as far as I can see. There's now a working sitelink on the US river item - Trinity River (Q1969490) - and no ES sitelink on the Chilean river Trinidad river (Q22395603). --Tagishsimon (talk) 16:12, 17 December 2022 (UTC)
- OK, There was "Rio Trinidad" instead of "Río Trinidad". Now is all right. --Juan Villalobos (talk) 17:01, 17 December 2022 (UTC)
Show multiple merge conflicts when merging
Is it possible to show all the errors when trying to merge an item. I usually have a problem merging an item because there are different descriptions in the same language. But the merge tool only shows me one conflict at a time. And it also only shows me the code for the language (fr for french and so on). So I have to figure out what the name of the language is, delete the description, try to merge and find the next language that has a conflict. My suggestion is to show all the conflicts in a row (with the name of the language, not only the code). Steinninn (talk) 05:58, 12 December 2022 (UTC)
- @Steinninn: How are you performing the merge: are you using MediaWiki:Gadget-Merge.js, Special:MergeItems or something else? - Mohammed Sadat (WMDE) (talk) 13:15, 12 December 2022 (UTC)
- Im using Special:MergeItems --Steinninn (talk) 21:01, 12 December 2022 (UTC)
- @Mohammed Sadat (WMDE): What do you suggest I use? --Steinninn (talk) 09:01, 22 December 2022 (UTC)
- @Steinninn: Apologies for the delay in responding, as a portion of our development team is currently on vacation. Currently, it is not possible to display multiple merge conflicts simultaneously using the Special:MergeItems tool. In order to enable this functionality, it will be necessary to implement it within the tool itself. Additionally, we will need to ensure that the full name of the language is displayed as part of this feature. As for the merge gadget, it is a community-developed tool and we hope that it can be improved in the future. However, we will first need to make the necessary API improvements on our end in order to facilitate this. I've created a ticket to track this issue and we will consider it in the future. Thank you for bringing it to our attention. -Mohammed Sadat (WMDE) (talk) 10:53, 22 December 2022 (UTC)
- Thank you! Sounds great. I understand that new features take time. --Steinninn (talk) 15:45, 22 December 2022 (UTC)
- @Steinninn: Apologies for the delay in responding, as a portion of our development team is currently on vacation. Currently, it is not possible to display multiple merge conflicts simultaneously using the Special:MergeItems tool. In order to enable this functionality, it will be necessary to implement it within the tool itself. Additionally, we will need to ensure that the full name of the language is displayed as part of this feature. As for the merge gadget, it is a community-developed tool and we hope that it can be improved in the future. However, we will first need to make the necessary API improvements on our end in order to facilitate this. I've created a ticket to track this issue and we will consider it in the future. Thank you for bringing it to our attention. -Mohammed Sadat (WMDE) (talk) 10:53, 22 December 2022 (UTC)
- @Mohammed Sadat (WMDE): What do you suggest I use? --Steinninn (talk) 09:01, 22 December 2022 (UTC)
- Im using Special:MergeItems --Steinninn (talk) 21:01, 12 December 2022 (UTC)