Re: Migrating from Endeca
Thanks all. I'll have a poke around Hue, but depending on how it goes may end up doing as Jack suggests and extending the existing admin UI. On 21 September 2013 02:50, Shawn Heisey wrote: > On 9/19/2013 5:50 AM, Gareth Poulton wrote: > > A customer wants us to move their entire enterprise platform - of which > one > > of the many components is Oracle Endeca - to open source. > > However, customers being the way they are, they don't want to have to > give > > up any of the features they currently use, the most prominent of which > are > > user friendly web-based editors for non-technical people to be able to > edit > > things like: > > - Schema > > - Dimensions (i.e. facets) > > - Dimension groups (not sure what these are) > > - Thesaurus > > - Stopwords > > - Report generation > > - Boosting individual records (i.e. sponsored links) > > - Relevance ranking settings > > - Process pipeline editor for, e.g. adding new languages > > -...all without touching any xml. > > I think Jack and Alexandre have pretty much covered what exists now for > Solr without paying someone for features and support - not much. There > is however some background work underway to bring features exactly like > this to Solr. Except for the Schema REST API that exists right now, I > don't think any of it has much priority. The priority is likely to > increase in the future, but probably not fast enough for your needs. > > There is a strong desire among the top Solr developers to have Solr > always be in SolrCloud mode in a future major version release -- which > means it would use Zookeeper to store all config information, just like > SolrCloud does now. > > When your config is in a separate network service instead of traditional > config files, the ability to edit the config using API calls is very > important. Creating a UI front-end that uses the API and doesn't > require editing XML would be EXTREMELY nice. I'm pretty sure that this > is the goal with the current work on the Schema REST API. > > If you have any idea how to bring these features to Solr, patches are > always welcome! > > Some of the things in your list, particularly facets and grouping (which > is what dimension groups might be equivalent to) are normally handled in > client code. The application creates the parameters it needs and > handles the response. With Solr they aren't normally configured on the > server side. You could do so, by putting parameters in request handler > definitions. > > Thanks, > Shawn > >
Re: Migrating from Endeca
On 9/19/2013 5:50 AM, Gareth Poulton wrote: > A customer wants us to move their entire enterprise platform - of which one > of the many components is Oracle Endeca - to open source. > However, customers being the way they are, they don't want to have to give > up any of the features they currently use, the most prominent of which are > user friendly web-based editors for non-technical people to be able to edit > things like: > - Schema > - Dimensions (i.e. facets) > - Dimension groups (not sure what these are) > - Thesaurus > - Stopwords > - Report generation > - Boosting individual records (i.e. sponsored links) > - Relevance ranking settings > - Process pipeline editor for, e.g. adding new languages > -...all without touching any xml. I think Jack and Alexandre have pretty much covered what exists now for Solr without paying someone for features and support - not much. There is however some background work underway to bring features exactly like this to Solr. Except for the Schema REST API that exists right now, I don't think any of it has much priority. The priority is likely to increase in the future, but probably not fast enough for your needs. There is a strong desire among the top Solr developers to have Solr always be in SolrCloud mode in a future major version release -- which means it would use Zookeeper to store all config information, just like SolrCloud does now. When your config is in a separate network service instead of traditional config files, the ability to edit the config using API calls is very important. Creating a UI front-end that uses the API and doesn't require editing XML would be EXTREMELY nice. I'm pretty sure that this is the goal with the current work on the Schema REST API. If you have any idea how to bring these features to Solr, patches are always welcome! Some of the things in your list, particularly facets and grouping (which is what dimension groups might be equivalent to) are normally handled in client code. The application creates the parameters it needs and handles the response. With Solr they aren't normally configured on the server side. You could do so, by putting parameters in request handler definitions. Thanks, Shawn
Re: Migrating from Endeca
I think Hue ( http://cloudera.github.io/hue/ ) which Cloudera uses for Solr search among other things has some of UI customization. And it is open-source, so would make for much better base. Regards, Alex. Personal website: http://www.outerthoughts.com/ LinkedIn: http://www.linkedin.com/in/alexandrerafalovitch - Time is the quality of nature that keeps events from happening all at once. Lately, it doesn't seem to be working. (Anonymous - via GTD book) On Thu, Sep 19, 2013 at 8:21 PM, Jack Krupansky wrote: > Take a look at LucidWorks Enterprise. It has a graphical UI. > > But if you must meet all of the listed requirements and Lucid doesn't meet > all of them, then... you will have to develop everything on your own. Or, > maybe Lucid might be interested in partnering with you to allow your to add > extensions to their UI. If you really are committed to a deep replacement > of Endeca's UI, then rolling your own is probably the way to go. Then the > question is whether you should open source that UI. > > You can also consider extending the Solr Admin UI. It does not do most of > your listed features, but having better integration with the Solr Admin UI > is a good idea. > > -- Jack Krupansky > > -Original Message- From: Gareth Poulton > Sent: Thursday, September 19, 2013 7:50 AM > To: solr-user@lucene.apache.org > Subject: Migrating from Endeca > > > Hi, > A customer wants us to move their entire enterprise platform - of which one > of the many components is Oracle Endeca - to open source. > However, customers being the way they are, they don't want to have to give > up any of the features they currently use, the most prominent of which are > user friendly web-based editors for non-technical people to be able to edit > things like: > - Schema > - Dimensions (i.e. facets) > - Dimension groups (not sure what these are) > - Thesaurus > - Stopwords > - Report generation > - Boosting individual records (i.e. sponsored links) > - Relevance ranking settings > - Process pipeline editor for, e.g. adding new languages > -...all without touching any xml. > > My question is, are there any solr features, plugins, modules, third party > applications, or the like that will do this for us? Or will we have to > develop all the above from scratch? > > thanks, > Gareth >
Re: Migrating from Endeca
Take a look at LucidWorks Enterprise. It has a graphical UI. But if you must meet all of the listed requirements and Lucid doesn't meet all of them, then... you will have to develop everything on your own. Or, maybe Lucid might be interested in partnering with you to allow your to add extensions to their UI. If you really are committed to a deep replacement of Endeca's UI, then rolling your own is probably the way to go. Then the question is whether you should open source that UI. You can also consider extending the Solr Admin UI. It does not do most of your listed features, but having better integration with the Solr Admin UI is a good idea. -- Jack Krupansky -Original Message- From: Gareth Poulton Sent: Thursday, September 19, 2013 7:50 AM To: solr-user@lucene.apache.org Subject: Migrating from Endeca Hi, A customer wants us to move their entire enterprise platform - of which one of the many components is Oracle Endeca - to open source. However, customers being the way they are, they don't want to have to give up any of the features they currently use, the most prominent of which are user friendly web-based editors for non-technical people to be able to edit things like: - Schema - Dimensions (i.e. facets) - Dimension groups (not sure what these are) - Thesaurus - Stopwords - Report generation - Boosting individual records (i.e. sponsored links) - Relevance ranking settings - Process pipeline editor for, e.g. adding new languages -...all without touching any xml. My question is, are there any solr features, plugins, modules, third party applications, or the like that will do this for us? Or will we have to develop all the above from scratch? thanks, Gareth
