On Tue, May 21, 2013 at 5:24 PM, Sands Alden Fish wrote:
> Just to follow up on this, rerunning index-init did resolve the Browse
> errors I was seeing.
I wish all the questions on the lists would be so easily resolved ;)
Anyway, this turned out to be quite an informative thread. Thanks, everyon
Just to follow up on this, rerunning index-init did resolve the Browse errors I
was seeing.
-S
--
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring serv
Not really meant as overall arguments against browse, just pointing out
two current issues with Browse:
pagination counts incorrect: https://jira.duraspace.org/browse/DS-954
I'm not sure what is going on there, but a couple of things immediately
leap out:
1) The sort_value should be unique
Not really meant as overall arguments against browse, just pointing out two
current issues with Browse:
pagination counts incorrect: https://jira.duraspace.org/browse/DS-954
Browsing by year/issue date has some confusing elements as well:
https://jira.duraspace.org/browse/DS-1213
>From a user ex
Not really. The SOLRBrowseDAO works for both jspui than xmlui.
You don't need a custom aspect because it implements exactly the same API than
the DBMS browse dao, in fact you need to set it as the browsedao plugin
implementation.
As helix says it is not enabled by default in 3.x
Andrea
Inviat
