Skip to content
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

Full text extraction contrib libraries as option #46

Open
grosscol opened this issue Sep 1, 2015 · 3 comments
Open

Full text extraction contrib libraries as option #46

grosscol opened this issue Sep 1, 2015 · 3 comments

Comments

@grosscol
Copy link

grosscol commented Sep 1, 2015

Some hydra development relies on additional functionality in solr. In order to support that development, the projects have been pulling in the libraries and modifying the solrconfig.xml using an install generator. With this functionality being pushed down the stack to hydra works samvera/hydra-works#195, the option to use an install generator goes away.

Is adding contrib libraries and modifying the solrconfig something that the community is interested in providing as an option at the jettywrapper level? This could be related to #33, as optional arguments could be a method of implementing this.

@jcoyne
Copy link
Contributor

jcoyne commented Sep 1, 2015

Sure. So you are proposing something like a rake task? rake jetty:install:fulltext or something?

@awead
Copy link
Contributor

awead commented Sep 1, 2015

There's already this set of tasks in Sufia that enable fulltext indexing:

https://github.com/projecthydra/sufia/blob/master/sufia-models/lib/tasks/sufia-models_tasks.rake#L37

It just downloads the appropriate jars. There's are solr config files in Sufia as well that are copied over to the jetty directory as part of this process too. It would be nice if different config options could be exacted and shared across different projects. Maybe jettywrapper is the place to do that.

@grosscol
Copy link
Author

grosscol commented Sep 3, 2015

@jcoyne, Yes. A rake task to do install fulltext or something similar would be convenient. Since it's a jettywrapper related configuration change, the thought was that it should be an optional task that lives in jetty.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants