[Dspace-devel] [DuraSpace JIRA] (DS-1552) luceneMatchVersion missing in oai and statistics solr core configuration
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 Issue Type: Bug Components: OAI-PMH, Solr, Statistics Affects Versions: 3.1, 3.0 Reporter: Bram Luyten (@mire) Assignee: Bram Luyten (@mire) Attachments: lucene-error-messages.txt lucenematchversion is a mandatory config field in solrconfig.xml in Solr 4.0. It used to be optional. While it is defined for the search core, it seems missing in the stats and OAI core. As a result, it defaults to Lucene_24. e.g. WARNING: the luceneMatchVersion is not specified, defaulting to LUCENE_24 emulation. You should at some point declare and reindex to at least 3.0, because 2.4 emulation is deprecated and will be removed in 4.0. This parameter will be mandatory in 4.0. In attachment a logfile. Thanks to Ben Ryan for pointing me to the cause. Will issue a pull request for this soon. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1552) luceneMatchVersion missing in oai and statistics solr core configuration
[ 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 configuration Key: DS-1552 URL: https://jira.duraspace.org/browse/DS-1552 Project: DSpace Issue Type: Bug Components: OAI-PMH, Solr, Statistics Affects Versions: 3.0, 3.1 Reporter: Bram Luyten (@mire) Assignee: Bram Luyten (@mire) Attachments: lucene-error-messages.txt lucenematchversion is a mandatory config field in solrconfig.xml in Solr 4.0. It used to be optional. While it is defined for the search core, it seems missing in the stats and OAI core. As a result, it defaults to Lucene_24. e.g. WARNING: the luceneMatchVersion is not specified, defaulting to LUCENE_24 emulation. You should at some point declare and reindex to at least 3.0, because 2.4 emulation is deprecated and will be removed in 4.0. This parameter will be mandatory in 4.0. In attachment a logfile. Thanks to Ben Ryan for pointing me to the cause. Will issue a pull request for this soon. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1552) luceneMatchVersion missing in oai and statistics solr core configuration
[ 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) luceneMatchVersion missing in oai and statistics solr core configuration Key: DS-1552 URL: https://jira.duraspace.org/browse/DS-1552 Project: DSpace Issue Type: Bug Components: OAI-PMH, Solr, Statistics Affects Versions: 3.0, 3.1 Reporter: Bram Luyten (@mire) Assignee: Bram Luyten (@mire) Attachments: lucene-error-messages.txt lucenematchversion is a mandatory config field in solrconfig.xml in Solr 4.0. It used to be optional. While it is defined for the search core, it seems missing in the stats and OAI core. As a result, it defaults to Lucene_24. e.g. WARNING: the luceneMatchVersion is not specified, defaulting to LUCENE_24 emulation. You should at some point declare and reindex to at least 3.0, because 2.4 emulation is deprecated and will be removed in 4.0. This parameter will be mandatory in 4.0. In attachment a logfile. Thanks to Ben Ryan for pointing me to the cause. Will issue a pull request for this soon. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1552) luceneMatchVersion missing in oai and statistics solr core configuration
[ 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)) luceneMatchVersion missing in oai and statistics solr core configuration Key: DS-1552 URL: https://jira.duraspace.org/browse/DS-1552 Project: DSpace Issue Type: Bug Components: OAI-PMH, Solr, Statistics Affects Versions: 3.0, 3.1 Reporter: Bram Luyten (@mire) Attachments: lucene-error-messages.txt lucenematchversion is a mandatory config field in solrconfig.xml in Solr 4.0. It used to be optional. While it is defined for the search core, it seems missing in the stats and OAI core. As a result, it defaults to Lucene_24. e.g. WARNING: the luceneMatchVersion is not specified, defaulting to LUCENE_24 emulation. You should at some point declare and reindex to at least 3.0, because 2.4 emulation is deprecated and will be removed in 4.0. This parameter will be mandatory in 4.0. In attachment a logfile. Thanks to Ben Ryan for pointing me to the cause. Will issue a pull request for this soon. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1552) luceneMatchVersion missing in oai and statistics solr core configuration
[ 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 Key: DS-1552 URL: https://jira.duraspace.org/browse/DS-1552 Project: DSpace Issue Type: Bug Components: OAI-PMH, Solr, Statistics Affects Versions: 3.0, 3.1 Reporter: Bram Luyten (@mire) Assignee: Bram Luyten (@mire) Fix For: 4.0 Attachments: lucene-error-messages.txt lucenematchversion is a mandatory config field in solrconfig.xml in Solr 4.0. It used to be optional. While it is defined for the search core, it seems missing in the stats and OAI core. As a result, it defaults to Lucene_24. e.g. WARNING: the luceneMatchVersion is not specified, defaulting to LUCENE_24 emulation. You should at some point declare and reindex to at least 3.0, because 2.4 emulation is deprecated and will be removed in 4.0. This parameter will be mandatory in 4.0. In attachment a logfile. Thanks to Ben Ryan for pointing me to the cause. Will issue a pull request for this soon. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1552) 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://github.com/DSpace/DSpace/pull/220 luceneMatchVersion missing in oai and statistics solr core configuration Key: DS-1552 URL: https://jira.duraspace.org/browse/DS-1552 Project: DSpace Issue Type: Bug Components: OAI-PMH, Solr, Statistics Affects Versions: 3.0, 3.1 Reporter: Bram Luyten (@mire) Assignee: Bram Luyten (@mire) Fix For: 4.0 Attachments: lucene-error-messages.txt lucenematchversion is a mandatory config field in solrconfig.xml in Solr 4.0. It used to be optional. While it is defined for the search core, it seems missing in the stats and OAI core. As a result, it defaults to Lucene_24. e.g. WARNING: the luceneMatchVersion is not specified, defaulting to LUCENE_24 emulation. You should at some point declare and reindex to at least 3.0, because 2.4 emulation is deprecated and will be removed in 4.0. This parameter will be mandatory in 4.0. In attachment a logfile. Thanks to Ben Ryan for pointing me to the cause. Will issue a pull request for this soon. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1552) luceneMatchVersion missing in oai and statistics solr core configuration
[ 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 solr core configuration Key: DS-1552 URL: https://jira.duraspace.org/browse/DS-1552 Project: DSpace Issue Type: Bug Components: OAI-PMH, Solr, Statistics Affects Versions: 3.0, 3.1 Reporter: Bram Luyten (@mire) Assignee: Bram Luyten (@mire) Fix For: 4.0 Attachments: lucene-error-messages.txt lucenematchversion is a mandatory config field in solrconfig.xml in Solr 4.0. It used to be optional. While it is defined for the search core, it seems missing in the stats and OAI core. As a result, it defaults to Lucene_24. e.g. WARNING: the luceneMatchVersion is not specified, defaulting to LUCENE_24 emulation. You should at some point declare and reindex to at least 3.0, because 2.4 emulation is deprecated and will be removed in 4.0. This parameter will be mandatory in 4.0. In attachment a logfile. Thanks to Ben Ryan for pointing me to the cause. Will issue a pull request for this soon. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1552) 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=28118#comment-28118 ] Bram Luyten (@mire) commented on DS-1552: - Can someone with some more experience in stats oai confirm that this will have no negative consequences? luceneMatchVersion missing in oai and statistics solr core configuration Key: DS-1552 URL: https://jira.duraspace.org/browse/DS-1552 Project: DSpace Issue Type: Bug Components: OAI-PMH, Solr, Statistics Affects Versions: 3.0, 3.1 Reporter: Bram Luyten (@mire) Assignee: Bram Luyten (@mire) Fix For: 4.0 Attachments: lucene-error-messages.txt lucenematchversion is a mandatory config field in solrconfig.xml in Solr 4.0. It used to be optional. While it is defined for the search core, it seems missing in the stats and OAI core. As a result, it defaults to Lucene_24. e.g. WARNING: the luceneMatchVersion is not specified, defaulting to LUCENE_24 emulation. You should at some point declare and reindex to at least 3.0, because 2.4 emulation is deprecated and will be removed in 4.0. This parameter will be mandatory in 4.0. In attachment a logfile. Thanks to Ben Ryan for pointing me to the cause. Will issue a pull request for this soon. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1552) 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=28119#comment-28119 ] João Melo commented on DS-1552: --- For OAI seems fine. luceneMatchVersion missing in oai and statistics solr core configuration Key: DS-1552 URL: https://jira.duraspace.org/browse/DS-1552 Project: DSpace Issue Type: Bug Components: OAI-PMH, Solr, Statistics Affects Versions: 3.0, 3.1 Reporter: Bram Luyten (@mire) Assignee: Bram Luyten (@mire) Fix For: 4.0 Attachments: lucene-error-messages.txt lucenematchversion is a mandatory config field in solrconfig.xml in Solr 4.0. It used to be optional. While it is defined for the search core, it seems missing in the stats and OAI core. As a result, it defaults to Lucene_24. e.g. WARNING: the luceneMatchVersion is not specified, defaulting to LUCENE_24 emulation. You should at some point declare and reindex to at least 3.0, because 2.4 emulation is deprecated and will be removed in 4.0. This parameter will be mandatory in 4.0. In attachment a logfile. Thanks to Ben Ryan for pointing me to the cause. Will issue a pull request for this soon. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1547) Don't store user data if we can get them from external source when needed
[ 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 we can get them elsewhere at need) Don't store user data if we can get them from external source when needed - Key: DS-1547 URL: https://jira.duraspace.org/browse/DS-1547 Project: DSpace Issue Type: Improvement Reporter: Mark H. Wood Authentication providers like LDAP and Shibboleth can also be used as identity providers. But we just capture all that stuff and salt it away in our database, where it can go out of sync. with the authoritative data. We should split authentication and identity more effectively, and push provision of things like phone numbers and email into pluggable identity providers (which might be the same code as the authn providers). When you ask an EPerson for its phone number, it should see which identity provider it uses and call that to get its response. LDAP for example would then go look it up in the directory and hand that up the chain. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1547) Don't store user data if we can get them from external source when needed
[ 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 needed - Key: DS-1547 URL: https://jira.duraspace.org/browse/DS-1547 Project: DSpace Issue Type: Improvement Reporter: Mark H. Wood Authentication providers like LDAP and Shibboleth can also be used as identity providers. But we just capture all that stuff and salt it away in our database, where it can go out of sync. with the authoritative data. We should split authentication and identity more effectively, and push provision of things like phone numbers and email into pluggable identity providers (which might be the same code as the authn providers). When you ask an EPerson for its phone number, it should see which identity provider it uses and call that to get its response. LDAP for example would then go look it up in the directory and hand that up the chain. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] Bizarre DSpace Browse Failure
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 or hints would be appreciated. The table bi_2_dis does not seem to be specified anywhere in the codebase. - Sands Fish - MIT Libraries - sa...@mit.edu 2013-05-14 11:25:09,151 ERROR org.dspace.browse.BrowseCreateDAOPostgres @ caught exception: org.postgresql.util.PSQLException: ERROR: insert or update on table bi_2_dmap violates foreign key constraint bi_2_dmap_distinct_id_fkey Detail: Key (distinct_id)=(70465) is not present in table bi_2_dis. at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:1531) at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1313) at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:188) at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:452) at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:354) at org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc2Statement.java:258) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96) at org.dspace.storage.rdbms.DatabaseManager.doInsertPostgres(DatabaseManager.java:1755) at org.dspace.storage.rdbms.DatabaseManager.insert(DatabaseManager.java:675) at org.dspace.browse.BrowseCreateDAOPostgres.updateDistinctMappings(BrowseCreateDAOPostgres.java:277) at org.dspace.browse.IndexBrowse.indexItem(IndexBrowse.java:492) at org.dspace.browse.IndexBrowse.indexItem(IndexBrowse.java:321) at org.dspace.browse.BrowseConsumer.end(BrowseConsumer.java:126) at org.dspace.event.BasicDispatcher.dispatch(BasicDispatcher.java:149) at org.dspace.core.Context.commit(Context.java:336) at org.dspace.submit.step.CompleteStep.doProcessing(CompleteStep.java:110) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:155) at org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:243) at org.mozilla.javascript.Interpreter.interpretLoop(Interpreter.java:3237) at org.mozilla.javascript.Interpreter.interpret(Interpreter.java:2394) at org.mozilla.javascript.InterpretedFunction.call(InterpretedFunction.java:162) at org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:393) at org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:2834) at org.mozilla.javascript.InterpretedFunction.call(InterpretedFunction.java:160) at org.mozilla.javascript.Context.call(Context.java:538) at org.mozilla.javascript.ScriptableObject.callMethod(ScriptableObject.java:1833) at org.mozilla.javascript.ScriptableObject.callMethod(ScriptableObject.java:1803) at org.apache.cocoon.components.flow.javascript.fom.FOM_JavaScriptInterpreter.handleContinuation(FOM_JavaScriptInterpreter.java:698) at org.apache.cocoon.components.treeprocessor.sitemap.CallFunctionNode.invoke(CallFunctionNode.java:94) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:55) at org.apache.cocoon.components.treeprocessor.sitemap.MatchNode.invoke(MatchNode.java:87) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78) at org.apache.cocoon.components.treeprocessor.sitemap.SelectNode.invoke(SelectNode.java:82) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78) at org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:143) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78) at org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:81) at org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:239) at
Re: [Dspace-devel] Bizarre DSpace Browse Failure
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 (webui.browse.index.2) and has to be regenerated after changing that property. Those properties also have to be numbered sequentially with no gaps. I'm only pointing that out because you tried to look it up in the codebase, while it's in fact generated by index-init. I assume you have tried running index-init, have you? Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
Re: [Dspace-devel] Bizarre DSpace Browse Failure
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 as needed? Do you have to rebuild the indexes after re-running that, or is that just taken care of as part of the process? -Sands P.S. - hg, thanks for the link, it's useful to see your process written out. From: ivan.ma...@gmail.com [ivan.ma...@gmail.com] on behalf of helix84 [heli...@centrum.sk] Sent: Monday, May 20, 2013 12:11 PM To: Sands Alden Fish Cc: dspace-devel@lists.sourceforge.net Subject: Re: [Dspace-devel] Bizarre DSpace Browse Failure On Mon, May 20, 2013 at 6:03 PM, Sands Alden Fish sa...@mit.edumailto: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 (webui.browse.index.2) and has to be regenerated after changing that property. Those properties also have to be numbered sequentially with no gaps. I'm only pointing that out because you tried to look it up in the codebase, while it's in fact generated by index-init. I assume you have tried running index-init, have you? Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
Re: [Dspace-devel] Bizarre DSpace Browse Failure
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 course google scholar to do searches with. Are the browse indexes useful and accurate? Comments on the list welcome, I am sitting undecided, on the fence, with this one. Cheers hg On 20 May 2013 19:02, Sands Alden Fish sa...@mit.edu wrote: 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 as needed? Do you have to rebuild the indexes after re-running that, or is that just taken care of as part of the process? -Sands P.S. - hg, thanks for the link, it's useful to see your process written out. -- *From:* ivan.ma...@gmail.com [ivan.ma...@gmail.com] on behalf of helix84 [ heli...@centrum.sk] *Sent:* Monday, May 20, 2013 12:11 PM *To:* Sands Alden Fish *Cc:* dspace-devel@lists.sourceforge.net *Subject:* Re: [Dspace-devel] Bizarre DSpace Browse Failure 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 (webui.browse.index.2) and has to be regenerated after changing that property. Those properties also have to be numbered sequentially with no gaps. I'm only pointing that out because you tried to look it up in the codebase, while it's in fact generated by index-init. I assume you have tried running index-init, have you? Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel -- *Hilton Gibson* Systems Administrator JS Gericke Library Room 1025C Stellenbosch University Private Bag X5036 Stellenbosch 7599 South Africa Tel: +27 21 808 4100 | Cell: +27 84 646 4758 http://library.sun.ac.za http://scholar.sun.ac.za http://ar1.sun.ac.za http://aj1.sun.ac.za -- AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
Re: [Dspace-devel] Bizarre DSpace Browse Failure
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 hilton.gib...@gmail.comwrote: 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 course google scholar to do searches with. Are the browse indexes useful and accurate? Comments on the list welcome, I am sitting undecided, on the fence, with this one. Cheers hg On 20 May 2013 19:02, Sands Alden Fish sa...@mit.edu wrote: 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 as needed? Do you have to rebuild the indexes after re-running that, or is that just taken care of as part of the process? -Sands P.S. - hg, thanks for the link, it's useful to see your process written out. -- *From:* ivan.ma...@gmail.com [ivan.ma...@gmail.com] on behalf of helix84 [heli...@centrum.sk] *Sent:* Monday, May 20, 2013 12:11 PM *To:* Sands Alden Fish *Cc:* dspace-devel@lists.sourceforge.net *Subject:* Re: [Dspace-devel] Bizarre DSpace Browse Failure On Mon, May 20, 2013 at 6:03 PM, Sands Alden Fish sa...@mit.eduwrote: 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 (webui.browse.index.2) and has to be regenerated after changing that property. Those properties also have to be numbered sequentially with no gaps. I'm only pointing that out because you tried to look it up in the codebase, while it's in fact generated by index-init. I assume you have tried running index-init, have you? Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel -- *Hilton Gibson* Systems Administrator JS Gericke Library Room 1025C Stellenbosch University Private Bag X5036 Stellenbosch 7599 South Africa Tel: +27 21 808 4100 | Cell: +27 84 646 4758 http://library.sun.ac.za http://scholar.sun.ac.za http://ar1.sun.ac.za http://aj1.sun.ac.za -- AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel -- AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
Re: [Dspace-devel] Bizarre DSpace Browse Failure
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 doesn't exist yet for XMLUI (only for jspui and it's not enabled by default). On May 20, 2013 8:22 PM, Hilton Gibson hilton.gib...@gmail.com wrote: 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 course google scholar to do searches with. Are the browse indexes useful and accurate? Comments on the list welcome, I am sitting undecided, on the fence, with this one. Cheers hg On 20 May 2013 19:02, Sands Alden Fish sa...@mit.edu wrote: 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 as needed? Do you have to rebuild the indexes after re-running that, or is that just taken care of as part of the process? -Sands P.S. - hg, thanks for the link, it's useful to see your process written out. -- *From:* ivan.ma...@gmail.com [ivan.ma...@gmail.com] on behalf of helix84 [heli...@centrum.sk] *Sent:* Monday, May 20, 2013 12:11 PM *To:* Sands Alden Fish *Cc:* dspace-devel@lists.sourceforge.net *Subject:* Re: [Dspace-devel] Bizarre DSpace Browse Failure On Mon, May 20, 2013 at 6:03 PM, Sands Alden Fish sa...@mit.eduwrote: 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 (webui.browse.index.2) and has to be regenerated after changing that property. Those properties also have to be numbered sequentially with no gaps. I'm only pointing that out because you tried to look it up in the codebase, while it's in fact generated by index-init. I assume you have tried running index-init, have you? Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel -- *Hilton Gibson* Systems Administrator JS Gericke Library Room 1025C Stellenbosch University Private Bag X5036 Stellenbosch 7599 South Africa Tel: +27 21 808 4100 | Cell: +27 84 646 4758 http://library.sun.ac.za http://scholar.sun.ac.za http://ar1.sun.ac.za http://aj1.sun.ac.za -- AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] R: Re: Bizarre DSpace Browse Failure
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 Inviato da Tablet Samsunghelix84 heli...@centrum.sk ha scritto: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 doesn't exist yet for XMLUI (only for jspui and it's not enabled by default). On May 20, 2013 8:22 PM, Hilton Gibson hilton.gib...@gmail.com wrote: 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 course google scholar to do searches with. Are the browse indexes useful and accurate? Comments on the list welcome, I am sitting undecided, on the fence, with this one. Cheers hg On 20 May 2013 19:02, Sands Alden Fish sa...@mit.edu wrote: 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 as needed? Do you have to rebuild the indexes after re-running that, or is that just taken care of as part of the process? -Sands P.S. - hg, thanks for the link, it's useful to see your process written out. From: ivan.ma...@gmail.com [ivan.ma...@gmail.com] on behalf of helix84 [heli...@centrum.sk] Sent: Monday, May 20, 2013 12:11 PM To: Sands Alden Fish Cc: dspace-devel@lists.sourceforge.net Subject: Re: [Dspace-devel] Bizarre DSpace Browse Failure 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 (webui.browse.index.2) and has to be regenerated after changing that property. Those properties also have to be numbered sequentially with no gaps. I'm only pointing that out because you tried to look it up in the codebase, while it's in fact generated by index-init. I assume you have tried running index-init, have you? Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel -- Hilton Gibson Systems Administrator JS Gericke Library Room 1025C Stellenbosch University Private Bag X5036 Stellenbosch 7599 South Africa Tel: +27 21 808 4100 | Cell: +27 84 646 4758 http://library.sun.ac.za http://scholar.sun.ac.za http://ar1.sun.ac.za http://aj1.sun.ac.za-- AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
