-
-
Notifications
You must be signed in to change notification settings - Fork 57
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
Change publisher to dictionary #105
Conversation
Could this be implemented in a way that makes defining a standalone location for everything that isn't an event possible? In my university it seems to be standard practice to sometimes only display the location of a book, not the publisher itself, so I don't always have that information. Right now I have to define an empty string for the publisher, which obviously isn't ideal. Line 318 in d2db1fa
|
That would kind of be the current implementation. Technically, in my implementation you can always define a location but
If I may ask: Why? And what style are you using? It seems odd and is certainly not intended by most styles.
In my version, hayagriva behaves exactly the same: If no publisher is present, it shows no location. If I am correct, and having a location but no publisher is not intended, adding an empty string seems fair. |
Okay after looking through some more random sociology and political science books, only two included the publisher's name and five didn't while all included the location. Obviously not representative, but I think it shows that that style is at least somewhat common place. And don't get me wrong: I think it's pretty weird too and it makes finding the correct book a lot harder but maybe hayagriva might want to support it because enough people seem to use it? Besides, what is the actual gain of forbidding it? Also I think making the |
Strange... But yeah, in that case we should support it. The question is whether we consider it rare enough that setting the publisher's name to an empty string is the way to support it (in which case, we should document that), or just disregard this PR.
The gain of this PR is to structure the information in hayagriva better. And as far as I can see, in the vast majority of styles and for most tools, a location without a publisher is not intended.
That's possible. But if someone just writes |
I think that's a good compromise, maybe it could accept the following: guide:
...
publisher: Megadodo
guide:
...
publisher:
name: Megadodo
location: Ursa Minor
guide:
...
publisher:
location: Ursa Minor Would that work? |
That looks good |
I think that renaming |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks nice! Here are some observations (paging @reknih for further thoughts).
Co-authored-by: PgBiel <9021226+PgBiel@users.noreply.github.com>
Thank you! |
Follows and fixes #34.
Changes:
publisher
field to be either aFormatString
or a dictionary withname
andlocation
.location
field remains but only for events; publisher location must be in thepublisher
field.To discuss:
location
field of an entry be renamed (e.g.,event-location
) or handled in another way?TODO: