Closed mcritchlow closed 8 years ago
Is there some reason we need to update this branch and not do:
# Gemfile
gem 'hydra', '9.1.0'
gem 'hydra-works', '0.7.0'
This to me seems like a better way to teach people what is going on. It makes it clear that hydra-works is a gem you can chose to use rather than a different (non-standard) version of hydra itself.
I was going with the previous convention.
But to answer your question, yes I think instructing users to add hydra-works in their Gemfile would be preferable to keeping a separate branch up to date. And, as you said, would be the pattern in real use anyway. Happy to update the tutorial to reflect this.
On Sun, Feb 21, 2016, 5:41 PM Justin Coyne notifications@github.com wrote:
Is there some reason we need to update this branch and not do:
Gemfilegem 'hydra', '9.1.0'gem 'hydra-works', '0.7.0'
This to me seems like a better way to teach people what is going on. It makes it clear that hydra-works is a gem you can chose to use rather than a different (non-standard) version of hydra itself.
— Reply to this email directly or view it on GitHub https://github.com/projecthydra/hydra/pull/97#issuecomment-186966628.
closing in favor of @jcoyne recommendation to directly reference hydra-works gem in tutorial
updating pcdm branch to use latest pcdm, hydra-works, and af-aggregations gems.
The Dive into Hydra works tutorials works fine, though I'm going to update it to properly reference the solr and fedora wrappers and related information.
Notes:
#in_works
example still returns[]
instead of the BibliographicWork as expected.