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

Format reference to article in book #43

Open
stweil opened this issue Sep 11, 2017 · 1 comment
Open

Format reference to article in book #43

stweil opened this issue Sep 11, 2017 · 1 comment

Comments

@stweil
Copy link
Member

stweil commented Sep 11, 2017

An article in a book like this example currently looks strange. From the example:

[...]. In: Hänger,Christian 50 Jahre UB Mannheim : Entwicklung und Perspektiven, Mannheim : Mannheim University Press, S. 147-160.

How should it look like? Is it correct to name only one of the editors? Should there be a space after the comma in the editor's name? Or use first name before name for the editor(s), too? How to separate editor(s) and book title?

Maybe like this?

[...]. In: Christian Hänger, Annette Klein : 50 Jahre UB Mannheim : Entwicklung und Perspektiven, Mannheim : Mannheim University Press, S. 147-160.

@zuphilip
Copy link
Member

In our EPrints we only save one book editor, but I don't know from where/when this rule comes from: "Autor/Hrsg. des Buches (nur der Erstgenannte!): " see https://ub-madoc.bib.uni-mannheim.de/42798/

The ordering of the name and spacing is fixed in the new version v0.1.4, see also http://bibtemp.bib.uni-mannheim.de/mannheim .

I would like to add the information about the role, i.e. something like (Hrsg.), see issue #25 .

I guess we should also add some delimiter like : but here we are free to do so, because we have our own template, see https://github.com/UB-Mannheim/publist4ubma2/blob/master/Resources/Private/Partials/FrontendBibCoinTemplate.html

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

No branches or pull requests

2 participants