We were at DSpace 5.5 (with XMLUI and Mirage2 and with ORCID enabled) and responded to the bug fixes in 5.6 and 5.7 by incorporating the security patches rather than doing a full upgrade to 5.6 and 5.7.
When 5.8 was released we decided to upgrade to 5.8, and everything is working fine for us except for the author browse with metadataAuthority. The authors of new items were not appearing in our author browse index although they are in the Solr discovery and authority cores. When we ran index-discovery -b and -o and index-authority, every author disappeared from the author browse and they have not been seen since. All our items appear in the other browses. We have a staging server, where we tried multiple attempts to reconfigure the browse index and adjust confidence values all to no avail. I've reviewed carefully the documentation on ORCID and authority configuration, all with no satisfaction. Not even going back to the default author browse that isn't based on the authority index works. Finally, taking the staging server back to our 5.5 code with 5.6 and 5.7 patches, we were able to bring back the author browse. Checking carefully I found that there were no significant differences in dspace.cfg between our staging server with the patched 5.5 code and our 5.8 production server. I've also been carefully through our log files for cocoon, dspace, and solr and can find nothing that would explain the difference between the author browse on our two servers. We are holding back from updgrading to DSpace 6 for two reasons. Our institution has adopted PURE and so far our information is that PURE works with DSpace 5 (REST API) but it is not known if it works with DSpace 6. In any case, our PURE project is not at the point of trying DSpace integration. The other reason for hesitating is seeing that people are still having various problems with adopting DSpace 6. At this point, I'm fairly certain there is a bug, but I can't be sure where it was introduced between 5.5 and 5.8, but I'm at a loss as to how to investigate further. Given our present knowledge, it would seem best to go back to our patched 5.5 rather than staying with 5.8. Does anyone have any suggestions about where we might look next? Is anyone else at 5.6, 5.7, or 5.8 using Mirage 2 and ORCID successfully? -- 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.
