VladimirAlexiev added a subscriber: Ivan_A_Krestinin. VladimirAlexiev added a comment.
(Yes, we mean WMDE.) This is basically a reopen of T189747 <https://phabricator.wikimedia.org/T189747> which was declined because the source is not available. @Ivan_A_Krestinin Can you comment about opening the source? The bot generates the constraint violation pages, eg see https://www.wikidata.org/wiki/Wikidata:Database_reports/Constraint_violations/P2088. - These pages are the best way to work out data quality problems. Eg I'm now working out through https://www.wikidata.org/wiki/Wikidata:Database_reports/Constraint_violations/P2088#%22Single_value%22_violations to remove stale or wrong CrunchBase identifiers - Given T201150 <https://phabricator.wikimedia.org/T201150>, this is currently the ONLY way to find constraint violations - But even when I can get all violations with SPARQL, I'll prefer to work from a generated WD page - The only improvement I'd ask for is to print the labels of WD items in addition to Qnnnn - (Hmm, https://www.wikidata.org/wiki/Wikidata:Requests_for_permissions/Bot/KrBot describes different tasks). https://phabricator.wikimedia.org/T189747#4058205 describes how the bot operates. If WMDE won't take over the operation of KrBot, another option would be to write a WMDE bot to do it. I believe that when violations are fully exposed for querying (T201150 <https://phabricator.wikimedia.org/T201150>), this should be possible to do with SPARQL (or with SQL if they are also available in the underlying RDBMS). TASK DETAIL https://phabricator.wikimedia.org/T290635 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: VladimirAlexiev Cc: Ivan_A_Krestinin, Addshore, Aklapper, VladimirAlexiev, Lydia_Pintscher, So9q, Invadibot, maantietaja, Akuckartz, Nandana, Lahi, Gq86, GoranSMilovanovic, QZanden, LawExplorer, _jensen, rosalieper, Scott_WUaS, Wikidata-bugs, aude, Mbch331
_______________________________________________ Wikidata-bugs mailing list -- [email protected] To unsubscribe send an email to [email protected]
