Tobias Diez

Very nice to see this implemented! A few comments from my side: - I wouldn't bother with the migration of search groups. There is going to be friction anyway if...

I still have the opinion we shouldn't bother with the migration at all. Yes, in an ideal world all groups are perfectly migrated. But in reality we have only limited...

I like the idea with the "alarming color + tooltip". In my opinion, that is sufficient. I guess (although we don't have data on this), free search groups are used...

What about writing to a unique temporary file (in the users temporary file folder, with some random name)? Then you don't need to worry about locking etc (since the `move`...

Yeah I understand, that's why I suggested that every write process should have their own temporary file.

@Krzmbrzl you have coding experience, right? This bug is a bit hard to fix for us since non of the core developers can reproduce it. So it would be nice...

Sure, no problem. In case you find bit of time, you find everything that you need to setup the build locally here: https://github.com/JabRef/jabref/wiki/Guidelines-for-setting-up-a-local-workspace

I think this issue is a direct consequence of #5257. The user saves the library, which changes the file, which leads JabRef to check for changes. Normally, there are none...

Hopefully, this should be fixed in the latest development version. Could you please check the build from http://builds.jabref.org/master/. Thanks! Please remember to make a backup of your library before trying-out...

@ChristopherHackett Thank you for having a look at the worldcat fetcher. I created a sandbox wskey for you, which should be enough for playing around with the API. | Name...