Main PDF Directory: and Main PS directory: preference settings removed. Needed for heterogeneous repositories.

[ajbelle]

As part of checking "issue Attached File Delete functionality #245" I note the Options>Preferences>[External programs] Legacy file fields --------------- are no longer showning, nor do they appear in File>Database Properties. Settings for my repositories have carried across from my ver2.10 install, BUT WHAT DO I DO IN FUTURE? If I move the Endnote file repository I have in "Main PDF Directory:" and "Main PS directory:" I can edit the directory directly in "Exported preferences.xml” with PFE and reimport, but is all support going to terminate!
I have used these fields for heterogeneous linking to a large Endnote Database (not the intended purpose), so retention of these additional paths is useful functionality to me. All I found on the internet were changes to the bibtex file PS and PDF entries. Is there an alternative method to link a second file repository? The helpfile of my V.30 install is not getting past the second page and https://fossies.org/linux/misc/JabRef-3.0.jar/help/en/ExternalFiles.html is the old information.
This maybe should be a forum post.

[lenhard]

Yes, all support for these things is terminated. You can put multiple file links into the file field of a bibtex entry. You just need to separate the path via a semicolon.

[ajbelle]

Thanks lenhard:-( I am not referring to having multiple files linked in the file field, I was asking after the additional paths to directory locations other than set in options>Preferences>External programs"Main file Directory" that the "Main PDF Directory:" and "Main PS directory:" settings allowed (VERY HANDY EVEN THOUGH NOT THEIR INTENDED PURPOSE).
Can you please contirm your reply means that I have to apply the full file specification from the root for the thousand+ files I have in my separate Endnote directory (outside the "Main file Directory") . Am I missing something?

[matthiasgeiger]

I'm not sure whether I understand your use case correctly... You have used the "legacy fields" pdf / ps to define file links which are based outside your set "main file directory"?

So your entries have both: a file field AND a pdf/ps field pointing relatively to different files (in different folders)?

If so, then you cannot retain this behavior with JabRef 3.0+.

Or do you have only the pdf/ps field but no additional file link? So what you basically want is to define database specific "main directories" which are used for relative linking?

If so, you should use the functionality to define a database specific main directory. Accessible via right-click on the database title tab -> "Database properties".

[simonharrer]

Maybe paste a small excerpt of your bib file here, as this may clarify things.

[koppor]

@ajbelle bump

[ajbelle]

Sorry for delayed reply gentlemen.
@matthiasgeiger Thanks for your hint ---> Accessible via right-click on the database title tab -> "Database properties". It is the closest to my case, however I can only get JabRef to access the files in a single base directory I enter here rather than across multiple base file directories (folders on my Win7 hard drive) simultaneously. If I complete both fields JabRef only accesses the User Specific file directory:!
I insert the .bib file fields (@simonharrer) so you can see that there are only single relative file links against each BibTeX entry. I don't have multiple files for each entry for this test file.

from the .bib file :
Entry calling from base directory E:\JabRef_library
File = {:°paper\°CFD\°LES\leveque2007A- Shear improved Smagorinsky model.pdf:PDF},
--- From totally BibTeX separate entry below -------------
Entry calling from base directory E:\CRC Share\endnote\Data\PDF
File = {://7276-2854935553/7276.pdf:PDF},

As set up for test .bib by RMB on the database title tab -> "Database properties"
from the .bib file:
@comment{jabref-meta: fileDirectory:E:\JabRef_library;}
@comment{jabref-meta: fileDirectory-abelle-LTN-AMC-18QL102:E:\CRC Share\endnote\Data\PDF;}

This does not replicate the behaviour that JabRef provides with the legacy fields (that are still present in my preferences as set through legacy fields by an older JabRef version)
from exported JabRef_Preferences.xml file:

The above preferences make JabRef search both the default and the legacy base directory locations for file links that within the BibTeX file provide no indication of their different directory locations. This is what I meant by a heterogeneous file structure. The current JabRef version seems to expect a single base directory location for all pdf files.

I could provide a directory link/mount (within the Windows file system) to the second ‘base directory’ so that JabRef did not have to search both paths (The second one containing the imported Endnote pdfs.). I don’t know how to, but this is the simple and singular capability that my ‘misuse’ of the legacy directory fields provided.

Once again, sorry if I am missing something.

[koppor]

The pdf field is used by some people to have notes on the paper in a different file and to have two columns in the entry table: one for the notes and one for the PDF. See message by Guido Milanese for details: https://sourceforge.net/p/jabref/mailman/message/34736202/

[ajbelle]

@koppor I can see others would use this, but it is completely the reverse requirement I have identified, which is a single relative file reference within by 'jabref'.bib file entry that is searched for by JabRef in two root directories without having to provide the complete file spec for the second repository root directory. THIS IS A VERY USEFUL CAPABILITY THAT SEEMS LOST in the current JabRef revision, and presumably could be resurrected as a new JabRef 'feature' if in the background as the "Legacy pdf directory" being rebadged the "Alternative repository root directory". I believe it is just an alternative search path added to the file search specification. Because my configuration file already has the "Legacy pdf directory" included it still works for me at the moment, but not if the JabRef ‘back end’ terminates what the ‘front end’ already has.
The ability @koppor mentions no longer is available, because it is ‘front end’ program changes that were implemented in the revision. There are probably other users that are unaware they have the issue I have raised because their files in their files in legacy locations are still found while the ‘back end’ is left alone.

[tobiasdiez]

So if I understand you correctly, you want to specify more then one folder in Database Properties -> General (or user specific) file directory, right?
Moreover, if both the general and the user specific path are specified, then also both paths should be searched (currently only the user specific folder is taken into account).