#29 — Editor field not handled correctly in bibtex import/export

by Bernd Rellermeyer — last modified Dec 19, 2009 05:19 PM

State	Unconfirmed
Version:	0.9.0
Area	Functionality
Issue type	Feature
Severity	Low
Submitted by	Bernd Rellermeyer
Submitted on	May 12, 2007
Responsible	—
Target release:	—

Return to tracker

Tags:

1. Some bibtex entries, like incollection, may have an author and an editor field. The editor field, althoug in bibtex formatted like the author field, i. e. several editors separated with 'and' are possible, is then mapped into a single line.

2. Other bibtex entries, like the book entry, may also have an author and an editor field. If both are filled, the editor field is lost.

I think, in those cases the editor field must be handled like the author field, i. e. mapped always into a list of editors. Both authors and editors should be possible in the same entry.

Note: When applying the crossref-patch, the editor field result is a list.

Steps to reproduce:: 1. Import the following entry:

@InCollection{_boeckenfoerde87:_zusammenbruch_der_monarchie,
  author = {Ernst-Wolfgang B{\"o}ckenf{\"o}rde},
  title = {Der Zusammenbruch der Monarchie und die Entstehung
                  der Weimarer Republik},
  booktitle = {Die Weimarer Republik 1918--1933},
  crossref = {bracher87:_weimarer_republik},
  pages = {17--43},
  editor = {Karl Dietrich Bracher and Manfred Funke and
                  Hans-Adolf Jacobsen},
  publisher = {Bundeszentrale f{\"u}r politische Bildung},
  year = 1987,
  address = {Bonn},
  edition = {Zweite},
  note = {Buchhandelsausgabe: Droste Verlag, D{\"u}sseldorf}
}

2. Import the following entry:

@Book{machiavelli78:_fuerst,
  author = {Niccolo Machiavelli},
  editor = {Rudolf Zorn},
  title = {Der F{\"u}rst},
  publisher = {Alfred K{\"o}rner Verlag},
  year = 1978,
  address = {Stuttgart},
  edition = {Sechste}
}

Added by Tim Hicks on May 20, 2007 11:40 AM

I agree that the 'editor' field should be a sequence of names as we currently have with the 'author' field.

Presumably, it should be easy enough to apply the field in the schema. However, the parsers and renderers would need updating. Also, we'd need reliable migration code for converting existing data to the new format.

Care to provide patches and tests?

No responses can be added.