Hi Bhavesh, It looks like you have dc.contributor.author metadata values for which the authority column has a value. But your dspace.cfg file doesn't contain any valid authority configuration for dc.contributor.author.
That means you have two options: 1. *Configure authority control for dc.contributor.author*: To do this, you have to uncomment the following section https://github.com/DSpace/DSpace/blob/dspace-6.0/dspace/config/dspace.cfg#L1473 2. *OR ignore authorities for the browse index: *Add these lines to config/modules/discovery.cfg discovery.browse.authority.ignore-prefered.author = true discovery.browse.authority.ignore-variants.author = true That should make that error disappear and index all items. [image: logo] Tom Desair 250-B Suite 3A, Lucius Gordon Drive, West Henrietta, NY 14586 Gaston Geenslaan 14, Leuven 3001, Belgium www.atmire.com <http://atmire.com/website/?q=services&utm_source=emailfooter&utm_medium=email&utm_campaign=tomdesair> 2017-05-03 15:54 GMT+02:00 Bhavesh Patel <bhavesh.bece...@gmail.com>: > Dear Tom Desair, > > We have followed the instruction as per your reply, index command was > successfully executed, but the count remain same. > > we see into dspace.log file (dspace.log.2017-05-03), it's around 26 MB, so > I have taken some of the lines (that is having error while executing the > command) into attached .txt file > > It's give error like: *"ERROR org.dspace.discovery.SolrServiceImpl @ No > choices plugin was configured for field "dc_contributor_author".* > *java.lang.IllegalArgumentException: No choices plugin was configured for > field "dc_contributor_author"."* > > what may be the issue? it's not recognize the author field? > > Thanks > Bhavesh > > > > Thanks & Regards, > *Bhavesh R. Patel* > > *"Learning is a never ending process"* > > > On Wed, May 3, 2017 at 5:18 PM, Tom Desair <tom.des...@atmire.com> wrote: > >> DSpace 6.0 has some known memory issue so it might be that the indexing >> process is stopped before it could complete. These will be fixed in DSpace >> 6.1. >> >> For now, can you try this: >> >>> $ export JAVA_OPTS="-Xmx4G -Dfile.encoding=UTF-8" >>> $ bin/dspace index-discovery -bf >> >> >> Do you see any errors in the dspace.log file when running "dspace >> index-discovery -bf" or when it completes? >> >> >> [image: logo] Tom Desair >> 250-B Suite 3A, Lucius Gordon Drive, West Henrietta, NY 14586 >> Gaston Geenslaan 14, Leuven 3001, Belgium >> www.atmire.com >> <http://atmire.com/website/?q=services&utm_source=emailfooter&utm_medium=email&utm_campaign=tomdesair> >> >> 2017-05-03 13:36 GMT+02:00 Bhavesh Patel <bhavesh.bece...@gmail.com>: >> >>> Dear Tom Desair, >>> >>> Both counts are different, >>> >>> SQL Query in database: 18072 >>> >>> Through Solr: 17058 >>> >>> Through Solr: >>> ----------------------- >>> >>> { >>> "responseHeader":{ >>> "status":0, >>> "QTime":1, >>> "params":{ >>> "q":"search.resourcetype:2", >>> "indent":"true", >>> "rows":"0", >>> "wt":"json"}}, >>> "response":{"numFound":17058,"start":0,"docs":[] >>> }} >>> ------------------- >>> >>> >>> >>> Thanks & Regards, >>> *Bhavesh R. Patel* >>> >>> *"Learning is a never ending process"* >>> >>> >>> On Wed, May 3, 2017 at 4:52 PM, Tom Desair <tom.des...@atmire.com> >>> wrote: >>> >>>> Hi Bhavesh, >>>> >>>> To check the number of items in the database that need to be indexed, >>>> execute: >>>> >>>>> select count(*) from item where in_archive = true or withdrawn = true; >>>> >>>> >>>> Then compare this to the number of items that are in the discovery >>>> index: >>>> >>>>> curl "http://localhost:8080/solr/search/select?q=search.resourcet >>>>> ype%3A2&rows=0&wt=json&indent=true" >>>> >>>> (check the value after "numFound") >>>> >>>> Are the counts different? >>>> >>>> >>>> [image: logo] Tom Desair >>>> 250-B Suite 3A, Lucius Gordon Drive, West Henrietta, NY 14586 >>>> Gaston Geenslaan 14, Leuven 3001, Belgium >>>> www.atmire.com >>>> <http://atmire.com/website/?q=services&utm_source=emailfooter&utm_medium=email&utm_campaign=tomdesair> >>>> >>>> >>>> 2017-05-03 13:12 GMT+02:00 Bhavesh Patel <bhavesh.bece...@gmail.com>: >>>> >>>>> Thanks for your reply, we did it as per your suggestion but there is >>>>> no change in number. >>>>> >>>>> We have cross checked in database (postgresql), in table: >>>>> *metadatavalue* we set the condition with itemtype and count, it >>>>> shows the perfect number of records but it when we index, it doesn't show >>>>> all the title, we don't know what is missing as some of the most recent >>>>> submissions are there. >>>>> >>>>> Can you please suggest *how to find collection wise list and count >>>>> through query in DSpace 6?* >>>>> >>>>> what is the possible reason for not indexing all the items?, please >>>>> help us. >>>>> >>>>> Thanks & regards, >>>>> Bhavesh >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> Thanks & regards, >>>>> Bhavesh >>>>> >>>>> >>>>> Thanks & Regards, >>>>> *Bhavesh R. Patel* >>>>> >>>>> *"Learning is a never ending process"* >>>>> >>>>> >>>>> On Tue, May 2, 2017 at 9:15 AM, Tran Huu Trung (TTTV.ICT) < >>>>> trun...@hpu.edu.vn> wrote: >>>>> >>>>>> Please check anonymous authorization of these data and try >>>>>> index-discovery -b -f >>>>>> >>>>>> Vào 20:48:48 UTC+7 Thứ Hai, ngày 01 tháng 5 năm 2017, Bhavesh Patel >>>>>> đã viết: >>>>>>> >>>>>>> Dear all, >>>>>>> >>>>>>> we have upgraded DSpace 5 to DSpace 6, we have imported the database >>>>>>> and assesstore but when we run index-discovery it will not list all the >>>>>>> records, it will hide some records even we got the data that we have >>>>>>> entered latest one but some older data still not indexed. >>>>>>> >>>>>>> what may be the issue? what is the proper steps to run full index? >>>>>>> >>>>>>> OS: CentOS 7 >>>>>>> DSpace: 6 >>>>>>> >>>>>>> Thanks & Regards, >>>>>>> *Bhavesh R. Patel* >>>>>>> >>>>>>> *"Learning is a never ending process"* >>>>>>> >>>>>>> -- >>>>>> You received this message because you are subscribed to the Google >>>>>> Groups "DSpace Technical Support" group. >>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>> send an email to dspace-tech+unsubscr...@googlegroups.com. >>>>>> To post to this group, send email to dspace-tech@googlegroups.com. >>>>>> Visit this group at https://groups.google.com/group/dspace-tech. >>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>> >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "DSpace Technical Support" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to dspace-tech+unsubscr...@googlegroups.com. >>>>> To post to this group, send email to dspace-tech@googlegroups.com. >>>>> Visit this group at https://groups.google.com/group/dspace-tech. >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> >>> >> > -- > You received this message because you are subscribed to the Google Groups > "DSpace Technical Support" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to dspace-tech+unsubscr...@googlegroups.com. > To post to this group, send email to dspace-tech@googlegroups.com. > Visit this group at https://groups.google.com/group/dspace-tech. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech+unsubscr...@googlegroups.com. To post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
