Salgo60 added a comment.
List Contemporary constraint check errors http://tinyurl.com/y8pjk5ux
SELECT DISTINCT ?item ?itemLabel WHERE {
?statement wikibase:hasViolationForConstraint wds:P27-ad2c85a5-49ba-6748-4302-77b44a268ed5 .
?item ?p ?statement .
FILTER( ?item NOT IN ( wd:Q4115189, wd:Q134
Lucas_Werkmeister_WMDE added a comment.
In T141859#4595822, @Lydia_Pintscher wrote:
Is there a place already where I can see it working?
I updated wikidata-constraints as well, but it’s probably easiest to test it on Wikidata with @abian’s example item.TASK DETAILhttps://phabricator.wikimedia.or
Salgo60 added a comment.
Ok ping @Ivan_A_KrestininTASK DETAILhttps://phabricator.wikimedia.org/T141859EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: abian, Salgo60Cc: gerritbot, Salgo60, Jklamo, Ivan_A_Krestinin, PokestarFan, Lucas_Werkmeister_WMDE, Lydia_Pin
abian added a comment.
In T141859#4603658, @Salgo60 wrote:
Wikidata:Database_reports/Constraint_violations/P27 reports
ERROR: Unknown constraint type: Q25796498.
Right, that's a bug in KrBot2. Only its operator has access to the source code, so we sadly can't contribute to it.TASK DETAILhttps:/
Salgo60 added a comment.
Wikidata:Database_reports/Constraint_violations/P27 reports
ERROR: Unknown constraint type: Q25796498.TASK DETAILhttps://phabricator.wikimedia.org/T141859EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: abian, Salgo60Cc: gerritbot, Sal
IP’s are not aloud to fix anything, we are people too.
From: abian
Sent: Thursday, September 20, 2018 8:59 AM
To: wikidata-bugs@lists.wikimedia.org
Subject: [Wikidata-bugs] [Maniphest] [Commented On] T141859:
[Task]Contemporary constraint check
abian added a comment.
Now deployed on
abian added a comment.
Now deployed on Wikidata. You can find a violation on http://www.wikidata.org/entity/Q628365... until someone fixes it.TASK DETAILhttps://phabricator.wikimedia.org/T141859EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: abianCc: gerritbot
abian added a comment.
In T141859#4595822, @Lydia_Pintscher wrote:
Is there a place already where I can see it working?
I see WikibaseQualityConstraints is already updated on https://test.wikidata.org/, but maybe the config variables of the contemporary constraint should still be set. Otherwise,
Lydia_Pintscher added a comment.
Is there a place already where I can see it working?TASK DETAILhttps://phabricator.wikimedia.org/T141859EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: abian, Lydia_PintscherCc: gerritbot, Salgo60, Jklamo, Ivan_A_Krestinin, Pok
gerritbot added a comment.
Change 458522 merged by jenkins-bot:
[mediawiki/extensions/WikibaseQualityConstraints@master] Implement contemporary constraint check
https://gerrit.wikimedia.org/r/458522TASK DETAILhttps://phabricator.wikimedia.org/T141859EMAIL PREFERENCEShttps://phabricator.wikimedia.o
gerritbot added a comment.
Change 458522 had a related patch set uploaded (by Abián; owner: Abián):
[mediawiki/extensions/WikibaseQualityConstraints@master] Implement contemporary constraint check
https://gerrit.wikimedia.org/r/458522TASK DETAILhttps://phabricator.wikimedia.org/T141859EMAIL PREFER
abian added a comment.
Update: I have finished formalizing this constraint as a part of my final degree project, and I will start implementing it at some point in the coming weeks so that this can be finished around May. I will keep you informed. :-)TASK DETAILhttps://phabricator.wikimedia.org/T141
abian added a comment.
Do we actually have an efficient way to find subproperties of a property without using the query service?
No idea. But couldn't we retrieve those subproperties asynchronously, from time to time? They aren't expected to change very often.TASK DETAILhttps://phabricator.wikimed
Lucas_Werkmeister_WMDE added a comment.
Okay, those are some good points :) I’m still skeptical about one thing:
An algorithm that gives us the same outputs as another in almost the same time
Do we actually have an efficient way to find subproperties of a property without using the query service?
abian added a comment.
In T141859#3549363, @Lucas_Werkmeister_WMDE wrote:
(Aside: that first query should probably include “work period (start)”. It seems to be missing a P279 statement.)
I’m not convinced that this is the best approach. Do we really need all the properties for every constraint?
Lucas_Werkmeister_WMDE added a comment.
(Aside: that first query should probably include “work period (start)”. It seems to be lacking a P279 statement.)
I’m not convinced that this is the best approach. Do we really need all the properties for every constraint? I feel like it might make more sen
Ivan_A_Krestinin added a comment.
All other constraints store settings as qualifiers on property page. I think it is good practice make all constraints as similar as possible. This makes implementation and understanding of full constraints system easier.TASK DETAILhttps://phabricator.wikimedia.org/
abian added a comment.
This task was added to #Need-volunteer. Could I help with it in some way?TASK DETAILhttps://phabricator.wikimedia.org/T141859EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: abianCc: Lydia_Pintscher, Wikibase-Quality-Constraints, abian, A
abian added a comment.
Example of query that detects Constraint:Contemporary violations:
SELECT ?subject ?value
WHERE {
?subject wdt:P${THEPROPERTY} ?value .
OPTIONAL { ?subject p:P569/psv:P569 [ wikibase:timeValue ?subject_birth ; wikibase:timePrecision "11"^^xsd:integer ] . }
OPTIONAL { ?v
19 matches
Mail list logo
