Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request: ("core") crossef support in saving and exporting (and display) of BibTeX items #542

Open
balanco opened this issue Nov 12, 2021 · 1 comment

Comments

@balanco
Copy link

balanco commented Nov 12, 2021

crossref should be supported in the saving and exporting of BibTeX items (as well as in the display of items including a crossref)

  • if any BibTeX item (or multiple items...) containing a crossref (for example, an @incollection item that crossrefs a @book item) is selected by the user for saving to file, then the crossrefed item(s) (i.e., in the example, the @book) should be offered to be saved as well (there could (should) be a profile option to have this (not) always happen without asking)
  • if a record containing a crossref is selected for export, then care should be taken that all information – i.e., including the information "inherited" via the crossref – is exported (if e.g. by always expanding BibTeX items first (so that all fields defined in the crossrefd "parent" are set explicitly), and then exporting the expanded item). Currently, one ends up with unusable records in the exported format (XML for Windows, say).

Further (but not as crucial) it would be quite helpful if the field values inherited via crossref were shown (in a way that clearly distinguishes them from ("actual") values local to the item.

PS: for those who have access to macOS, see BibDesk for a worked out example (that e.g. also sports the display of the inherited values in the item that crossrefs another).

@koppor
Copy link
Member

koppor commented Nov 14, 2021

@balanco Could you provide a screenshot of BibDesk here? Then the feature request would be even more clearer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants