Bram Luyten (@mire) created DS-1552:
---
Summary: luceneMatchVersion missing in oai and statistics solr
core configuration
Key: DS-1552
URL: https://jira.duraspace.org/browse/DS-1552
Project: DSpace
[
https://jira.duraspace.org/browse/DS-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bram Luyten (@mire) updated DS-1552:
Status: Accepted (was: Received)
luceneMatchVersion missing in oai and statistics solr core
[
https://jira.duraspace.org/browse/DS-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bram Luyten (@mire) updated DS-1552:
Assignee: Bram Luyten (@mire)
Status: Accepted (was: Volunteer Needed)
[
https://jira.duraspace.org/browse/DS-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bram Luyten (@mire) updated DS-1552:
Status: Volunteer Needed (was: Accepted)
Assignee: (was: Bram Luyten (@mire))
[
https://jira.duraspace.org/browse/DS-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Masár updated DS-1552:
---
Fix Version/s: 4.0
luceneMatchVersion missing in oai and statistics solr core configuration
[
https://jira.duraspace.org/browse/DS-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=28117#comment-28117
]
Bram Luyten (@mire) commented on DS-1552:
-
pull request:
[
https://jira.duraspace.org/browse/DS-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bram Luyten (@mire) updated DS-1552:
Status: Code Review Needed (was: Accepted)
luceneMatchVersion missing in oai and statistics
[
https://jira.duraspace.org/browse/DS-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=28118#comment-28118
]
Bram Luyten (@mire) commented on DS-1552:
-
Can someone with some more experience in stats oai
[
https://jira.duraspace.org/browse/DS-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=28119#comment-28119
]
João Melo commented on DS-1552:
---
For OAI seems fine.
luceneMatchVersion missing in oai
[
https://jira.duraspace.org/browse/DS-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Masár updated DS-1547:
---
Summary: Don't store user data if we can get them from external source when
needed (was: Don't store user data if
[
https://jira.duraspace.org/browse/DS-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Masár updated DS-1547:
---
Status: Volunteer Needed (was: Received)
Don't store user data if we can get them from external source when
We're currently struggling with a confusing browse error that is preventing us
from submissions being indexed in the browse index.
If anyone is familiar with this area of the code, I would most appreciate a
second set of eyes. (This is DSpace 1.8.)
We have Discovery turned off. Any help
On Mon, May 20, 2013 at 6:03 PM, Sands Alden Fish sa...@mit.edu wrote:
We have Discovery turned off. Any help or hints would be appreciated.
The table bi_2_dis does not seem to be specified anywhere in the
codebase.
Hi Sands,
the bi_2_dis table belongs to the second browse index
Ivan, thanks for the pointer.
This is one aspect of repo administration I've never had to deal with in the
past. It is possible that the previous tech lead on this project modified
those settings without re-running index-init.
I assume there's no issue with rerunning index-init as many times
I tried using our browse index today (http://scholar.sun.ac.za) to find all
titles with knowledge economy. It did not work as well as the advanced
search, which I assume is based on the solr discovery service. I am
thinking of removing the browse indexes. We have discovery, advanced search
and of
My metadata / technical librarian / repo admin loves the browse indices.
But, they're probably the only person. We keep adding additional fields,
probably so they can jump directly to items keyed with special metadata.
Peter Dietz
On Mon, May 20, 2013 at 2:22 PM, Hilton Gibson
No, you can't remove them yet. The browse aspect still depends on them.
That's the one that renders the /browse urls. Advanced search is handled by
Discovery if you enabled Discovery. The next step in Discovery development
is to make the discovery aspect render the browse indices, but that code
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
18 matches
Mail list logo
