Store columns per library file

[ThiloteE]

Some users want to have different columns per library, not per whole JabRef application. See https://discourse.jabref.org/t/von-datei-reiter-in-einzeldatei-n-zerlegt/5254/7.

If we were to go that route we would have to decide between different solutions:

• A) Store columns in library file.
• B) Store columns in dedicated directory/file containing the config (as it is done in JabRef 5.15) and everytime a new library is a opened in JabRef, add a new config to that list (which is not done in 5.15).

I am not sure, if A or B is better, but I could imagine A is. That way, users can share their preferences with multiple machines, but care has to be taken to separate it from preferences of other users. Maybe a "user specific" preference in the library file. Reseting that preference to a default is another thing to think about. Lots of possibility for feature creep. Not sure if B wouldn't be better with JabRef online though. Hmm.

Related issues:

• Loses table view configuration #8465
• New concept for list main table #6857

[koppor]

• Pre-condition: jabref-meta storage in bib file should be improved (by switching to embedded JSON) #10371
• This can be done as part of Generic way to store preferences in .bib file / self-contained library settings #8701.