Hi Shwetha, > I am using dspace1.4. I applied the patch for “ completely configurable > browse system” using myeclipse. > > http://sourceforge.net/tracker/index.php?func=detail&aid=1480998&group_id=19984&atid=319984 > > <http://sourceforge.net/tracker/index.php?func=detail&aid=1480998&group_id=19984&atid=319984> > > But I am not getting it to work. > > In the patch for dspace.cfg file we have the following indices > +webui.browse.index.1 = dateissued:dc.date.issued:date:full > +webui.browse.index.2 = author:dc.contributor.*:text:single > +webui.browse.index.3 = title:dc.title:title:full > +webui.browse.index.4 = subject:dc.subject.*:text:single > +webui.browse.index.5 = dateaccessioned:dc.date.accessioned:date:full > + > +# and an extra test one > +webui.browse.index.5 = type:dc.type:text:full:type > > But I think the last index has to be > > +webui.browse.index.6 = type:dc.type:text:full:type > > I am right?
Yes, you are right - sorry, that's an error in the example configuration. The rule is that the configured indices have to be numbered sequentially starting from 1 in an unbroken set of single increments. > Then I rebuilt the dspace. When I try to access the website, it is > giving exception in the BrowseIndex.java contructor. public > BrowseIndex(String definition, int number) This was the first draft of the browse patch, so it is definitely buggy (please do take good note of the caveats and issues that I posted on SourceForge, and I would strongly advise not using this patch in production yet). I am close to producing a much more stable patch (but the finishing point just keeps slipping back over the horizon!). I suspect that this is another error in the webui.browse.index.6, which should actually read: webui.browse.index.6 = type:dc.type:text:full (The final part of the config is there erroneously in the example, and the documentation - apologies; the <message key> part is now assumed to be the same as the <index name>, and thus the <message key> bit was dropped before I published this patch) > Please someone tell me Where did I do wrong? If that doesn't fix your problem, can you post the stack trace from dspace.log. I suspect you will find a "configuration invalid" error or something, though. Cheers, -- Richard ------------------------------------------------------------------------ Richard Jones | t: +44 (0)20 759 [48614 / 41815] Web & Database | e: [EMAIL PROTECTED] Technology Specialist | b: http://chronicles-of-richard.blogspot.com/ Imperial College London | ------------------------------------------------------------------------ ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
