<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)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Arial",sans-serif;
color:#1F497D;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Arial",sans-serif;
color:#1F497D;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1F497D">One more detail about this issue – in the public interface, the untitled archival objects don’t display in the component tree along the right side of the page,
just like they don’t in the staff interface. But if I click on their parent, they do display in the full display that appears in the center of the page, directly under the “Collection Organization” tab.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1F497D">So in the example below, the sub-series “962-1966 Thunderclaps (programs, music)” is clicked open in the component structure on the right hand side, but no archival
objects are shown beneath it. However, if the detailed view in the middle of the page, there are 5 archival objects displayed as children of the sub-series, including the culprit at the very bottom, which has no title, but is dated 1966.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1F497D"><img width="1062" height="614" id="Picture_x0020_1" src="cid:image001.jpg@01D31D90.16C4D1D0"></span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1F497D">Karen<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Karen Miller <br>
<b>Sent:</b> Friday, August 25, 2017 10:19 AM<br>
<b>To:</b> Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org><br>
<b>Subject:</b> RE: [Archivesspace_Users_Group] Error when searching in archivesspace v2.1.1<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1F497D">Hi, all.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1F497D">We’re having a different problem with archival objects that lack a Title (but include a Date sub-record) not showing up at all in the staff interface. In addition,
any siblings (and in some cases cousins as well) do not show up. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1F497D">For example, on our public v1.5 site, the Gwendolen M. Carter papers finding aid has three sub-series (General Correspondence, Letters of Recommendation, and Subject
Files) under the second series (Administrative Files):<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1F497D"><a href="https://findingaids.library.northwestern.edu/repositories/6/resources/18#components">https://findingaids.library.northwestern.edu/repositories/6/resources/18#components</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1F497D">If you open the sub-series, you can see that the first two have archival object children that have Dates, but no Titles. The third sub-series (Subject Files) has
archival objects with both Titles and Dates. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1F497D">In the v2.1.1 Staff interface, the Administrative Files series shows up, but it has no children. They are present in the MySQL tables and their contents show up
in the Container Inventory on the public interface. I added several components under the Administrative Files series in the staff interface and they saved, but they did not show up.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1F497D">I found that any archival object that is added with a Date but no Title will save but not show up in a Resource component tree. In addition, if I save an archival
object without a Title and use the +1 button to create a sibling, neither of them display in the component tree.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1F497D">I have not tried RDE to see if that functions differently, but this seems like a pretty big issue as it is. It’s not a data issue, it’s a display issue – so maybe
it will be straightforward to fix? <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1F497D">Karen<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#272323"><o:p> </o:p></span></b></p>
<p class="MsoNormal" style="text-autospace:none"><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#272323">Karen D. Miller<o:p></o:p></span></b></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Monographic Cataloger/Metadata Specialist<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#272323">Northwestern University Libraries<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#4E2A85">Northwestern University<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">1970 Campus Drive<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Evanston, IL 60208<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#272323"><a href="http://www.library.northwestern.edu">www.library.northwestern.edu</a><o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><a href="mailto:k-miller3@northwestern.edu">k-miller3@northwestern.edu</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#272323">874.467.3462</span><span style="font-size:10.0pt;color:#1F497D"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> <a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">
archivesspace_users_group-bounces@lyralists.lyrasis.org</a> [<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org</a>]
<b>On Behalf Of </b>Harmeyer, Neal A<br>
<b>Sent:</b> Wednesday, August 23, 2017 12:18 PM<br>
<b>To:</b> Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@lyralists.lyrasis.org</a>><br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] Error when searching in archivesspace v2.1.1<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoPlainText"><span style="color:#1F4E79">Hi Lance,<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:#1F4E79"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="color:#1F4E79">We've experienced this issue as well, in search results after the move to 2.1. We recently finished some testing on it. Our findings suggest this is directly related to archival objects that possess a date
subrecord but no title. For these records, a search in the new public interface spawns the ‘something went wrong’ message—from our error logs and yours, it looks like the search parameters are looking for titles and when those do not exist, and it breaks the
search. Although an archival object title in ASpace is conditionally required when a date subrecord is present, the search does not seem to recognize that flexibility.<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:#1F4E79"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="color:#1F4E79">In addition, it appears when a keyword search is conducted across all record types, and any one of the related archival objects (for example, a sibling or child archival object in a series) does not have a
title, any search for terms in that series will also generate the ‘something went wrong’ search result.<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:#1F4E79"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="color:#1F4E79">We’ve been able to reproduce this result and repair it. Adding the titles resolved the search error. I also created a simple test record with archival objects that do not possess titles; a search within the
titles gives the broken search result but once the title is entered and saved, the search works. I’ve attached an EAD export of that test resource record (we used unique terms for us, ‘AEIOU’ and ‘fuzzy’ so we could pinpoint the test). You’ll see that the
series in the EAD export does not have a <unittitle> field.<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:#1F4E79"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="color:#1F4E79">We’ve made the local decision to require title fields for all archival objects.<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:#1F4E79"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="color:#1F4E79">I hope this helps identity trouble areas. Perhaps the public interface search could be updated to work with archival objects lacking titles—or the archival object title field made required?<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:#1F4E79"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F4E79">Neal</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#1F4E79">--<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#1F4E79">Neal Harmeyer<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#1F4E79">Digital Archivist<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#1F4E79">Archives and Special Collections<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#1F4E79">Purdue University Libraries<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#1F4E79"><a href="mailto:harmeyna@purdue.edu">harmeyna@purdue.edu</a><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoPlainText"><span style="color:#1F4E79"><o:p> </o:p></span></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">-----Original Message-----<br>
From: <a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_group-bounces@lyralists.lyrasis.org</a> [<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org</a>]
On Behalf Of DUPRE, LANCE<br>
Sent: Wednesday, August 23, 2017 11:55 AM<br>
To: Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@lyralists.lyrasis.org</a>><br>
Subject: [Archivesspace_Users_Group] Error when searching in archivesspace v2.1.1<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Hello,<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">We have a test instance of archivespace 2.1.1 that is throwing the "Something went wrong" error when a search is performed searching all record types and for a keyword. It is only throwing the error for certain words (ex tree, navy and
possibly others) and other words return results fine. The * wildcard also returns results.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Our production instance, on archivesspace 1.5.4 does not throw these errors when I do the same search.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">I have attached the logs I think are relevant to the search.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Any help would be appreciated.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Thanks,<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">, [2017-08-23T11:48:57.060531 #11297] DEBUG -- : Thread-2022: GET /repositories/9/accessions?all_ids=true&modified_since=1503433821 [session: #<Session:0x291a34af @store={:user=>"search_indexer", :login_time=>2017-08-23 10:57:40 -0400,
:expirable=>false}, @id="35ccdf0821cbc8065adf7f1576eb02e254564cd1484d6cc5dec6c673ae3ba709", @system_mtime=2017-08-23 15:48:27 UTC>] D, [2017-08-23T11:48:57.061902 #11297] DEBUG -- : Thread-2022: Post-processed params: {"all_ids"=>true, "modified_since"=>1503433821,
:repo_id=>9} Aug 23, 2017 11:48:57 AM org.eclipse.jetty.server.handler.ContextHandler$Context log<o:p></o:p></p>
<p class="MsoPlainText">INFO: F, [2017-08-23T11:48:57.063591 #11297] FATAL -- : [11861f8d-4ed2-494e-93d5-bde230321aec]
<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Aug 23, 2017 11:48:57 AM org.eclipse.jetty.server.handler.ContextHandler$Context log<o:p></o:p></p>
<p class="MsoPlainText">INFO: F, [2017-08-23T11:48:57.064606 #11297] FATAL -- : [11861f8d-4ed2-494e-93d5-bde230321aec] ActionView::Template::Error (key not found: :title):<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">D, [2017-08-23T11:48:57.066191 #11297] DEBUG -- : Thread-2022: Responded with [200, {"Content-Type"=>"application/json", "Cache-Control"=>"private, must-revalidate, max-age=0", "Content-Length"=>"3"}, ["[]\n"]]... in 6ms Aug 23, 2017
11:48:57 AM org.eclipse.jetty.server.handler.ContextHandler$Context log<o:p></o:p></p>
<p class="MsoPlainText">INFO: F, [2017-08-23T11:48:57.065756 #11297] FATAL -- : [11861f8d-4ed2-494e-93d5-bde230321aec] 50: <% result.ancestors.each do |ancestor| %><o:p></o:p></p>
<p class="MsoPlainText">[11861f8d-4ed2-494e-93d5-bde230321aec] 51: /<o:p></o:p></p>
<p class="MsoPlainText">[11861f8d-4ed2-494e-93d5-bde230321aec] 52: <span class="ancestor"><o:p></o:p></p>
<p class="MsoPlainText">[11861f8d-4ed2-494e-93d5-bde230321aec] 53: <%= link_to process_mixed_content(ancestor.fetch('title')).html_safe, app_prefix(ancestor.fetch('uri')) %><o:p></o:p></p>
<p class="MsoPlainText">[11861f8d-4ed2-494e-93d5-bde230321aec] 54: </span><o:p></o:p></p>
<p class="MsoPlainText">[11861f8d-4ed2-494e-93d5-bde230321aec] 55: <% end %><o:p></o:p></p>
<p class="MsoPlainText">[11861f8d-4ed2-494e-93d5-bde230321aec] 56: <% else %><o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Aug 23, 2017 11:48:57 AM org.eclipse.jetty.server.handler.ContextHandler$Context log<o:p></o:p></p>
<p class="MsoPlainText">INFO: F, [2017-08-23T11:48:57.066453 #11297] FATAL -- : [11861f8d-4ed2-494e-93d5-bde230321aec]
<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Aug 23, 2017 11:48:57 AM org.eclipse.jetty.server.handler.ContextHandler$Context log<o:p></o:p></p>
<p class="MsoPlainText">INFO: F, [2017-08-23T11:48:57.067003 #11297] FATAL -- : [11861f8d-4ed2-494e-93d5-bde230321aec] app/views/shared/_result.html.erb:53:in `block in _app_views_shared__result_html_erb___496965727_2290'<o:p></o:p></p>
<p class="MsoPlainText">[11861f8d-4ed2-494e-93d5-bde230321aec] app/views/shared/_result.html.erb:50:in `_app_views_shared__result_html_erb___496965727_2290'<o:p></o:p></p>
<p class="MsoPlainText">[11861f8d-4ed2-494e-93d5-bde230321aec] app/views/search/search_results.html.erb:72:in `block in _app_views_search_search_results_html_erb___490211956_2278'<o:p></o:p></p>
<p class="MsoPlainText">[11861f8d-4ed2-494e-93d5-bde230321aec] app/views/search/search_results.html.erb:71:in `_app_views_search_search_results_html_erb___490211956_2278'<o:p></o:p></p>
<p class="MsoPlainText">[11861f8d-4ed2-494e-93d5-bde230321aec] app/controllers/search_controller.rb:59:in `search'<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">_______________________________________________<o:p></o:p></p>
<p class="MsoPlainText">Archivesspace_Users_Group mailing list<o:p></o:p></p>
<p class="MsoPlainText"><a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org"><span style="color:windowtext;text-decoration:none">Archivesspace_Users_Group@lyralists.lyrasis.org</span></a><o:p></o:p></p>
<p class="MsoPlainText"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__secure-2Dweb.cisco.com_15lWK5VFuWNYU8-2Ddysqpky6CV0tBt-2D4GGXX7vXdSyYU9KRzp-2DCuiExj7UOi6znSgQuoHzU-5FbugQWuB2AhpAoyjk-2D8HZ-5F7zXWkpvTrrtiKG9VSeG2Z4UtkxEkMafDFKKmdLWkVH7PocSqfwIt6DzC4FMFo5uN9X1-5FvHDu-5FPcd36-2DBPZHVDrRxYibxSD5OgpCEOvauD51TSX2pgrdDEdUKOcxDsX1XtcmTkpJ2P28WEorUKVG5yLWdx2gF-5FMekYRyTJZoUBiDtGJdOm2p8LLuRBCStt4PVbjoBt5SwPrkYWO1B3xEaBMP1dw3P0-5FQhDbEv8lbuuhadbsK4cp5EKBqAZNiJ4sJFSEEYPQiHaUYCGLCU_http-253A-252F-252Flyralists.lyrasis.org-252Fmailman-252Flistinfo-252Farchivesspace-5Fusers-5Fgroup&d=DwMFAg&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=P54V6LrXJP5Ddzc8ZItBdqB1Kr3elvFIQ04P7n0UCbQ&m=WWDt2pKrjhqtsW2LY1FslQB2ebDUgEldSRP8AP_iUbo&s=HfdAYjl2iDc8zOclK3RhBI5h8_tZ6zPUE1QnXMWmnVU&e="><span style="color:windowtext;text-decoration:none">http://secure-web.cisco.com/15lWK5VFuWNYU8-dysqpky6CV0tBt-4GGXX7vXdSyYU9KRzp-CuiExj7UOi6znSgQuoHzU_bugQWuB2AhpAoyjk-8HZ_7zXWkpvTrrtiKG9VSeG2Z4UtkxEkMafDFKKmdLWkVH7PocSqfwIt6DzC4FMFo5uN9X1_vHDu_Pcd36-BPZHVDrRxYibxSD5OgpCEOvauD51TSX2pgrdDEdUKOcxDsX1XtcmTkpJ2P28WEorUKVG5yLWdx2gF_MekYRyTJZoUBiDtGJdOm2p8LLuRBCStt4PVbjoBt5SwPrkYWO1B3xEaBMP1dw3P0_QhDbEv8lbuuhadbsK4cp5EKBqAZNiJ4sJFSEEYPQiHaUYCGLCU/http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group</span></a><o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
</div>
</body>
</html>