> On 21 Sep 2018, at 20:15, Br. Samuel Springuel <rpspring...@gmail.com> wrote: > > On 9/21/18 2:01 PM, Christiaan Hofman wrote: >> If you want to use crossrefs just to copy fields, than I would not do that, >> it's not the purpose of crossref support. That was added to help with >> crossrefs in bibtex. > > I'm more interested in using it to save me from having to edit/reenter > information multiple times when dealing with several references from the same > physical source. That is, as I understand it, the whole point of crossrefs. > >> Using crossrefs can have negative consequences. > > I've not heard that before. Can you elaborate?
Crossrefs do add some overhead, because links have to be followed to resolve field values. And the editing involving crossers adds overhead and vulnerabilities. Also, editing field group names that involve items with crossrefs gives overhead and is a bit more cumbersome. Also, if you use bibtex, what BibDesk shows is not necessarily the same as what bibtex will reproduce. > >> Also, fields in different types can differ. This may be in particular true >> for book and incollection, where booktitle really should correspond to title >> in the other type. > > I already have the Duplicate "Title" to "Booktitle" option active for dealing > with this. > >> Having said that, you can always add crossrefs to items, and delete fields >> you want to have filled by the mechanism. > > That works. Thank you. Also note that there are a few shortcuts to handle crossers, like using the selected item as crossers when holding the Option key when creating a new item. > >> You may also partly automate this using Applescript. > > Are you referring to an existing Applescript somewhere, or saying that I > could write my own? I don’t know of any existing Applescripts, so you’d need to write that yourself. Christiaan
_______________________________________________ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
