You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
JabRef should support a database (MySQL, Postgres, Oracle, ...) as backend. As far as I understand the current implementation, the DB export simply overwrites all data. This is a show stopper for collaborative work.
JabRef should support collaborative work where a database (MySQL, Postgres, or Oracle) is shared between multiple users. If an entry is added (or even changed) to the DB, all other users should see it.
If there are concurrent edits, the user should be warned and the window "Merge duplicate entries" should be shown. With the event system (#969), this might be obsolete as JabRef will instantly synchronize the changes.
The implementation heavily depends on the event system of JabRef (#969).
As soon as the feature is implemented, it should also be possible to import a bib into the database and export the database to a bib. This should work with the current functionality, but we have to add documentation and a test case.
Background: For many users, local installation of desktop software is OK. They are not on the everything-in-the-web-train.
JabRef should support a database (MySQL, Postgres, Oracle, ...) as backend. As far as I understand the current implementation, the DB export simply overwrites all data. This is a show stopper for collaborative work.
JabRef should support collaborative work where a database (MySQL, Postgres, or Oracle) is shared between multiple users. If an entry is added (or even changed) to the DB, all other users should see it.
If there are concurrent edits, the user should be warned and the window "Merge duplicate entries" should be shown. With the event system (#969), this might be obsolete as JabRef will instantly synchronize the changes.
The implementation heavily depends on the event system of JabRef (#969).
As soon as the feature is implemented, it should also be possible to import a bib into the database and export the database to a bib. This should work with the current functionality, but we have to add documentation and a test case.
Background: For many users, local installation of desktop software is OK. They are not on the everything-in-the-web-train.
Dropped wishes:
This is (currently) too much work for too little gain.
Implementation hints:
Decision: Only implement it for Oracle and Postgres.
The text was updated successfully, but these errors were encountered: