dependent on ActiveFedora::SolrService

[elrayle]

Observed Issues:

• the code should use Hyrax::SolrService instead of ActiveFedora::SolrService , so it would be best to fix this as they are identified
• because ActiveFedora is included in the set of gems, ActiveFedora::SolrService.new is called
• AF SolrService doesn’t find a config defining the solr URL so it uses the default which is http://127.0.0.1:8983/solr/hydra-development which is defined in ActiveFedora /config/solr.yml

Exploration

Confirmed consistent configuration of solr urls in:

path	gem that uses it
config/blacklight.yml	expected for Blacklight search builders
config/solr.yml	expected by ActiveFedora for ActiveFedora::SolrService
config/valkyrie_index.yml	expected by Valkyrie indexers

_NOTE: The values of SOLR_URL and VALKYRIE_SOLR_HOST/PORT/CORE are defined as environment variables in .env for development._

See PR #21 which was used to help diagnose which config was defining the observed solr core.

Temporary Solution

It turned out that if config/fedora.yml is not present (and it is not in nurax-pg), then ActiveFedora uses its default solr.yml. To avoid this, added the following configuration to the end of config/initializers/hyrax.rb in nurax-pg to define the path to the solr.yml config that sets up the correct solr core.

ActiveFedora.init(solr_config_path: Rails.root.join('config', 'solr.yml'))

[elrayle]

This addresses the issue in nurax-pg to use the correct core when ActiveFedora::SolrService is used. Long term, this should be using Hyrax:SolrService.

Leaving this open to track the transition to Hyrax::SolrService.

Related Work

TODO: Create a Hyrax issue to track this work.