Hi Chris, First, I'd recommend checking the logs to ensure no errors are being thrown behind the scenes: https://wiki.duraspace.org/display/DSPACE/Troubleshoot+an+error
If there are no obvious errors in DSpace or Tomcat logs (especially related to Solr or browse indexing), then you should also double check your Browse index configurations (in dspace.cfg). Maybe they are misconfigured (or you are using outdated configurations)? https://wiki.duraspace.org/display/DSDOC5x/Configuration+Reference#ConfigurationReference-BrowseIndexConfiguration My suspicion here is this sounds like either Solr isn't responding properly *or* something is misconfigured in your dspace.cfg (or similar config files). Since you mentioned a staging server (and presumably it is showing the same behavior), you could consider reverting the staging server's configuration to default DSpace settings (and see if you can zero in on which setting is causing the odd behavior -- and maybe that'd give us more information to test against and determine if a bug exists). - Tim On Wed, Oct 11, 2017 at 2:01 PM Chris Gray <[email protected]> wrote: > After upgrading to DSpace 5.8, added items no longer appear in the browse > by author. Existing items were there but not new items. If an author with > a specific item was in DSpace before the upgrade, after the upgrade the > browse by author only showed the older item not the new item. The > underlying unique id for that author is present for both items. Both items > are in the 'search' Solr core and the author is in the 'authority' core. > Everything is findable by a search and by all the other browse functions, > just not author browse. > > We have implemented ORCID functionality and our author browse was working > before the upgrade to 5.8. We set the author browse to use > metadataAuthority instead of metadata, and it was working before the > upgrade. We've reverted our staging server to before the 5.8 upgrade and > the author browse is working fine. > > We tried to fix the production server by having the discovery index > rebuilt from scratch (-b option to index-discovery). This removed > everything from the author browse. This suggests that items are added to > the discovery index in such a way that they are not accessed by the author > browse anymore. > > It seems that there is some problem with the way items are added to the > discovery index and how the XMLUI browse function accesses the Solr core. > We are using XMLUI with Mirage2. > > Does anyone have any idea where we should look for the problem? How to > diagnose it? > > -- > 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 [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/dspace-tech. > For more options, visit https://groups.google.com/d/optout. > -- Tim Donohue Technical Lead for DSpace & DSpaceDirect DuraSpace.org | DSpace.org | DSpaceDirect.org -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
