Offer migration stategy from PDF und PS directories

[koppor]

JabRef offers a single file directory with the possibility to have user-specific file directories for shared libraries. (see #459 (comment))

@ajbelle came up at #496 that he still uses the pdfDirectory setting although it is not visible in the UI. We should offer a migration path for users with that setting.

• Understand why users want two user-specific directories (PDF and everything else?)
• convert pdfDirectory and psDirectory setting to something appropriate

[ajbelle]

Thanks @koppor
I posted to #496 my findings that at least on my instal this great (for me) access to multiple unlinked directories is still functional.
My answer to your first question is simple. It makes a move to JabRef (or use of JabReF together with another file manager such as EndNote/Zotero/Docear) very easy in the first instance.
If JabRef developer's wisdom is to close this existing capability, I suggest you recommend the use a 'junction', which made very easy with LinkShellExtension from http://schinagl.priv.at/nt/hardlinkshellext/linkshellextension.html. It makes is as easy as using |Windows Explorer|, so your average user can easily do it.
I often see JabRef turned down in favour of Zotero or Endnote supported and paid for by the university, but if JabReF offered easy joint file access that decision would not be required (All gain-little pain). I presonnally cannot use Docear for my large repository, so retain JabReF as my full file repository manager and give Docear just the files it needs to work with via hardlinks. Jöran Beel (he is great) can't see why everything isn't done in Docear ;-) I have Endnote, JabReF and Docear all accessing the same files from different directories, and think I should really be accessing Zotero for its functionality. JabRef is friendly and easy to use and can handle any sized file repository a single researcher will usually generate, so I stick with it. I hope that answers why and thanks for everything.
I just remembered why I used the Legacy Directory in the first place. Being a complete novice I read Legacy to mean imported from the old bib-manager (Endnote), not legacy PDF and PS fields within JabReF. If required there is no reason the replacement field could be called the same. It is usual a change of file hierarchy and a fresh start is justified.

[mlep]

This issue on JabRef repository is also an issue at stackexchange :
https://tex.stackexchange.com/questions/300963/no-linking-to-pdf-files-since-jabref-3-2-upgrade

[simonharrer]

Maybe something for the stupro? @koppor

[koppor]

We are currently trying to focus on other things. 🔥
We will come back later to this topic, therefore closing adding on-hold label and closing the issue for now.