Oh, sure, sorry, the basics: DSpace 1.7.1 (manually patched to be compatible with 1.7.2), Discovery is not yet turned on. We *are* using Oracle on the back end.
So, I'm thinking since we use /xmlui in our URL (we don't use the ROOT webapp) that we need to craft our OpenSearch URLs a bit differently than is documented. I'll keep poking around and see what I can find. -- HARDY POTTINGER <pottinge...@umsystem.edu> University of Missouri Library Systems http://lso.umsystem.edu/~pottingerhj/ https://MOspace.umsystem.edu/ "Don't undertake a project unless it is manifestly important and nearly impossible." --Edwin Land On 9/10/12 5:21 PM, "helix84" <heli...@centrum.sk> wrote: >On Mon, Sep 10, 2012 at 11:57 PM, Pottinger, Hardy J. ><pottinge...@umsystem.edu> wrote: >> Hi, I have never tinkered with OpenSearch until today, and I am trying >>to >> set it up on our staging server, but I think I am missing something key. >> It appears that myrepositoryurl/opensearch should point to an existing >>UI, >> so, I am thinking I need to specify another reverse proxy in Apache... >>Or >> am I missing something? > >Hi Hardy, > >can you first check what DSpace version you're trying this on, maybe >you're running into this bug (present in 1.7 and 1.8, fixed in >master): >https://jira.duraspace.org/browse/DS-1244 > >Regards, >~~helix84 ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
