after having successfully exported my email archive of the last five years (with some 13000 emails) into EagleFiler, I have developed a taste for using it for other things as well.
One that springs to mind is organising the masses of pdf files (mostly academic journal articles) that I have so far largely sitting in a folder in ~/Documents. Organising them with EF would have the advantages of quick preview, the ability to tag them, and to search through all of them very quickly.
However, there is one snag: I have created links to many of this files from my EndNote library. Obviously, as this involved a lot of work, I would like to maintain the links. So I thought I would rename the original folder, create an EF library, and then create an alias of that library’s “Files” folder (which contains the pdfs), and place it under the original folders name in its original place.
However, although accessing that alias in the Finder opens a view to all pdf files, it does not work from EndNote (simply changing the information per record in EndNote through search and replace, by the way, does not work either, which is why this attempt at a workaround was necessary in the first place).
Also, when I use Terminal to “cd” from ~/Documents into the aliased directory, I get an error message stating that it “is not a directory”. OK, it’s an alias, but shouldn’t that be of no concern to the operating system? I thought that this is exactly what aliases are for…
Sorry if this has been overly long, but perhaps someone can think of a solution here. I would hate to have to relink hundreds of pdf files to their EndNote records, which would have to be done manually, as I know of no way to automatize that. (I’m using EndNote X).
Many thanks for any help and thoughts in advance,