[Archivesspace_Users_Group] problems with public site indexing in 2.0

[Laney McGlohon]

Hey Rachel,

I talked with HM about this issue and we believe it is a bug. If you would like to follow the progress, I opened a ticket for them to work on: https://archivesspace.atlassian.net/browse/ANW-136. It should be fixed for the 2.1.0 release.

Best,
Laney

Laney McGlohon
ArchivesSpace Tech Lead
laney.mcglohon at lyrasis.org<mailto:laney.mcglohon at lyrasis.org>
800.999.8558 x2927
laneymcglohon Skype



From: <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of "Maderik, Rachel A" <maderikra at vmi.edu>
Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Date: Friday, May 26, 2017 at 10:52 AM
To: "'archivesspace_users_group at lyralists.lyrasis.org'" <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] problems with public site indexing in 2.0

We’ve noticed that since upgrading to 2.0, we’ve been having problems with components not showing up in the search results on our public site. In some cases, new components take several days to be searchable on the public site (even though they are searchable in the staff side immediately), and there are also instances of old components (ones that have existed for years) never showing up at all, even after rebuilding the index.

Whatever is happening seems to be related to the new PUI indexer.  When searching the Solr index directly, the components that do show up in the public results have two Solr entries with identical IDs, except one is appended with “#pui”. E.g.

"id": "/repositories/3/archival_objects/4572#pui"
"id": "/repositories/3/archival_objects/4572"

The components that aren’t showing up only have a single entry in the index without the #pui addition. They also lack a “pui” designation in the types field, which all other records seem to have now. (screenshots attached)

I tried disabling the PUI indexing in config.rb (by setting AppConfig[:pui_indexer_enabled] to false), since we’re not actually using the PUI yet, but that resulted in *no* components being searchable on the public site at all (though other record types showed up). Is there some other config.rb setting I need to change in order to use 2.0 without the PUI? Or, is there a reason that the PUI indexer is not properly indexing all components?

Rachel Maderik
Systems and Technology Librarian
501D Preston Library
Virginia Military Institute
Lexington, VA 24450
540-464-7572

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170531/7a6b5b5c/attachment.html>