The sage-1_0 should use "*_string" rather than "*_str", "string" rather than "whole", and other core related changes.

[kaladay]

Description

Using the incorrect copyfield name results in a failure when populating the index.

The filter query does not work as expected for "whole" strings. Change these "whole" strings used in core types to "string" (this will need further runtime testing).

The PR #549 introduced the "multivalue" field across the board. Play it safe and do not add the explicit "multivalue" attribute to the core types.

The date type cannot be used for date_published and date_created because the provided dates may not be in a supported format.

Both collection and resource are multivalued in DSpace. Change the solr core to support multiple values for both collection and resource.

Type of change

• [x] Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• [x] solr 9.3 and sage runtime.

Checklist:

• [x] My code follows the style guidelines of this project
• [x] I have performed a self-review of my code
• [x] I have commented my code, particularly in hard-to-understand areas
• [x] I have made corresponding changes to the documentation
• [x] My changes generate no new warnings
• [x] New and existing unit tests pass locally with my changes

[coveralls]

coverage: 45.792% (-0.02%) from 45.815% when pulling c42600d1ab83f93de90bc848c03fc65614083809 on solrconfig_should_use_string into 074fc8269e3a83b970b2da1110c084ce8ada915b on sprint-staging.