The issue is caused by an out of date discovery index (this is why the
*-f*was used, this forces a complete re index).
As to why the discovery index was out of date in the first place, I would
check if you have the discovery consumer enabled in your dspace.cfg, more
information on how to do this can be found here:
https://wiki.duraspace.org/display/DSPACE/Discovery+Configuration
Kind regards,
Kevin Van de Velde
@mire
Esperantolaan 4 - 3001 Heverlee - Belgium
2888 Loker Avenue East, Suite 305 - Carlsbad, CA 92010 - USA
atmire.com - Institutional Repository Solutions
On 20 May 2011 17:04, James Bardin <jbar...@bu.edu> wrote:
> On Fri, May 20, 2011 at 10:41 AM, Kevin Van de velde <ke...@mire.be>
> wrote:
> > This is caused because the discovery index is out of date I would attempt
> to
> > run the following in your {dspace.dir}/bin
> >
> >> dspace update-discovery-index -f
> >
> > Hope this helps,
> >
>
> That was it, specifically the '-f' option (the index is updated
> normally via cron).
>
> Any idea as to what could cause this?
>
> Thanks!
>
>
>
> --
> James Bardin <jbar...@bu.edu>
> Systems Engineer
> Boston University IS&T
>
------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
