Thanks, Nathan! See below for quick responses.
Cheers, Matt > On Nov 29, 2020, at 3:55 PM, nathan.art...@softhome.net wrote: > > Matthew Heun via Bibdesk-users writes: >> it says that "A document must always produce the same URL even if the >> document is moved renamed or edited." The script below will not meet that >> requirement if the cite key changes. Should we rather use the DOI of an >> entry as the primary URL, if the DOI is present? (The scheme you suggested >> (using the cite key) could be a backup scheme when no DOI is present.) > > Based on my experience, I would say that it's the responsibility of the user > to maintain the cite key as a permanent identifier. In other words, the user > shouldn't change the cite key, and it should be fine to use the cite key as a > permanent identifier. If the user changes the cite key, they are going to > have bigger problems than Hook not working: all the LaTeX commands that use > that cite key won't work, any other x-bdsk://citekey URLs you've created > won't work, etc. Just don't change the cite key and you'll be fine. You > should set up a standard cite key format at the start and use it until you > die. That's my experience (though I haven't died yet). OK. You have convinced me đŸ™‚. >> Should the URL returned by this script also encode an identifier for the >> .bib file in which the entry is embedded? It seems like Hook will need to >> know which .bib file to open before finding the entry within that .bib file. > > Christiaan can correct me if I'm wrong, but the way x-bdsk://citekey URLs > work does not need an identifier for the .bib file. I did some testing this evening, and I think you're right. That's awesome! > Nathan > _______________________________________________ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
