Solr docs generated by ActiveFedora and Hyrax::ValkyrieWorkIndexer are not compatible

[elrayle]

Descriptive summary

I would expect the solr doc created by Hyrax::ValkyrieWorkIndexer to generate the same set of fields as the ActiveFedora generated solr doc.

Rationale

With both processes producing the same solr doc fields, existing solr indices will not need to be migrated when switching from ActiveFedora to Valkyrie.

Expected behavior

Generated fields would have the same field names and values.

Actual behavior

NOTE: Excluded all custom fields in our indexer.

Steps to reproduce the behavior

In my local app, I created a custom indexer which inherits from Hyrax::ValkyrieWorkIndexer. I use the following in a spec to create the publication work which is Valkyrie::Resource, save it, and index it.

  let!(:publication) do
    pub = FactoryBot.valkyrie_create(:publicationr, identifier: identifier)
    solr_doc = PublicationrIndexer.new(resource: pub).to_solr
byebug
    Hyrax::SolrService.new(use_valkyrie: true).add(solr_doc, commit: true)
    pub
  end

• valkyrie_create saves the work through ActiveFedora creating the ActiveFedora solr doc.
• Hyrax::SolrService saves the ValkyrieWorkIndexer generated solr doc to a separate solr core.

[elrayle]

Per discussion in Samvera-Tech call today, the diffs reflect work in progress. The path forward is to create PRs that move toward making the Hyrax::ValkyrieWorkIndexer consistent with the AF generated solr doc.

[elrayle]

Related Issues

Issue #4795 - Hyrax::Works do not show Date Added in Dashboard -> Works
Issue #4788 - Hyrax::Works do not show thumbnail in Dashboard -> Works
Issue #4794 - Hyrax::Works do not index file sets

[elrayle]

This is mostly complete. It appears that permissions is the only part that is not in the Valkyrie solr document. I opened Issue #4901 to cover just that part.

New comparison of the solr docs created by ActiveFedora and Valkyrie indexing...

Closing this issue. See Issue #4901 for remaining issue with permissions.