You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For a while we were almost exclusively using "dynamic" fields in Solr that have underscores in them:
type_s
subtree_ss
citationyear_i
We did this for speed of development and convenience (everyone can use Solr "as is" out of the box) but we are now requiring a Dataverse-specific Solr schema.xml. We are aiding in constructing it with a new API call ( http://localhost:8080/api/config/solr/schema ) so we can hard-code metadata fields into schema.xml, including "copyField" directives into the "catchall" field.
Originally, this ticket said "finalize" but I changed it to say "define" since I'm sure we'll continue to iterate on the schema.xml.
But for the purposes of QA, a lot of work was done this week in this area and we think it's good enough for now.
Instructions for updating one's schema.xml are in the dev guide.
The text was updated successfully, but these errors were encountered:
Author Name: Philip Durbin (@pdurbin)
Original Redmine Issue: 3480, https://redmine.hmdc.harvard.edu/issues/3480
Original Date: 2014-02-03
Original Assignee: Elda Sotiri
For a while we were almost exclusively using "dynamic" fields in Solr that have underscores in them:
We did this for speed of development and convenience (everyone can use Solr "as is" out of the box) but we are now requiring a Dataverse-specific Solr schema.xml. We are aiding in constructing it with a new API call ( http://localhost:8080/api/config/solr/schema ) so we can hard-code metadata fields into schema.xml, including "copyField" directives into the "catchall" field.
Originally, this ticket said "finalize" but I changed it to say "define" since I'm sure we'll continue to iterate on the schema.xml.
But for the purposes of QA, a lot of work was done this week in this area and we think it's good enough for now.
Instructions for updating one's schema.xml are in the dev guide.
The text was updated successfully, but these errors were encountered: