Skip to content

Shorter nodeserver resource names#8

Merged
SarahZum merged 3 commits intoSarahZum:masterfrom
karlbecker:feature/shorter-nodeserver-resource-names
Aug 11, 2017
Merged

Shorter nodeserver resource names#8
SarahZum merged 3 commits intoSarahZum:masterfrom
karlbecker:feature/shorter-nodeserver-resource-names

Conversation

@karlbecker
Copy link
Copy Markdown
Contributor

@karlbecker karlbecker commented Aug 11, 2017

Hi @SarahZum !

After setting things up on my own, thought a few tweaks to names of things might help this be a little more straightforward:

  • browzine is in the /primo/browzine/browzineJournals URL twice, so how about we eliminate the second reference to it and instead have /primo/browzine/browzineJournals ?
  • same with browzineArticleInContext, except I simplified it down even further to articles since the resource being requested really is just an article - it just so happens to include an "article in context" URL, but it also has just general information about the article, too
  • rename of the env variables to include browzine in the name so systems with other env variables can more clearly separate these two from other vars

I think all of these things simplify the code a little bit, and things like the env vars hopefully help the long-term maintenance for anyone who installs this on their own server, too.

What do you think?

Thanks!

  • Karl

I missed this on first glance, too - there's a comma instead of a dot!
…ls and articles

The default URL has primo/browzine/ already in it, so if we use that, we already identify this URL as being related to browzine.
Also, this entire repo has browzine in the name, so the node server being for browzine articles and journals should be fairly clear - and the README should make that clear.
…zineLibraryID

It'll be a little clearer, especially for systems that may have many env vars on them
@SarahZum
Copy link
Copy Markdown
Owner

Thanks Karl, makes sense to me!

@SarahZum SarahZum merged commit b4f787b into SarahZum:master Aug 11, 2017
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

Successfully merging this pull request may close these issues.

2 participants