<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Courier New";}
span.value
{mso-style-name:value;}
span.attribute
{mso-style-name:attribute;}
span.string
{mso-style-name:string;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">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.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">"id": "/repositories/3/archival_objects/4572#pui" <o:p></o:p></p>
<p class="MsoNormal">"id": "/repositories/3/archival_objects/4572"<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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)<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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 *<b>no</b>* 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?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Rachel Maderik<o:p></o:p></p>
<p class="MsoNormal">Systems and Technology Librarian<o:p></o:p></p>
<p class="MsoNormal">501D Preston Library<o:p></o:p></p>
<p class="MsoNormal">Virginia Military Institute<o:p></o:p></p>
<p class="MsoNormal">Lexington, VA 24450<o:p></o:p></p>
<p class="MsoNormal">540-464-7572<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>