**Motivation**
For mobile edits, we don't want to create every action atomically. Reasons for this are:
- The number of edits currently created by one save creates rather cluttering watchlists
- It would create a lot of requests, and this would increase needed band width
- It would create "part error states", where some part of an edit is saved, but some other part is not
- The number of edit summaries is rather cluttering (this reason is not mobile specific).
However, editors should still be able to understand as much as possible about an edit without having to look at the diff. Thus we need edit summaries that are as specific as possible, and at the same time not overwhelming.
**As a** Wikidata or a Wikipedia patrolerr (both are affected!)
**I want to** understand what an edit was about just by reading the edit summary
**so that I** identify vandalism right from my watchlist
**Technical thoughts****Acceptance Criteria**
In order to create a[] Provide custom general "ted edit summary creation" pointries, the edit summary should be generated as part of the wbeditentity endpoint.
**Eif only termbox contents was changed, and if no custom edit summary versions**has been provided
**Expanded version** [] As long as 5 or less terms (item, description or alias) were changed, display the expanded version of the edit summary (see definition below)
For each language code [] If more than 5 items were changed, use the shortened version. (see definition below)
Changed: < [] If more than 50 language code> <label/description> to <new label/description>,s received changes, use the fallback version. [this now repeats if both were changed](see definition below)
Changed <language code> aliases: Removed <removed aliases>, added <added aliases>[] If anything outside of the termbox was changed, changed <changeddon't use the new version of aliases>edit summary mechanism
**Shortened version**Technical thoughts**
Changes for <all language codes that changed the same types>: Label, Description, Alias [whichever of these were changed] [whole line repeats for all variations changed of label, description- In order to create a general "edit summary creation" point, alias]
**Fallback version**the edit summary should be generated as part of the wbeditentity endpoint.
In XX languages there were changes- Dealing with change operations was a struggle in either Labelthe lexeme project, Description and/or Alias [whichever of them has been touched anywmaybe we can learn something from there] ?
**Acceptance Criteria**Edit summary versions**
[] As long as the edit summary still contains less than XX Bytes, create the edit summary in the before mentioned ideal**Expanded version.**
[] If the Byte limit cannot be metShow each change seperated by comma, usein the shortened version.following format:
[] If it still cannot be met, use the fallback version.
[] If a custom edit summary is provided, this is the one used
**Open questions:**
- Do we want to have newlines in there?<Added/Changed/Removed> [<language code>] <label/description/alias>: <new label/description contents>,
Example:
- Which pieces`Added [en] label: Frame of the edit summary should be translated?Notre-Dame de Paris, Changed [en] label: Maja, How can we make it translatable?Added [fr] alias: Marie`
The wording is attempted to be as close to the current edit summary formulation as possible
**Shortened version**
- What should be the Byte limit?Changes for <all language codes that changed the same types>: Label, Description, Alias [whichever of these were changed] [whole line repeats for all variations changed of label, description, alias]
- What would actually be the best summary suggestions?Example:
- What should be the edit summary if sth else but`Changes for fr, es, en, pl zh: label, description, alias. Changes for it, alias was changed?hu: label`
**Fallback version**
In XX languages there were changes in either label, description and/or alias [whichever of them has been touched anywhere]