Yes, you understand this correctly. Be aware though that after syncing between different computers the aliases probably won't work, so moving the file behind BibDesk may lose the link.
Christiaan Op ma 12 okt. 2020 17:52 schreef Jan David Hauck via Bibdesk-users < [email protected]: > Hi everyone, > > I have a follow-up question to this discussion. > Following Christiaan’s explanations about how to best go about moving > files, am I understanding correctly that as long as *either* the relative > file path *or* the file identity is kept intact, BibDesk will correctly > be able to figure out what the string in Bdsk-File-1 points to? > If this is so, does that mean it is possible to have two separate > databases (i.e., .bib files plus folders with files) synced by a cloud > service and the two .bib files continuing to file files correctly in each > local directory? Since the relative paths will be the same? > So let’s say I have a .bib file in a folder X which auto-files pdfs in > subfolders of folder X, and folder X is synced to another computer and I > make sure the BibDesk auto-file settings on that computer are exactly the > same, and I also make sure that I never open both at the same time, will it > be able to correctly keep things in sync? > So that I could add entries to the .bib file with associated files on > either computer? > > Thanks > > Jan > > > > On Oct 9, 2020, at 2:21 AM, Christiaan Hofman <[email protected]> wrote: > > > Are all of the directories on the same volume (dropbox, iCloud, and > database)? > > First make sure Dropbox has not replaced any file behind your back while > the database was open. Probbaly it is best to just freshly (re)open your > database in BibDesk, to make sure the aliases and relative paths are > updated. Then you can move the files (perhaps by moving the containing > folder) to the new location. Then check a bit whether BibDesk still finds > the files, and save the database. After that it is probably safest to close > and reopen the database again. > > If you want to move both the database AND the files together, keeping a > fixed relative path, you can also do the following. Close the database, and > just move both the files and the database (e.g. by moving the containing > folder). Then open the database, check a bit whether BibDesk finds the > files, and save the database. > > What is important is when you move you either keep the file identities > fixed (i.e. make sure you files are movemoved rather than copied, note that > moving between volumes is really a copy operation, and also that Dropbox > has a habit of copying files behind your back). Or you keep the relative > path fixed. And consolidate your changes afterwards by saving and reopening > the database. > > And of course you may have to udate your auto file settings. > > Christiaan > > On 9 Oct 2020, at 09:25, Simon Spiegel <[email protected]> wrote: > > Hi everyone, > > for years I have been relying on a setup where BibDesk would autofill all > my publications to a Dropbox folder; this has worked well, but now my > Dropbox is reaching its capacity limits and I am considering to move > everything to iCloud where I still have much space left. > > Now the question is: Is there an easy and secure way to move the > autofilled files to a new place so that BibDesk will update all paths > correctly? Since we are talking about hundreds of files, it’s not something > which I can do by hand. The alternative would, of course, be to buy more > space for Dropbox. > > Thanks in advance > > > Simon > > > > > _______________________________________________ > Bibdesk-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/bibdesk-users > > > _______________________________________________ > Bibdesk-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/bibdesk-users >
_______________________________________________ Bibdesk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bibdesk-users
