Dear Thomas,
Have you resolved this issue? I'm having the same error after I upgrade from
version 1.7.0 to 1.7.1. After I run update-discovery-index, I got the same
error.
Hoping for a positive response and thanks in advance.
--
Elvi S. Nemiz
Information Assistant
Library and Data Bank
Have you been able to make any progress on this?
Ralph
From: LeVan,Ralph
Sent: Thursday, March 24, 2011 4:42 PM
To: Kocisky
Cc: dspace-tech@lists.sourceforge.net
Subject: RE: [Dspace-tech] SRW Dspace 1.7 Cannot get a connection
pool(resultSetTTL)
With the resultSetTTL set to zero, how
Hi Bojan,
Thanks for getting back to me on this. I was having an issue whereby I
was loosing the connection to the DB through the context. In
investigating this I found the problem was the calling of
context.complete() in the ItemEntity constructor as the context.complete
nulls the connection
We would like to make the results of the search be based on the user logged in
the system. For example,
Person: John Smith, with item: The works of John Smith
Has sole rights to the item (metadata and bitstream )
So if an anonymous user is using the system and he searches for 'The works of
XMLUI Mirage is not honoring the registration setting in dspace.cfg
xmlui.user.registration = false
I still have the Register link on Mirage login page.
Where / how can I file this as a bug? Is there a dsapce Jira somewhere?
--
thanks
kevin.foote
Hi Kevin,
DSpace JIRA is at:
https://jira.duraspace.org/browse/DS
It looks like this particular bug was just filed today :
https://jira.duraspace.org/browse/DS-863
If you have any additional comments to add, feel free to add them to
that issue. It would be worth determining whether this bug
Hi Jose,
This actually sounds like a fun project to solve with Discovery, they look
like a good match.
Regarding the traditional lucene search index, my understanding is that the
lucene index is there to provide fast query on the data. In your case you
want to restrict what gets returned to the
Thank you! I was thinking that filtering out from the results page would be an
approach I could take. We are still discussing this, perhaps just not giving
access to the item will be good enough.
From: Peter Dietz [mailto:pdiet...@gmail.com]
Sent: Tuesday, March 29, 2011 2:37 PM
To: Blanco,
Thanks a lot for your attention, helix84.
But both the front and community pages exhibit what's inside the otherwise
condition.
On the front page we have no definition of URI:
metadata element=request qualifier=URI/
And on the communities page we have
metadata element=request
Post the error again, we will review it.
Regards,
Mark
On Tue, Mar 29, 2011 at 7:55 AM, Nemiz, Elvi S. esne...@seafdec.org.phwrote:
Dear Thomas,
Have you resolved this issue? I'm having the same error after I upgrade
from
version 1.7.0 to 1.7.1. After I run update-discovery-index, I got
Calling all students, Google Summer of Code 2011 Applications are due by
April 8!
(Professors, please share this with your students! Librarians, please
forward to both professors and students!)
YOU CAN EARN $5,000 FOR A BIT OF SUMMER CODING!?!
That's right! Apply for Google Summer of Code and
I found the full thread in context at:
http://www.mail-archive.com/dspace-tech@lists.sourceforge.net/msg12914.html
Something got chopped on his latest post.
Peter Dietz
On Tue, Mar 29, 2011 at 4:57 PM, Mark Diggory mdigg...@atmire.com wrote:
Post the error again, we will review it.
Dear Mark,
This is the error when I run update-discovery-index.
E:\DSpace\bindspace update-discovery-index
Using DSpace installation in: E:\DSpace
Exception: Error executing query
org.dspace.discovery.SearchServiceException: Error executing query
at
You will want to verify your solr server is running and that searches are
possible.
http://yourhost:yourport/solr/search/select?q=*:*
This is a query to return all the contents of the solr index. If you are
not able to run this request successfully from the same server as DSpace is
running on,
14 matches
Mail list logo
