On Jun 3, 2010, at 18:06, Colin Henein wrote: > I moved my bibdesk database to a new mac several years ago. Since > then, the links to the many PDF files I had in the filesystem have > been cross-linked to random other files, many of them folders under > /System > > I figure this has occurred because the Mac OS file numbers are still > being honoured, even though I am on a different filesystem. BibDesk is > happy and I have no "red paperclips" because all the links are "good", > but they are to the wrong files. > > I can think of the following ways forward, the trouble is BibDesk > doesn't seem to offer me any of these options: > > 1. cause BibDesk to forget all its HFS aliases, and fall back on the > relative path method. >
BibDesk tries the relative path first. Therefore when you move a database to another computer you should always move the papers and the database together so the relative path remains the same, that is by far the most reliable way. The file number is checked only as a last resort AFAIK. I find it strange it's linking to arbitrary files or folders, but we have not much control over how aliases are resolved except for the search order. > 2. cause BibDesk to forget all the files it has linked, and then: > a. reverse the AutoFile process to re-link the appropriate files > (all my PDFs are named exactly the way AutoFile would make them) This can be done using AppleScript. There have been several threads on this list about that. > b. use the Orphaned Files somehow to bind them up (orphaned files > doesn't work for me, perhaps because I have subdirectories under > my paper directory?) > Orphaned files are searched recursively in subdirectories. > It is frustrating to put work into organizing these files in a > database, and then not be able to use them. Does anyone have any > suggestions as to how to proceed? I don't have huge numbers of > references and papers, but doing it manually seems to be a task that I > never really have time for. > > Regards, > Colin > Do you still have the old setup? Perhaps you can copy the database again. Make sure next time you do it to move the whole database as a whole and make sure you re-save the .bib file afterwards to update the links. Christiaan ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Bibdesk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bibdesk-users
