Hi there,
my problem is to design a proper working review-format. I have the author of the review, the editor of the Journal. So far so good. But I have additional the author of the reviewed book. No problem to define a field for that also no problem to define a field for the Editor of the reviewed book who also appears not seldom.
My problem is that I have to insert these names as I want them to be used in the formatted bibliography (first name last name order) and am not able to use the settings for that in the formatting dialog.
If I'm not overseeing something this is not possible at the moment in Bookends. Therefor I would request the features: "field is author" and "field is editor". I can imagine this is quite easy in Preferences > References. In the Field Labels section a context-menu when clicking on a lable could be displayed with the both named entries.
It would be great if these options would also attach the field to the according Term-list.
By the way there are further fields which would be significantly improved the same way: Translator, transkribed Author etc.
Additional I think it would be great to have the option to use the same term lists for Editors and authors and translators and so on or to separate them, as user likes.
And two further feature requests are to be named round here, because it would be the same kind of improvement: The named context-menu could also contain the additional entries:
- "field is volume" which would enable the issue-numbers to be placed in parenthesis.
- "field is location". I think I requested something like this some time ago. The problem: some publishing houses name two, three or even more locations. In some formats they are named all, in other only the first, in others the first with et al. I would like to add them in single rows as I do with multiple authors and then define how they are used in the format. There are different ways e. g. "München–Wien–Zürich" (with en-dashes) or "München/Wien/Zürich".
I don't know if thisproblem is a German specific but it would be great if Bookends could handle this at least for German users. That's for sure.
And there's an additonal problem in handling German city-names:
You could write "Frankfurt am Main", "Frankfurt/Main", "Frankfurt a. M.", "Frankfurt/M.", "Frankfurt" (which is also usual but not definitely) or "Ffm". They are all very common and everybody understands what is meant. Further notations are imaginable. My request is, that a unified handling via the bibliography formatting in Bookends is able.
To illustrate the problem: If I have to cite with multiple locations "Frankfurt/Main–Berlin" is very common but if you have to cite with slashes "Frankfurt/Main/Berlin" would be nonsense.
I think the easiest would be a Location-Glossary. Option 1 would be just a columned list where user has to define every possible notation he wants to use. Same column would have to contain the same notation. In the formatting dialog then I could choose which way I want to use via the selection of the column (which could be named by user to make it easier).
Option 2:
Full name: Frankfurt am Main
abbreviation: Ffm
abbreviation of the name additon: M.
A second section of the Glossary could contain a list of conjunctions:
full: am – abbr.: a.
second example: full: im - abbr.: i.
In the formatting dialog then I could choose if I want to use the full location name, the abbreviated version with abbreviated name addion. The third choose should show a pulldown menu with the list of the conjunctions:
full
abbr.
/
em-dash
en-dash
dash
space
All a bit complicated but Bookends could simplify the handling of this stuff significant.
All the best
Feature Request: further author/editor-fields
Two things may help:
1. In a format, putting a * after a field means that Bookends will treat it as a name field (e.g. u1* will apply the name formatting options [surname first, initials only, etc.] to the contents of User1).
2. Any field in the main view can have a term list (including the user-defined fields). User Utilities -> Term Lists -> Add List. They will then also have autocomplete enabled.
Jon
Sonny Software
1. In a format, putting a * after a field means that Bookends will treat it as a name field (e.g. u1* will apply the name formatting options [surname first, initials only, etc.] to the contents of User1).
2. Any field in the main view can have a term list (including the user-defined fields). User Utilities -> Term Lists -> Add List. They will then also have autocomplete enabled.
Jon
Sonny Software
thank you very much. I have overseen that. Great.Jon wrote:1. In a format, putting a * after a field means that Bookends will treat it as a name field (e.g. u1* will apply the name formatting options [surname first, initials only, etc.] to the contents of User1).
Yes, I know that. Thanks.Jon wrote:2. Any field in the main view can have a term list (including the user-defined fields). User Utilities -> Term Lists -> Add List. They will then also have autocomplete enabled.
But if I'm not wrong this helps to unifiy the data entry but not the output and does not solve the problems I described with locations.
Also it isn't possible to use the same term list for two fields what also would be great.
Also you didn't comment the suggestion of "field is volume".
What do you think of the requests besides the first one which is useless because Bookends already solves this problem?
Hi Reiner,
To be honest, I think they are very specific issues that are not of general interest, and the kind of thing that leads to application bloat. I am much more likely to add features that solve general problems and/or don't impose an interface penalty on users who have no interest in them.
Jon
Sonny Software
To be honest, I think they are very specific issues that are not of general interest, and the kind of thing that leads to application bloat. I am much more likely to add features that solve general problems and/or don't impose an interface penalty on users who have no interest in them.
Jon
Sonny Software