search

TAMULib / scholars-discovery

MIT License
1 stars 1 forks source link

Relocate custom defined fields and create in Solr before schematizing #346

Open ghost opened 1 year ago

ghost commented 1 year ago

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

wwelling commented 2 months ago

Here are explicitly defined field type and dynamic field type.

https://github.com/TAMULib/scholars-discovery/blob/tamu-main/solr/configsets/scholars-discovery/conf/managed-schema.xml#L206

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.

wwelling commented 2 months ago

Blocked by https://github.com/TAMULib/scholars-discovery/issues/367