API gloss update "non-updated fields"

[susanodd]

          @rem0g One more thing relevant to this issue:

We noticed that you send all the fields in the request to update the gloss. However this gives a lot of non-informative changes in the revision history (see https://signbank.cls.ru.nl/dictionary/gloss/49249/history)

We clearly did not document this well ;) However the intention for this api was to only include the fields that are changed so it only updates those and leaves the others as is and they are not added to the revision history. Just so you know! You can close this issue again when read.

Originally posted by @Jetske in https://github.com/Signbank/Global-signbank/issues/1360#issuecomment-2454853764

[susanodd]

DISCUSSION @Woseseltops read here

I made a separate issue for this, since it's not a bug, but a usage concern.

• For the Signbank Gloss Detail Edit View and the Batch Edit, each of the updates in the Phonology panel, etc. is done by a separate AJAX call. So the updates themselves are very small, one field at a time. This was to limit database locking.

• But for the API update gloss, this has been communicated poorly in the documentation / Swagger pages.

• By including a "giant json dictionary" of updates, which in practice is being used with the majority of the fields empty.

• Signbank is forced to calculate all the "changed fields".

• This is API server overload compared to the Gloss Edit and Batch Edit interfaces.

• The gloss update API is causing the database to get locked because of this.