Hi, we recently upgraded to DSpace 5.3, and have encountered a very disturbing problem. A large number of our collections are showing that they have no content (i.e. "no results for browse"). I believe I have eliminated misconfiguration as a cause: on our staging server (with a copy of the production metadata) I've reset the title browse configuration to the default settings for DSpace 5. On our production server, we've also disabled access rights awareness, and I thought that perhaps *that* change (which was done after our upgrade) might have been responsible for the "empty collections". However, re-enabling access rights awareness on our staging server still results in the same broken behavior.
Here's an example on our production server: First, visit this item: https://mospace.umsystem.edu/xmlui/handle/10355/11615 Now, click on the link for the parent collection on that item: "Evidence Based Practice, 2011 (MU)" and then click on the browse by title link. You'll see the "no results for this browse" message. That just can't be possible, can it? I've also looked at the metadata and can confirm that there are in fact links between the collection in question and items. This is a shot in the dark, but I thought I'd at least try: have you ever encountered anything like this? I'm looking for any suggestions for troubleshooting the Solr index (in case you're curious, there are no error messages in the dspace.log, and I've rebuilt this index so many times the past few days). Thanks! --Hardy -- 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 http://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
