We should update the constraint table, so when we announce the new constraint API and a gadget for the item page users are not confronted with very outdated data.
Instructions:
php maintenance/runScript.php extensions/Constraints/maintenance/UpdateConstraintsTable.php --csv-file <path_to_csv_file>
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Lydia_Pintscher | T160505 [Story] Keep constraint table in sync with constraint definitions of properties | |||
| Resolved | hoo | T160506 Update constraint table |
Mentioned in SAL (#wikimedia-operations) [2017-03-30T12:15:58Z] <hoo> Updated the Constraints table on Wikidata, per T160506.
Done:
hoo@terbium:~/constraint-data$ mwscript extensions/Wikidata/extensions/Constraints/maintenance/UpdateConstraintsTable.php --wiki wikidatawiki --csv-file constraints-wikidatawiki.2017-03-30.csv 11884 rows inserted
Since the API and user script announcement, several constraints have been fixed, such as this one which used to report two violations on every date of birth in Wikidata. Can we do another reload? We should also announce it to the community so that they know they should get in any necessary changes before the date in question (say, next Wednesday, 2017-05-10).
It's rather straight-forward to do this again, just tell me when it's needed and I'll take care of it.
I would prefer Thursday, May 11th. I'll announce it to the community (asking them to do some changes before if they want to) tomorrow and I'd like to let them one full week. I hope it's fine for you all :)
Should the completed update be announced? Looks like the original announcement was already archived.
Great, then I think we can close this again. Thanks @aude for the update and @Lea_Lacroix_WMDE for the announcement :)