As a Wikidata patroller I want statement edits made with REST API to have an "automated summary" provided so that I can have a quick overview on what the edit has been about.
As a Wikidata patroller I want statement edits made with REST API to have an "automated summary" provided so that I can consider edits made with the REST API in my regular workflows.
For the time being (July 2022), with no better alternative present, Wikibase REST API will mimic the "automated summaries" of Wikibase's Action API and other logic.
The following "automated summary" templates are suggested to use with edits made with specific REST methods and paths
POST /entities/items/{item_id}/statements | /* wbsetclaim-create:1||1 */ [[Property:P123]]: VALUE_FORMATTED |
PUT /entities/items/{item_id}/statements/{statement_id} PUT /statements/{statement_id} | /* wbsetclaim-update:1||1 */ [[Property:P123]]: VALUE_FORMATTED |
DELETE /entities/items/{item_id}/statements/{statement_id} DELETE /statements/{statement_id} | /* wbremoveclaims-remove:1| */ [[Property:P123]]: VALUE_FORMATTED |
PATCH /entities/items/{item_id}/statements/{statement_id} PATCH /statements/{statement_id} | /* wbsetclaim-update:1||1 */ [[Property:P123]]: VALUE_FORMATTED |
Notes to the above:
- [[Property:P123]] should be replaced by the wiki-specific wikitext representation of the link to the property used in the statement (P123 in the examples)
- VALUE_FORMATTED should be replaced by the wiki-specific wikitext representation of the value of the statement ("main snak")
No "smarter" automated summaries are intended to be provided for the time being.
Note: The MediaWiki framework will automatically truncate comments longer than the allowed limit of characters, so there is no need to change the comment length validation for this story.