Re: [Bibdesk-develop] crossref application rules

[Christiaan H. <cmh...@gm...>]

> On 13 Jan 2023, at 01:20, Emiliano Heyns <emi...@ir...> wrote:
> 
> My bad -- the booktitle should have been inherited, not present in the @incollection entry. <>
> On Fri, 13 Jan 2023 at 00:50, Christiaan Hofman <cmh...@gm... <mailto:cmh...@gm...>> wrote:
> 
> I am not completely clear about the question. For one thing, the item you mentions just has a booktitle field, so the crossref does not seem relevant for it.
> 
> My bad -- the booktitle should have been inherited, not present in the @incollection entry. <>
> 
>  <>
> This is more compact sample:
> 
> @inproceedings{author:06,
>   title = {Some publication title},
>   author = {Author, First and Author, Second},
>   crossref = {conference:06},
>   pages = {330—331}
> }
> @book{conference:06,
>   editor = {Editor, First and Editor, Second},
>   title = {Proceedings of the Xth Conference on XYZ},
>   booktitle = {Proceedings of the Xth Conference on XYZ (Book)},
>   year = {2006},
>   month = {oct}
> }
> 
>  <>
>  
> Are you talking about the tex preview?
> 
> I'm not sure -- when I click an item in bibdesk, there's a preview below the list, is that what you mean? If so, then yes -- that preview of author:06 shows a booktitle, and if I double-click author:06, it shows the booktitle in grey, with an arrow to open the parent item. Somewhere bibdesk must know what fields are candidate for inheritance, and what they are mapped to. 

We just fill in the missing fields from the crossref item, whenever there is a crossref field. As for which fields we display, it is all required, optional, and default fields (as well as other fields that are set in the item itself). Required and optional fields depend on the type (set in the advanced Field preferences), and the default fields are the ones flagged as default in the table in the Field preferences. So in your example, the booktitle is shown as an inherited field because it is a required field for inproceedings.

Christiaan