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

Add support for biblatex field aliases #521

Closed
koppor opened this issue Dec 15, 2015 · 3 comments · May be fixed by HITOSS/jabref#3, HITOSS/jabref#4 or HITOSS/jabref#5
Closed

Add support for biblatex field aliases #521

koppor opened this issue Dec 15, 2015 · 3 comments · May be fixed by HITOSS/jabref#3, HITOSS/jabref#4 or HITOSS/jabref#5

Comments

@koppor
Copy link
Member

koppor commented Dec 15, 2015

In the biblatex documentation at Section 2.2.5, "Field Aliases" are described.

  • address for location
  • annote for annotation (jurabib)
  • archiveprefix for eprinttype (arXiv)
  • journal for journaltitle
  • key for sortkey
  • pdf for file (JabRef compatibility ☀️)
  • primaryclass for eprintclass (arXiv)
  • school for institution

Issue: When switching from bibtex to biblatex mode, the field "journal" is written as optional field, even though it is a required field.

quick hack

In the serialization of JabRef, aliased fields should be treated like the original fields.

Issue with the quick hack: The aliased field is still treated as optional field or not treated at all. This seems to be inconsistent.

related bug reports

@cbersch
Copy link

cbersch commented Jan 3, 2016

The related bug report on sf isn't relevant, since this was only about the mere possibility to use the journaltitle field at all. It didn't try at all to handle field aliases properly.

@koppor koppor added this to the v3.8 milestone Nov 19, 2016
@koppor
Copy link
Member Author

koppor commented Nov 19, 2016

We have some support in the entry table: #24 and some code has been written for the journaltitle field: #1720 and #15

The entry editor, however, still does not support alias and this causes issues when fetching entries: #2209

@tobiasdiez
Copy link
Member

This is now implemented in the latest development version (at least if I understand it correctly). Could you please check the build from http://builds.jabref.org/master/. Thanks!

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