I claim: If one opens a .bib file with JabRef, save it and close it, the file is not modified

However, JabRef migrates the field review to comment without any user information. This should not happen.

Proposal:

1. In case JabRef wants to do a migration, then it asks for the user (example: pdf field)
2. The answer to the migration choice should be stored in the library

Note on 1: A list of migrations to be performed would be nice. The user can then add and remove migrations on demand.

Links:

• Pre-condition: New format for meta data: jabref-meta storage in bib file should be improved (by switching to embedded JSON) #10371
• This (somehow) contributes to Generic way to store preferences in .bib file / self-contained library settings #8701
• Alternative: Do not migrate review to comment if review is a customized field. Long explanation at Rename the Review Tab into Comments Tab #3658 (comment) (not chosen as I really opt for transparency)
• Other migration WTF example: https://discourse.jabref.org/t/convert-timestamp-to-creationdate-in-5-3/2787?u=koppor