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
The scholars-discovery Solr client can create these before schematize (poorly named process of creating the fields ad copy fields). We should persist them and a database may be preferred over additional configuration. This requires JPA entity, CRUD endpoints, and additional administrative tab in scholars-angular. I think provisioning is a reasonable identifier for this state and can refactor schematize while doing so. These field types have to be defined before the addition of fields and copy fields.
The custom defined fields should be moved out of the managed_schema into a persistent entity.
It is not recommended to modify the managed_schema directly.
https://solr.apache.org/guide/solr/latest/indexing-guide/schema-api.html
The text was updated successfully, but these errors were encountered: