samvera-deprecated / hydra Goto Github PK

  # These before_filters apply the hydra access controls
  before_filter :enforce_show_permissions, :only=>:show

is now

  # These before_filters apply the hydra access controls
    before_action :enforce_show_permissions, only: :show

it should be commented out, and the following line added afterwards...
Hydra::SearchBuilder.default_processor_chain -= [:add_access_controls_to_solr_params]

Hydra 10.0.1 asks for solr_wrapper ~> 0.15.0, but the latest release of solr_wrapper is 0.19.0. This makes the difference b/w the task in "Dive Into Hydra" working by default vs someone having to go figure out what the latest version of solr is.

I am about to fix this and issue a pull request, I just wanted to have an issue to close when I do.

The release process contains information about a deprecation script which outputs commits that include deprecations. It doesn't say what you should do with that information.

It would be useful to add some clarity about what should go in release notes, too.

https://github.com/projecthydra/active_fedora/wiki/XML-Metadata-Datastreams

(Hang in there! This script takes a couple minutes to run.)
WARNING: These Hydra repositories do not have gems: projecthydra/hydra-jetty,
projecthydra/deprecated-projects, projecthydra-labs/rightsmetadata-policyfinder,
projecthydra-labs/hydradam, projecthydra-labs/hydra-admin-collections,
projecthydra-labs/projecthydra-labs.github.io, projecthydra-labs/engine_factory,
projecthydra-labs/sufia-vagrant, projecthydra-labs/reqflow, projecthydra-labs/open_annotation_models, 
projecthydra-labs/docs-working-group, projecthydra-labs/rdf-proxy_list,
projecthydra-labs/power-steering, projecthydra-labs/active-encode, projecthydra-labs/curation_concerns,
 projecthydra-labs/sufia-core, projecthydra-labs/hydra_controlled_vocabularies, projecthydra-labs/pcdm-geo-models, projecthydra-deprecated/anti-harassment_policy, projecthydra-deprecated/hydra-fixtures, projecthydra-deprecated/hydra-plugin_test_host, projecthydra-deprecated/hydra-workflow, projecthydra-deprecated/hydrangea, projecthydra-deprecated/hydrangea_articles, projecthydra-deprecated/hydrangea_books, projecthydra-deprecated/hydrangea_datasets, projecthydra-deprecated/libxml2, projecthydra-deprecated/model_migrator, projecthydra-deprecated/white_list

The following errors were encountered:
hydra-pbcore: Adding [email protected]: You do not have permission to manage this gem.
hybag: Adding [email protected]: You do not have permission to manage this gem.
hydra-works: Adding [email protected]: You do not have permission to manage this gem.
fedora-migrate: Adding [email protected]: You do not have permission to manage this gem.
hydra-pcdm: Adding [email protected]: You do not have permission to manage this gem.
hydra-tutorial: Adding [email protected]: You do not have permission to manage this gem.

Perhaps I haven't granted my access token the correct scope. What scopes are required?

The wiki page contains:

</blog/entry1/> a ldp:DirectContainer .
  </blog/entry1/> a ldp:membershipResource </blog/comments> .
  </blog/entry1/> a ldp:hasMemberRelation hasComment .
  </blog/entry1/> ldp:contains </blog/entry1/comments1> .

which is clearly buggy, the second and third lines are not RDF triples...

https://github.com/projecthydra/hydra-head/wiki/Access-Controls-with-Hydra

Should have a blank line between issues and wrap long lines.

Explain how to do this.
curationexperts/alexandria-legacy@91f3c61

On the Lesson Start FCRepo and Solr, Dive Into page are instructions to run "solr_wrapper". It's not present in the new demo dir, nor is a jetty/webapp dir anywhere. Did I skip something?
-rkh

Attempting the Dive-into-hydra tutorial and hung up on Ldp::HttpError when requisting the service. Tips?

Hi,

Thanks for the great tutorials for getting started with hydra!

This is just a comment regarding this lesson: https://github.com/projecthydra/hydra/wiki/Lesson%3A-Generate-Rails-Scaffolding-for-Creating-and-Editing-Books

And this step: Step 5: Allow Create and Update views to display Authors as a multi-valued field

I thought it might be worth mentioning in the lesson that making these changes will (at least in my experience) break some tests, namely:

Failed examples:

rspec ./spec/views/books/edit.html.erb_spec.rb:11 # books/edit renders the edit book form
rspec ./spec/views/books/new.html.erb_spec.rb:11 # books/new renders new book form
rspec ./spec/views/books/show.html.erb_spec.rb:11 # books/show renders attributes in

Regards,

Brad

Each project hydra gem should have a Travis Badge and Badge Fury

This could be scripted by leveraging the ./script/push_contributing_document.rb

Blacklight before 5.7.2 is broken with Rails 4.2.x, so the Hydra 7.x gem must either be pegged to Rails 4.1 or have it's Blacklight spec loosened a la samvera/hydra-head@3b3341a

The result of this change is the problem reported at: https://groups.google.com/forum/#!topic/hydra-tech/qLPqC49fhEE

ActionView::Template::Error (undefined method `to_model' for #ActiveSupport::HashWithIndifferentAccess:0x0000000594cc58):

In the lesson: make blacklight return search results everything works well till step 2 (I mean, the blacklight search interface shows up well and as expected - the search keyword 'Anna' doesn't return any results because till step 2 we didn't tell Blacklight which fields to search in).

But as soon as I re-run the rails server after amending:

config.default_solr_params = { 
      :qf => 'title_tesim author_tesim',
      :qt => 'search',
      :rows => 10  
    }

in app/controllers/catalog_controller.rb I get:

ActionView::Template::Error (undefined method `to_model' for #<ActiveSupport::HashWithIndifferentAccess:0x0000000594cc58>):
    11:          <span class="document-counter">
    12:          <%= t('blacklight.search.documents.counter', :counter => counter) if counter %>
    13:          </span>
    14:          <%= link_to_document document, :label=>document_show_link_field(document), :counter => counter %>
    15:         </h5>
    16: 
    17:         <% # bookmark functions for items/docs -%>

error in my console log.

And in my browser I get (Image attached):

Extracted source (around line #49):                
  # with all of the original params and block
  def method_missing(m, *args, &b)
    @_source.send(m, *args, &b)
  end

  def [] *args

Any suggestion for what could be done to solve this problem?

can i get data from one/more Linked Open Data(LOD) and Store it in own End point using hydra. is it possible? and if yes then how?
Suppose, i have a property named Author, value of Author is for example 'William Shakespeare', and dbpedia has some property named for example dbp:Author, so in this case i want something like Author name at my end point(William Shakespeare) linked with dbpedia's author(using sparql query) and get dbp:Author's content at my end point. received content should store in my end point or directlly publish over backlight. it will be best if this content shows when is search Author name='author='William Shakespeare' from backlight.

mrbond on IRC said:

set bundler to install into vendor/bundle and put it up into git. when you download it to windows window will delete the files. Git client (graphical) crashes. Using sourcetree it shows the files are deleted. however, it wouldn’t allow a commit because it can’t find the files. It /really/ seems like a git client bug to me, they should be able to deal with the missing files.

This is because in the docs/ there are filenames with colins -- an illegal character on windows.

https://wiki.duraspace.org/display/hydra/Hydra+Stack+-+The+Hierarchy+of+Promises

The Hierarchy of Promises is encoded in the Hydra gem.

I noticed that there are two different versions of the tutorial for building a hydra head:

1. Dive into Hydra at https://github.com/projecthydra/hydra/wiki/Dive-into-Hydra
2. How to Get Started Building your own Hydra Application at https://github.com/projecthydra/hydra-head/wiki/How-to-Get-Started

There are significant differences between the instructions and I've been able to start the hydra-jetty only using the Dive into Hydra tutorial. I suggest either updating the tutorial in the hydra-head repository, or replacing with a link to Dive into Hydra. If this is done, then I also suggest removing the link to the hydra-head tutorial in the Duraspace wiki page under "For Developers", here: https://wiki.duraspace.org/display/hydra/Developers#Developers-ForNewandPotentialAdopters:
Let me know if you think these changes are a good idea and I'll be happy to help implement them.

Project Hydra work proceeds by lazy consensus as per Apache Rave (http://rave.apache.org/docs/governance/lazyConsensus.html). This concept should be incorporated in the Contributing document.

RubyGems.org doesn't report a license for your gem. This is because it is not specified in the gemspec of your last release.

via e.g.

spec.license = 'MIT'
# or
spec.licenses = ['MIT', 'GPL-2']

Including a license in your gemspec is an easy way for rubygems.org and other tools to check how your gem is licensed. As you can imagine, scanning your repository for a LICENSE file or parsing the README, and then attempting to identify the license or licenses is much more difficult and more error prone. So, even for projects that already specify a license, including a license in your gemspec is a good practice. See, for example, how rubygems.org uses the gemspec to display the rails gem license.

There is even a License Finder gem to help companies/individuals ensure all gems they use meet their licensing needs. This tool depends on license information being available in the gemspec. This is an important enough issue that even Bundler now generates gems with a default 'MIT' license.

I hope you'll consider specifying a license in your gemspec. If not, please just close the issue with a nice message. In either case, I'll follow up. Thanks for your time!

Appendix:

If you need help choosing a license (sorry, I haven't checked your readme or looked for a license file), GitHub has created a license picker tool. Code without a license specified defaults to 'All rights reserved'-- denying others all rights to use of the code.
Here's a list of the license names I've found and their frequencies

p.s. In case you're wondering how I found you and why I made this issue, it's because I'm collecting stats on gems (I was originally looking for download data) and decided to collect license metadata,too, and make issues for gemspecs not specifying a license as a public service :). See the previous link or my blog post about this project for more information.

If the following tags exist:
v3.4.0
v3.4.0.rc1
v3.4.0.rc2
v3.4.0.rc3
v3.4.0.rc4

then it thinks v3.4.0.rc4 is the most recent. The correct value is v3.4.0

So, running rails g hydra jetty seems to go off without a hitch. But then...

ubuntu@ubuntu-i386:~/hydra/dive_into_hydra$ rake jetty:start
rake aborted!
Don't know how to build task 'jetty:start'

Hmmm. What's available?

ubuntu@ubuntu-i386:~/hydra/dive_into_hydra$ rake -T
rake about                                     # List versions of all Rails frameworks and the envi...
rake assets:clean[keep]                        # Remove old compiled assets
rake assets:clobber                            # Remove compiled assets
rake assets:environment                        # Load asset compile environment
rake assets:precompile                         # Compile all the assets named in config.assets.prec...
rake blacklight:check:solr[controller_name]    # Check the Solr connection and controller configura...
rake blacklight:delete_old_searches[days_old]  # Removes entries in the searches table that are old...
rake blacklight:install:migrations             # Copy migrations from blacklight to application
rake blacklight:solr:seed                      # Put sample data into solr
rake cache_digests:dependencies                # Lookup first-level dependencies for TEMPLATE (like...
rake cache_digests:nested_dependencies         # Lookup nested dependencies for TEMPLATE (like mess...
rake db:create                                 # Creates the database from DATABASE_URL or config/d...
rake db:drop                                   # Drops the database from DATABASE_URL or config/dat...
rake db:fixtures:load                          # Load fixtures into the current environment's database
rake db:migrate                                # Migrate the database (options: VERSION=x, VERBOSE=...
rake db:migrate:status                         # Display status of migrations
rake db:rollback                               # Rolls the schema back to the previous version (spe...
rake db:schema:cache:clear                     # Clear a db/schema_cache.dump file
rake db:schema:cache:dump                      # Create a db/schema_cache.dump file
rake db:schema:dump                            # Create a db/schema.rb file that is portable agains...
rake db:schema:load                            # Load a schema.rb file into the database
rake db:seed                                   # Load the seed data from db/seeds.rb
rake db:setup                                  # Create the database, load the schema, and initiali...
rake db:structure:dump                         # Dump the database structure to db/structure.sql
rake db:version                                # Retrieves the current schema version number
rake doc:app                                   # Generate docs for the app -- also available doc:ra...
rake hydra:fixtures:delete                     # Remove default Hydra fixtures
rake hydra:fixtures:refresh                    # Refresh default Hydra fixtures
rake hydra:init                                # Init Hydra configuration
rake hydra:jetty:config                        # Copies the default Solr & Fedora configs into the ...
rake hydra:jetty:config_fedora                 # Copies a custom fedora config for the bundled Hydr...
rake hydra:jetty:config_solr                   # Copies the contents of solr_conf into the Solr dev...
rake hydra:jetty:load                          # Copies the default SOLR config files and starts up...
rake hydra:load_models                         # Load hydra-head models
rake jetty:config                              # Apply all configs to Testing Server (relies on hyd...
rake log:clear                                 # Truncates all *.log files in log/ to zero bytes (s...
rake middleware                                # Prints out your Rack middleware stack
rake notes                                     # Enumerate all annotations (use notes:optimize, :fi...
rake notes:custom                              # Enumerate a custom annotation, specify with ANNOTA...
rake rails:template                            # Applies the template supplied by LOCATION=(/path/t...
rake rails:update                              # Update configs and some other initially generated ...
rake repo:delete                               # Delete the object identified by pid
rake repo:delete_range                         # Delete a range of objects in a given namespace
rake repo:export                               # Export the object identified by pid into spec/fixt...
rake repo:load                                 # Load the object located at the provided path or id...
rake repo:refresh                              # Delete and re-import the object identified by pid
rake routes                                    # Print out all defined routes in match order, with ...
rake secret                                    # Generate a cryptographically secure secret key (th...
rake stats                                     # Report code statistics (KLOCs, etc) from the appli...
rake test                                      # Runs test:units, test:functionals, test:generators...
rake test:all                                  # Run tests quickly by merging all types and not res...
rake test:all:db                               # Run tests quickly, but also reset db
rake time:zones:all                            # Displays all time zones, also available: time:zone...
rake tmp:clear                                 # Clear session, cache, and socket files from tmp/ (...
rake tmp:create                                # Creates tmp directories for sessions, cache, socke...

Maybe try load?

ubuntu@ubuntu-i386:~/hydra/dive_into_hydra$ rake hydra:jetty:load
rake aborted!
Don't know how to build task 'jetty:start'

Tasks: TOP => hydra:jetty:load

Or config?

ubuntu@ubuntu-i386:~/hydra/dive_into_hydra$ rake hydra:jetty:config
/home/ubuntu/hydra/dive_into_hydra/fedora_conf/conf/development/fedora.fcfg file not found -- skipping fedora config
/home/ubuntu/hydra/dive_into_hydra/fedora_conf/conf/test/fedora.fcfg file not found -- skipping fedora config

The following errors were encountered:
hydra-groupy -a [email protected] -a [email protected] -a [email protected] -a [email protected] -a [email protected] -a [email protected] -a [email protected] -a [email protected] -a [email protected] -a [email protected] -a [email protected] -a [email protected] -a [email protected] -a [email protected] -a [email protected] -a [email protected] -a [email protected] -a [email protected] -a [email protected] -a [email protected] -a [email protected] -a [email protected] -a [email protected] -a [email protected] -a [email protected] -a [email protected] -a [email protected] -a [email protected] -a [email protected] -a [email protected]: Adding [email protected]: You do not have permission to manage this gem.

@jeremyf you are the only rubygem owner of that project. Please grant someone else authority or remove hydra-groupy from the grant_revoke_gem_authority.rb.

re-running bundle install fixes the error, but we should probably clean it up.

Output from my clean install (in my dev VM):

/hydra-demo$ rails g hydra:install
generate blacklight --devise
... _lots of predictable stuff here- ...
run bundle install from "."
...
Your bundle is complete!
... yet more stuff you would expect ...
... and finally ...
rake db:migrate
Could not find gem 'rspec-rails (>= 0) ruby' in the gems available on this machine.
Run bundle install to install missing gems.
camper@hydra-vbox:

Per Core Developers meeting bring the non Git Flow aspects of the Contributing document into the base Hydra gem.

There should be something about it here: https://github.com/projecthydra/hydra/wiki/Lesson%3A-install-hydra-jetty

On the Dive-into-Hydra lesson https://github.com/projecthydra/hydra/wiki/Lesson---make-blacklight-return-search-results

Update the instructions to just say add the following line since it won't be in the catalog controller anymore.

  Hydra::SearchBuilder.default_processor_chain -= [:add_access_controls_to_solr_params]

I am getting error when running "bin/rails hydra:server"

root@92bce299f2d1:/opt/myapp01# bin/rails hydra:server
rails aborted!
NameError: uninitialized constant SolrWrapper
/usr/local/rvm/gems/ruby-2.4.0/gems/active-fedora-11.4.0/lib/active_fedora/rake_support.rb:17:in with_server' /usr/local/rvm/gems/ruby-2.4.0/gems/hydra-core-10.5.0/lib/tasks/hydra.rake:6:in block (2 levels) in <top (required)>'
/usr/local/rvm/gems/ruby-2.4.0/gems/railties-5.1.2/lib/rails/commands/rake/rake_command.rb:21:in block in perform' /usr/local/rvm/gems/ruby-2.4.0/gems/railties-5.1.2/lib/rails/commands/rake/rake_command.rb:18:in perform'
/usr/local/rvm/gems/ruby-2.4.0/gems/railties-5.1.2/lib/rails/command.rb:46:in invoke' /usr/local/rvm/gems/ruby-2.4.0/gems/railties-5.1.2/lib/rails/commands.rb:16:in <top (required)>'
/opt/myapp01/bin/rails:9:in require' /opt/myapp01/bin/rails:9:in <top (required)>'
/usr/local/rvm/gems/ruby-2.4.0/gems/spring-2.0.2/lib/spring/client/rails.rb:28:in load' /usr/local/rvm/gems/ruby-2.4.0/gems/spring-2.0.2/lib/spring/client/rails.rb:28:in call'
/usr/local/rvm/gems/ruby-2.4.0/gems/spring-2.0.2/lib/spring/client/command.rb:7:in call' /usr/local/rvm/gems/ruby-2.4.0/gems/spring-2.0.2/lib/spring/client.rb:30:in run'
/usr/local/rvm/gems/ruby-2.4.0/gems/spring-2.0.2/bin/spring:49:in <top (required)>' /usr/local/rvm/gems/ruby-2.4.0/gems/spring-2.0.2/lib/spring/binstub.rb:31:in load'
/usr/local/rvm/gems/ruby-2.4.0/gems/spring-2.0.2/lib/spring/binstub.rb:31:in <top (required)>' /opt/myapp01/bin/spring:15:in <top (required)>'
bin/rails:3:in load' bin/rails:3:in

'
Tasks: TOP => hydra:server
(See full trace by running task with --trace)

Not sure if we should leave in support for 4.x (in Hydra 10.x) or consider this one of the breaks from Hydra 9 --> Hydra 10.

In a test Windows environment, I followed the Dive into Hydra instructions. Solr and Fedora started fine, but when I attempt to go to the Blacklight page at localhost:3000 I see the following error:

Any advice would be greatly appreciated.

Github provides an easy way to administer who has privileges for a given repository. But Github's administration is not for the creation of a formal Rubygems gem.
Instead a gem owner must manually add and remove gem owners from Rubygems via command line: gem owner my_gem -a [email protected]

We presently have 25 gems, each with different ownership lists.

Ideally we should provide the initial gem owner with an easy script to append owners to the Rubygems gem.

What likely makes the most sense is to create a list of emails in this repo that can be used to see the gem ownership.

ISSUE
I've just tried generating an app from scratch (Dive-into-Hydra) using the current release candidate (which worked in April), but now I'm getting errors. The dependencies in the 'hydra' gem should be tight enough that a release doesn't break because of future version updates to dependent gems. Possibly, we're just not managing semver successfully in some dependency...

Gemfile

gem 'hydra', '9.1.0.rc1'

I also tested

gem 'hydra', github: 'projecthydra/hydra', branch: 'master'

ERROR

Started GET "/" for 10.0.2.2 at 2015-10-27 14:29:42 +0000
Cannot render console from 10.0.2.2! Allowed networks: 127.0.0.1, ::1, 127.0.0.0/127.255.255.255

Ldp::HttpError (STATUS: 503 ...):
  ldp (0.3.1) lib/ldp/client/methods.rb:108:in `block in check_for_errors'
  ldp (0.3.1) lib/ldp/client/methods.rb:106:in `tap'
  ldp (0.3.1) lib/ldp/client/methods.rb:106:in `check_for_errors'
  ldp (0.3.1) lib/ldp/client/methods.rb:24:in `head'
  active-fedora (9.1.2) lib/active_fedora/fedora.rb:41:in `init_base_path'
  active-fedora (9.1.2) lib/active_fedora/fedora.rb:5:in `initialize'
  active-fedora (9.1.2) lib/active_fedora.rb:207:in `new'
  active-fedora (9.1.2) lib/active_fedora.rb:207:in `fedora'
  active-fedora (9.1.2) lib/active_fedora/ldp_cache.rb:40:in `reset_cache_settings'
  active-fedora (9.1.2) lib/active_fedora/ldp_cache.rb:33:in `rescue in call'
  active-fedora (9.1.2) lib/active_fedora/ldp_cache.rb:24:in `call'
  activerecord (4.2.4) lib/active_record/migration.rb:377:in `call'
  actionpack (4.2.4) lib/action_dispatch/middleware/callbacks.rb:29:in `block in call'
  activesupport (4.2.4) lib/active_support/callbacks.rb:88:in `__run_callbacks__'
  activesupport (4.2.4) lib/active_support/callbacks.rb:778:in `_run_call_callbacks'
  activesupport (4.2.4) lib/active_support/callbacks.rb:81:in `run_callbacks'
  actionpack (4.2.4) lib/action_dispatch/middleware/callbacks.rb:27:in `call'
  actionpack (4.2.4) lib/action_dispatch/middleware/reloader.rb:73:in `call'
  actionpack (4.2.4) lib/action_dispatch/middleware/remote_ip.rb:78:in `call'
  actionpack (4.2.4) lib/action_dispatch/middleware/debug_exceptions.rb:17:in `call'
  web-console (2.2.1) lib/web_console/middleware.rb:31:in `call'
  actionpack (4.2.4) lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
  railties (4.2.4) lib/rails/rack/logger.rb:38:in `call_app'
  railties (4.2.4) lib/rails/rack/logger.rb:20:in `block in call'
  activesupport (4.2.4) lib/active_support/tagged_logging.rb:68:in `block in tagged'
  activesupport (4.2.4) lib/active_support/tagged_logging.rb:26:in `tagged'
  activesupport (4.2.4) lib/active_support/tagged_logging.rb:68:in `tagged'
  railties (4.2.4) lib/rails/rack/logger.rb:20:in `call'
  actionpack (4.2.4) lib/action_dispatch/middleware/request_id.rb:21:in `call'
  rack (1.6.4) lib/rack/methodoverride.rb:22:in `call'
  rack (1.6.4) lib/rack/runtime.rb:18:in `call'
  activesupport (4.2.4) lib/active_support/cache/strategy/local_cache_middleware.rb:28:in `call'
  rack (1.6.4) lib/rack/lock.rb:17:in `call'
  actionpack (4.2.4) lib/action_dispatch/middleware/static.rb:116:in `call'
  rack (1.6.4) lib/rack/sendfile.rb:113:in `call'
  railties (4.2.4) lib/rails/engine.rb:518:in `call'
  railties (4.2.4) lib/rails/application.rb:165:in `call'
  rack (1.6.4) lib/rack/lock.rb:17:in `call'
  rack (1.6.4) lib/rack/content_length.rb:15:in `call'
  rack (1.6.4) lib/rack/handler/webrick.rb:88:in `service'
  /home/vagrant/.rvm/rubies/ruby-2.2.3/lib/ruby/2.2.0/webrick/httpserver.rb:138:in `service'
  /home/vagrant/.rvm/rubies/ruby-2.2.3/lib/ruby/2.2.0/webrick/httpserver.rb:94:in `run'
  /home/vagrant/.rvm/rubies/ruby-2.2.3/lib/ruby/2.2.0/webrick/server.rb:294:in `block in start_thread'

NOTE: I'm running in a VM using port forwarding, hence the 'cannot render console' warning.

Per Core Developers meeting include reference to the hierarchy of promises https://wiki.duraspace.org/display/hydra/Hydra+Stack+-+The+Hierarchy+of+Promises

I'd like to request that at least one known working Gemfile.lock be distributed with the Dive into Hydra instructions. I don't think it should be part of the instructions, but it would be helpful when troubleshooting when things break due to dependency changes.

Hi, is this project connected to http://www.hydra-cg.com/ https://www.w3.org/community/hydra/ in any way? You are both in the linked data space and it seems confusing to me.

cc @lanthaler as the W3C Hydra CG chair.

• Nokogiri to 1.7
• ActiveFedora to 11.1
• Remove nom-xml
• Remove OM
• Rails to 5.0
• Blacklight to 6.7
• LDP to 0.6
• Hydra-head to 10.3
• Solr_wrapper to latest #116
• Fcrepo_wrapper to latest
• ActiveTriples to 0.11

Colons are not friendly on windows file systems.

Among other things, you cannot build experiments against any of the hydra-labs aggregation or pcdm gems without hydra and hydra-head supporting something later than AF 9.1.x

I am trying to put another RC together, but the Doubletree network is slow.

If you don't have a dependency gem (e.g. jettywrapper) cloned in the directory above hydra, the deprecation script fails. It should explain what it is looking for and why.

In the Gemfile
'''
gem "hydra", "6.0.0.rc2"
gem "blacklight"
'''

In terminal:
'''
~/Develop/ruby/hydra-tutorials master: rails generate hydra:head -f
force app/controllers/catalog_controller.rb
create config/initializers/hydra_config.rb
insert config/initializers/hydra_config.rb
create config/initializers/action_dispatch_http_upload_monkey_patch.rb
create config/role_map_cucumber.yml
create config/role_map_development.yml
create config/role_map_production.yml
create config/role_map_test.yml
/Users/matt/.rvm/gems/ruby-1.9.3-p194/gems/active-fedora-6.0.0/lib/generators/active_fedora/config/solr/solr_generator.rb:4: Use RbConfig instead of obsolete and deprecated Config.
/Users/matt/.rvm/gems/ruby-1.9.3-p194/gems/thor-0.18.1/lib/thor/invocation.rb:118:in invoke_command': undefined methodname' for nil:NilClass (NoMethodError)
from /Users/matt/.rvm/gems/ruby-1.9.3-p194/gems/thor-0.18.1/lib/thor/group.rb:231:in dispatch' from /Users/matt/.rvm/gems/ruby-1.9.3-p194/gems/thor-0.18.1/lib/thor/invocation.rb:109:ininvoke'
from /Users/matt/.rvm/gems/ruby-1.9.3-p194/gems/active-fedora-6.0.0/lib/generators/active_fedora/config/config_generator.rb:6:in generate' from /Users/matt/.rvm/gems/ruby-1.9.3-p194/gems/thor-0.18.1/lib/thor/command.rb:27:inrun'
from /Users/matt/.rvm/gems/ruby-1.9.3-p194/gems/thor-0.18.1/lib/thor/invocation.rb:120:in invoke_command' from /Users/matt/.rvm/gems/ruby-1.9.3-p194/gems/thor-0.18.1/lib/thor/invocation.rb:127:inblock in invoke_all'
from /Users/matt/.rvm/gems/ruby-1.9.3-p194/gems/thor-0.18.1/lib/thor/invocation.rb:127:in each' from /Users/matt/.rvm/gems/ruby-1.9.3-p194/gems/thor-0.18.1/lib/thor/invocation.rb:127:inmap'
from /Users/matt/.rvm/gems/ruby-1.9.3-p194/gems/thor-0.18.1/lib/thor/invocation.rb:127:in invoke_all' from /Users/matt/.rvm/gems/ruby-1.9.3-p194/gems/thor-0.18.1/lib/thor/group.rb:233:indispatch'
from /Users/matt/.rvm/gems/ruby-1.9.3-p194/gems/thor-0.18.1/lib/thor/invocation.rb:109:in invoke' from /Users/matt/.rvm/gems/ruby-1.9.3-p194/gems/hydra-core-6.0.0/lib/generators/hydra/head_generator.rb:47:increate_configuration_files'
from /Users/matt/.rvm/gems/ruby-1.9.3-p194/gems/thor-0.18.1/lib/thor/command.rb:27:in run' from /Users/matt/.rvm/gems/ruby-1.9.3-p194/gems/thor-0.18.1/lib/thor/invocation.rb:120:ininvoke_command'
from /Users/matt/.rvm/gems/ruby-1.9.3-p194/gems/thor-0.18.1/lib/thor/invocation.rb:127:in block in invoke_all' from /Users/matt/.rvm/gems/ruby-1.9.3-p194/gems/thor-0.18.1/lib/thor/invocation.rb:127:ineach'
from /Users/matt/.rvm/gems/ruby-1.9.3-p194/gems/thor-0.18.1/lib/thor/invocation.rb:127:in map' from /Users/matt/.rvm/gems/ruby-1.9.3-p194/gems/thor-0.18.1/lib/thor/invocation.rb:127:ininvoke_all'
from /Users/matt/.rvm/gems/ruby-1.9.3-p194/gems/thor-0.18.1/lib/thor/group.rb:233:in dispatch' from /Users/matt/.rvm/gems/ruby-1.9.3-p194/gems/thor-0.18.1/lib/thor/base.rb:439:instart'
from /Users/matt/.rvm/gems/ruby-1.9.3-p194/gems/railties-3.2.13/lib/rails/generators.rb:171:in invoke' from /Users/matt/.rvm/gems/ruby-1.9.3-p194/gems/railties-3.2.13/lib/rails/commands/generate.rb:12:in<top (required)>'
from /Users/matt/.rvm/gems/ruby-1.9.3-p194/gems/activesupport-3.2.13/lib/active_support/dependencies.rb:251:in require' from /Users/matt/.rvm/gems/ruby-1.9.3-p194/gems/activesupport-3.2.13/lib/active_support/dependencies.rb:251:inblock in require'
from /Users/matt/.rvm/gems/ruby-1.9.3-p194/gems/activesupport-3.2.13/lib/active_support/dependencies.rb:236:in load_dependency' from /Users/matt/.rvm/gems/ruby-1.9.3-p194/gems/activesupport-3.2.13/lib/active_support/dependencies.rb:251:inrequire'
from /Users/matt/.rvm/gems/ruby-1.9.3-p194/gems/railties-3.2.13/lib/rails/commands.rb:29:in <top (required)>' from script/rails:6:inrequire'
from script/rails:6:in `

Hello,

Is hydra-head compatible with blacklight 5.1.0 ? Cause when I try to install last version of hydra, it throws that hydra-head depends on blacklight 4.7

Thanks.

Port this commit the the 5.5 branch and release a new version. projectblacklight/blacklight@ec145c3

The current work around is to add the line @import 'bootstrap-sprockets'; to the very beginning of app/assets/stylesheets/blacklight.css.scss in the host machine.

When attempting to run the fcrepo_wrapper with a specific port it appears the pull is failing. W/ https_proxy set I get..
rubies/ruby-2.2.1/lib/ruby/2.2.0/open-uri.rb:257:in 'open_http': Non-HTTP proxy URI: https://... (RuntimeError)

W/ http_proxy set or no proxy defined..
rubies/ruby-2.2.1/lib/ruby/2.2.0/net/http.rb:879:in 'initialize': Connection refused - connect(2) for "github.com" port 443 (Errno::ECONNREFUSED)

The build link under Code Status points to https://travis-ci.org/projecthydrahydra/hydra-head - should probably be https://travis-ci.org/projecthydra/hydra

The travis build for the hydra gem has also not run for April 2013

The lesson Build a Codex model with XML includes out-of-date syntax for associating a model with a datastream. It seems ActiveFedora 10.0.0 renamed contains to has_subresource and that it simply removed the delegate_to: functionality on property (commit here).

I'm new to Hydra but I'd be happy to update the tutorial if I knew what new functionality was intended to replace this. The deprecation message referenced "Forms" – is this still used in Hydra 11? Where can I find documentation on this?

E.G. in the dive-into-hydra tutorial at https://github.com/projecthydra/hydra/wiki/Lesson---Start-FCRepo-and-Solr#step-1-start-solr

Solr seems to withdraw older versions sooner than we'd like, might need to find a different archive location, remove the version from the wrapper file, or ....