On Friday, January 11, 2019 at 4:53:04 AM UTC-5, Wenz, Armin wrote: > > for testing purposes I cloned my postgres DB (create database .. from > template ..) right after a fresh install and creating admin-users and > empty collections (no items inserted). > > After testing a few imports I shut down the whole application, moved the > testing DB out of the way, cloned my template DB again and started DSpace > with the newly cloned DB again. > > Everything works fine, my epersons and empty collections where there. But > still the facettes from the old DB are displayed even when all collections > are empty. Of course, when clicking on the facette links, there is no data > shown. > > Another strange behaviour occured when importing items into the new > DB/Application: The amount of items shown in the item list is the sum from > the old imports and the new imports and I can click on 'next' as long as > there are new imports. > > So I guess this data is cached somewhere. Can anybody tell me where or > how I can get rid of that data? > >
The reason for this strange behavior is that search and Discovery information is cached in Solr. Solr still holds records for the test items that you created in the testing DB. As Claudia wrote, you need to empty and rebuild the Discovery index to make it consistent with the new DB. -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- 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.
