On Mon, Jun 17, 2013 at 4:01 PM, helix84 <heli...@centrum.sk> wrote: > On Mon, Jun 17, 2013 at 3:38 PM, Terry Brady <tw...@georgetown.edu> wrote: >> Would it be sufficient to run index-update rather than index-init after >> updating the community2collection table? > > Hi Terry, > > I don't think you need to update the Lucene index at all, because you > didn't actually change any item metadata. But I'm not 100% sure.
I think I was wrong. I looked at the index structure and there's a "location" field that specifies the parent. I don't see an option to reindex existing items like Discovery has (see below), so you might have to either run index-init or specify the updated items using the -i option to index-update. You can use a tool like Luke to look at the index (located in [dspace]/search) and check whether the "location" field is updated on a particular affected item when you run just index-update. > If you're using Discovery, then you do need to run > update-discovery-index - the Solr index used by Discovery does store > relations. Running just update-discovery-index actually doesn't reindex existing items. When you do an external change that DSpace is not aware of, like using SQL in this case, you may need to also reindex all existing items. To do that, run "update-discovery-index -f". Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
