Migrate library fields after confirmation. Store selected migration preference inside library

[koppor]

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: https://github.com/JabRef/jabref/issues/10371
• This (somehow) contributes to https://github.com/JabRef/jabref/issues/8701
• Alternative: Do not migrate review to comment if review is a customized field. Long explanation at https://github.com/JabRef/jabref/pull/3658#issuecomment-1707756535 (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

[koppor]

As far as I remember, the decision to automatically migrate review was done, because our check in 2015 revealed that review was a custom JabRef field and not used by any other software. We also wanted to streamline the code and support only the latest release version of JabRef.

[koppor]

Code:

https://github.com/JabRef/jabref/blob/c444c739d62737003fd1c178d3aeefb628fe78b1/src/main/java/org/jabref/gui/importer/actions/OpenDatabaseAction.java#L55

and

https://github.com/JabRef/jabref/blob/c444c739d62737003fd1c178d3aeefb628fe78b1/src/main/java/org/jabref/logic/importer/OpenDatabase.java#L33

[koppor]

Implementation hints were given at https://github.com/JabRef/jabref/pull/3658#discussion_r168779345. Follow-up at https://github.com/JabRef/jabref/pull/3733.

[koppor]

Code merging the fields at org.jabref.migrations.MergeReviewIntoCommentMigration.