-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support loading custom metadata blocks #85
Comments
I would love to use dataverse-kubernetes to spin up Dataverse with the custom metadata block included in IQSS/dataverse#6289 by @doigl |
This was implemented today in IQSS/dataverse-ansible#135 for dataverse-ansible and I put some screenshots from my testing in a comment at IQSS/dataverse-ansible#133 (comment) @poikilotherm thanks for |
Great! We're going to test it as well! |
@4tikhonov perfect! Thanks! @donsizemore I just gave you and @poikilotherm a shout out in this thread called "custom metadata blocks now easier to spin up and evaluate" - https://groups.google.com/d/msg/dataverse-community/uKretKox_io/4FyPVAMYBgAJ Thanks again! 🎉 🎉 🎉 |
The schema files need to be downloaded from Dataverse and loaded into Solr. On the other hand, Solr needs to start without those, so a fallback is necessary. * We modify the schema.xml to include loaded files, but fallback to upstream default. * We add tini to have an init system for the sidecar * We add webhook from https://github.com/adnanh/webhook to have a framework to create our webhook * We add the webhook "update-schema" and its configuration * We add a startup script with some nice logic around the webhook application
We need to support people having their own custom metadata blocks. See upstream docs on this.
The text was updated successfully, but these errors were encountered: