<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body>
<p>My fix should prevent all "Failed to clean XML: The reference to
entity..." errors triggered by EAD-compliant encoding. But,
depending on what version of ArchivesSpace you are running, it may
only make a difference in niche cases. As I understand it
(although Blake may wish to correct me if I am wrong) the timeline
is this:</p>
<blockquote>
<p>Up to 2.7.0, PDFs generated by the PUI did not fail in this
precise way, at least not if your records used EAD-compliant
encoding of characters such as ampersands, greater-than,
less-than, etc. <br>
</p>
<p>In 2.7.1, a change was made to allow people to include a HTML
entity reference, specifically the one for non-breaking spaces
( ) in their records. That is not strictly
EAD-compliant encoding, but some people use them for formatting
purposes, or because their records are converted from old web
pages. But that broke generation of PDFs for records containing
EAD-compliant encoding of ampersands which happened to be
immediately followed by an uppercase letter (e.g.
"B&W").</p>
<p>In 2.8.1, the case of ampersands immediately followed by an
uppercase letter was fixed, but PDFs will still fail if a record
contains an ampersand immediately followed by a character which
isn't an ASCII upper or lowercase alphabetic character or space.
The specific case I've encountered is numbers in citations of
printed resources (e.g. "Vols. 1&2") but it could also
happen with UTF-8 characters outside the ASCII range.<br>
</p>
<p>Now, my proposed fix would, I believe, prevent PDFs from
breaking whatever immediately follows an ampersand. Also
potentially other problems such as records containing <
in certain contexts. Admittedly these are rare, but if you've
got enough records they will occur somewhere, and they are
fiendishly difficult to track down.<br>
</p>
</blockquote>
<p>So, if you are running 2.7.1 or 2.8.0, and you are sure that your
records only contain things like "B&W", and never things
like "Vols. 1&2", then upgrading to 2.8.1 or higher would
probably fix your problem.<br>
</p>
<p>If you're already running 2.8.1 or higher, my fix is currently
untested by anyone but me, but if you want to give it a try, let
me know.<br>
</p>
<p>Andrew.</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 06/01/2022 14:28, Kyle Breneman
wrote:<br>
</div>
<blockquote type="cite" cite="mid:MN2PR05MB70223AAA2140FF01B02E065AB94C9@MN2PR05MB7022.namprd05.prod.outlook.com">
<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-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;}@font-face
{font-family:Garamond;
panose-1:2 2 4 4 3 3 1 1 8 3;}@font-face
{font-family:"Century Gothic";
panose-1:2 11 5 2 2 2 2 2 2 4;}@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}@font-face
{font-family:"Century Gothic \,sans-serif";
panose-1:0 0 0 0 0 0 0 0 0 0;}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;}code
{mso-style-priority:99;
font-family:"Courier New";}pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}p.xmsonormal, li.xmsonormal, div.xmsonormal
{mso-style-name:x_msonormal;
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}p.xmsonormal0, li.xmsonormal0, div.xmsonormal0
{mso-style-name:x_msonormal0;
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}p.xxmsonormal, li.xxmsonormal, div.xxmsonormal
{mso-style-name:x_xmsonormal;
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}p.xxmsochpdefault, li.xxmsochpdefault, div.xxmsochpdefault
{mso-style-name:x_xmsochpdefault;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}p.xmsochpdefault, li.xmsochpdefault, div.xmsochpdefault
{mso-style-name:x_msochpdefault;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:10.0pt;
font-family:"Calibri",sans-serif;}span.xmsohyperlink
{mso-style-name:x_msohyperlink;
color:#0563C1;
text-decoration:underline;}span.xmsohyperlinkfollowed
{mso-style-name:x_msohyperlinkfollowed;
color:#954F72;
text-decoration:underline;}span.xxmsohyperlink
{mso-style-name:x_xmsohyperlink;
color:#0563C1;
text-decoration:underline;}span.xxmsohyperlinkfollowed
{mso-style-name:x_xmsohyperlinkfollowed;
color:#954F72;
text-decoration:underline;}span.xxemailstyle17
{mso-style-name:x_xemailstyle17;
font-family:"Garamond",serif;
color:#2E74B5;}span.xemailstyle23
{mso-style-name:x_emailstyle23;
font-family:"Garamond",serif;
color:#2E74B5;}span.EmailStyle33
{mso-style-type:personal;
font-family:"Garamond",serif;
color:#2E74B5;}span.EmailStyle34
{mso-style-type:personal-compose;
font-family:"Garamond",serif;
color:#2E74B5;}.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}div.WordSection1
{page:WordSection1;}</style>
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Garamond",serif;color:#2E74B5">Andrew,
thank you for taking the time to point me to your Github
fix. I
<i>do</i> see the “Failed to clean XML” error in my logs,
but in each case it is seemingly upset about missing
semicolons: “Failed to clean XML: The reference to entity
"W" must end with the ';' delimiter.”<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Garamond",serif;color:#2E74B5"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Garamond",serif;color:#2E74B5">If
I understand your Github repo code, it is narrowly targeted
at dealing with situations where & is immediately
followed by a digit, and so would not help in my situation.
Have I got that right?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Garamond",serif;color:#2E74B5"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><b><span style="font-size:14.0pt;font-family:"Century
Gothic",sans-serif;color:#4472C4">Kyle Breneman<o:p></o:p></span></b></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Century
Gothic",sans-serif;color:#70AD47">Integrated Digital
Services Librarian<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Century
Gothic",sans-serif;color:black">The University of
Baltimore<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#2E74B5"><a href="mailto:kbreneman@ubalt.edu" moz-do-not-send="true"><span style="font-size:12.0pt;font-family:"Century
Gothic",sans-serif">kbreneman@ubalt.edu</span></a></span><span style="font-size:12.0pt;font-family:"Century
Gothic",sans-serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><i><span style="font-size:10.0pt;font-family:"Century
Gothic",sans-serif;color:#2E74B5">I believe in
freedom of thought and
<o:p></o:p></span></i></p>
<p class="MsoNormal"><i><span style="font-size:10.0pt;font-family:"Century
Gothic",sans-serif;color:#2E74B5">freedom of
speech. Do you?<o:p></o:p></span></i></p>
</div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Garamond",serif;color:#2E74B5"><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 class="moz-txt-link-abbreviated" href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_group-bounces@lyralists.lyrasis.org</a>
<a class="moz-txt-link-rfc2396E" href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org"><archivesspace_users_group-bounces@lyralists.lyrasis.org></a>
<b>On Behalf Of </b>Andrew Morrison<br>
<b>Sent:</b> Thursday, January 6, 2022 5:14 AM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@lyralists.lyrasis.org</a><br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] Advice on
what to look for in AS logs after printing error?<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:solid black 1.0pt;padding:2.0pt 2.0pt 2.0pt
2.0pt">
<p class="MsoNormal" style="background:pink"><b><span style="color:pink">[</span></b><b><span style="color:black">EXTERNAL EMAIL: This message
originated from a non-UBalt email system. Hover over any
links before clicking and use caution when opening
attachments.</span></b><b><span style="color:pink">]</span></b><o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p>If you do see that "Failed to clean XML" message in the
logs, then you might be interested in this pull request I
submitted recently:<o:p></o:p></p>
<p><o:p> </o:p></p>
<p><a href="https://github.com/archivesspace/archivesspace/pull/2553" moz-do-not-send="true">https://github.com/archivesspace/archivesspace/pull/2553</a><o:p></o:p></p>
<p><o:p> </o:p></p>
<p>I could put the same fix into the form of a plug-in, if
that is what you are seeing, you have the ability to install
plug-ins, and you are running 2.7.1 or newer.<o:p></o:p></p>
<p><o:p> </o:p></p>
<p>It might be a different markup issue, but in my experience
the logs never tell you which archival object the problem is
in. It cannot, because by that point it has converted the
collection into a temporary HTML file, which is the
intermediate step before converting to PDF. You could try
exporting as EAD from the staff interface, then validating
in an XML editor, but if the issue is something which is
valid in EAD, then it can be very difficult to trace. If you
have a local development instance of ArchivesSpace, you can
modify the code so it doesn't delete the temporary HTML
files, then validate those.
<o:p></o:p></p>
<p><o:p> </o:p></p>
<p>Andrew.<o:p></o:p></p>
<p><o:p> </o:p></p>
<p><o:p> </o:p></p>
<div>
<p class="MsoNormal">On 05/01/2022 18:14, Blake Carver
wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">It's going to be
a bit of looking for a bunch of needles in a very
short hay stack kinda thing.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">The errors should
have either FATAL or ERROR and something about pdf
around there somewhere. Sometimes there will be
allotta other FATAL and ERROR around, so you'll need
to narrow it down based on what each one says.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">You could also
look for "92" "126" and "21" I think the resource
number should show up around the error as well.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">Also wouldn't
surprise me to see this error in particular, but not
always:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<div style="mso-element:para-border-div;border:solid
#C2C8CC 1.0pt;padding:5.0pt 8.0pt 5.0pt
8.0pt;background:#F8F9F9">
<pre style="line-height:14.25pt;background:#F8F9F9;word-break:break-all;border:none;padding:0in;border-radius:3px;overflow-wrap:break-word;outline:0px"><code><span style="font-size:9.0pt;color:#68737D">RuntimeError (Failed to clean XML: The entity name must immediately follow the '&' in the entity reference.):</span></code><span style="font-size:9.0pt;font-family:Consolas;color:#68737D"><o:p></o:p></span></pre>
</div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div class="MsoNormal" style="text-align:center" align="center">
<hr width="98%" size="3" align="center">
</div>
<div id="divRplyFwdMsg">
<p class="MsoNormal"><b><span style="color:black">From:</span></b><span style="color:black">
<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" moz-do-not-send="true">archivesspace_users_group-bounces@lyralists.lyrasis.org</a>
<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" moz-do-not-send="true"><archivesspace_users_group-bounces@lyralists.lyrasis.org></a>
on behalf of Kyle Breneman
<a href="mailto:kbreneman@ubalt.edu" moz-do-not-send="true"><kbreneman@ubalt.edu></a><br>
<b>Sent:</b> Wednesday, January 5, 2022 12:36 PM<br>
<b>To:</b> Archivesspace Users Group <a href="mailto:archivesspace_users_group@lyralists.lyrasis.org" moz-do-not-send="true">
<archivesspace_users_group@lyralists.lyrasis.org></a><br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] Advice
on what to look for in AS logs after printing error?</span>
<o:p></o:p></p>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="xmsonormal"><span style="font-size:12.0pt;font-family:"Garamond",serif;color:#2E74B5">Thank
you for that reminder, Blake! Another question: the
print action was being run from the following
pages. Wouldn’t clicking the AS print button itself
register in the logs? If so, how could I
efficiently find those lines?</span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:12.0pt;font-family:"Garamond",serif;color:#2E74B5"> </span><o:p></o:p></p>
<p class="xmsonormal"><a href="https://archivesspace.ubalt.edu/repositories/2/resources/92" target="_blank" moz-do-not-send="true">https://archivesspace.ubalt.edu/repositories/2/resources/92</a><br>
<br>
<a href="https://archivesspace.ubalt.edu/repositories/2/resources/126" target="_blank" moz-do-not-send="true">https://archivesspace.ubalt.edu/repositories/2/resources/126</a><br>
<br>
<a href="https://archivesspace.ubalt.edu/repositories/2/resources/21" target="_blank" moz-do-not-send="true">https://archivesspace.ubalt.edu/repositories/2/resources/21</a><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:12.0pt;font-family:"Garamond",serif;color:#2E74B5"> </span><o:p></o:p></p>
<div>
<p class="xmsonormal"><b><span style="font-size:14.0pt;font-family:"Century
Gothic",sans-serif;color:#4472C4">Kyle
Breneman</span></b><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:12.0pt;font-family:"Century
Gothic",sans-serif;color:#70AD47">Integrated
Digital Services Librarian</span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:12.0pt;font-family:"Century
Gothic",sans-serif;color:black">The
University of Baltimore</span><o:p></o:p></p>
<p class="xmsonormal"><a href="mailto:kbreneman@ubalt.edu" moz-do-not-send="true"><span style="font-size:12.0pt;font-family:"Century
Gothic",sans-serif">kbreneman@ubalt.edu</span></a><o:p></o:p></p>
<p class="xmsonormal"><i><span style="font-size:10.0pt;font-family:"Century
Gothic",sans-serif;color:#2E74B5">I believe
in freedom of thought and
</span></i><o:p></o:p></p>
<p class="xmsonormal"><i><span style="font-size:10.0pt;font-family:"Century
Gothic",sans-serif;color:#2E74B5">freedom
of speech. Do you?</span></i><o:p></o:p></p>
</div>
<p class="xmsonormal"><span style="font-size:12.0pt;font-family:"Garamond",serif;color:#2E74B5"> </span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="xmsonormal"><b>From:</b> <a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" moz-do-not-send="true">
archivesspace_users_group-bounces@lyralists.lyrasis.org</a> <a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" moz-do-not-send="true">
<archivesspace_users_group-bounces@lyralists.lyrasis.org></a> <b>On
Behalf Of </b>
Blake Carver<br>
<b>Sent:</b> Wednesday, January 5, 2022 12:31 PM<br>
<b>To:</b> Archivesspace Users Group <a href="mailto:archivesspace_users_group@lyralists.lyrasis.org" moz-do-not-send="true">
<archivesspace_users_group@lyralists.lyrasis.org></a><br>
<b>Subject:</b> Re: [Archivesspace_Users_Group]
Advice on what to look for in AS logs after
printing error?<o:p></o:p></p>
</div>
</div>
<p class="xmsonormal"> <o:p></o:p></p>
<div style="border:solid black 1.0pt;padding:2.0pt 2.0pt
2.0pt 2.0pt">
<p class="xmsonormal" style="background:pink"><b><span style="color:pink">[</span><span style="color:black">EXTERNAL EMAIL: This message
originated from a non-UBalt email system. Hover
over any links before clicking and use caution
when opening attachments.</span><span style="color:pink">]</span></b><o:p></o:p></p>
</div>
<p class="xmsonormal"> <o:p></o:p></p>
<div>
<div>
<p class="xmsonormal"><span style="font-size:12.0pt;color:black">grep the
logs for ERROR or FATAL</span><o:p></o:p></p>
</div>
<div class="MsoNormal" style="text-align:center" align="center">
<hr width="98%" size="3" align="center">
</div>
<div id="x_divRplyFwdMsg">
<p class="xmsonormal"><b><span style="color:black">From:</span></b><span style="color:black">
</span><a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" moz-do-not-send="true">archivesspace_users_group-bounces@lyralists.lyrasis.org</a><span style="color:black"> <</span><a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" moz-do-not-send="true">archivesspace_users_group-bounces@lyralists.lyrasis.org</a><span style="color:black">> on behalf of Kyle
Breneman <</span><a href="mailto:kbreneman@ubalt.edu" moz-do-not-send="true">kbreneman@ubalt.edu</a><span style="color:black">><br>
<b>Sent:</b> Wednesday, January 5, 2022 12:28 PM<br>
<b>To:</b> </span><a href="mailto:archivesspace_users_group@lyralists.lyrasis.org" moz-do-not-send="true">archivesspace_users_group@lyralists.lyrasis.org</a><span style="color:black"> <</span><a href="mailto:archivesspace_users_group@lyralists.lyrasis.org" moz-do-not-send="true">archivesspace_users_group@lyralists.lyrasis.org</a><span style="color:black">><br>
<b>Subject:</b> [Archivesspace_Users_Group]
Advice on what to look for in AS logs after
printing error?</span>
<o:p></o:p></p>
<div>
<p class="xmsonormal"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="xxmsonormal"><span style="font-size:12.0pt;font-family:"Garamond",serif;color:#2E74B5">Our
archives staff have noticed that AS tends to
get hung up when users click the Print button
on some of our largest collections. Campus IT
tested this today. The server did not hang
for them, but the print action also <i>did
not complete</i>. They got a very, very
generic error message (attached).
</span><o:p></o:p></p>
<p class="xxmsonormal"><span style="font-size:12.0pt;font-family:"Garamond",serif;color:#2E74B5"> </span><o:p></o:p></p>
<p class="xxmsonormal"><span style="font-size:12.0pt;font-family:"Garamond",serif;color:#2E74B5">I
have access to the ArchivesSpace files on the
server, including the /logs directory, but I’m
not sure how to parse the logs for clues.
Does anyone have advice for how I can sift
through the logs? </span><o:p></o:p></p>
<p class="xxmsonormal"><span style="font-size:12.0pt;font-family:"Garamond",serif;color:#2E74B5"> </span><o:p></o:p></p>
<p class="xxmsonormal"><b><span style="font-size:14.0pt">Kyle Breneman</span></b><o:p></o:p></p>
<p class="xxmsonormal"><span style="font-size:12.0pt;font-family:"Century
Gothic",sans-serif;color:#70AD47">Integrated
Digital Services Librarian</span><o:p></o:p></p>
<p class="xxmsonormal"><span style="font-size:12.0pt;font-family:"Century
Gothic",sans-serif;color:black">The
University of Baltimore</span><o:p></o:p></p>
<p class="xxmsonormal"><a href="mailto:kbreneman@ubalt.edu" moz-do-not-send="true"><span style="font-size:12.0pt;font-family:"Century
Gothic ,sans-serif",serif">kbreneman@ubalt.edu</span></a><o:p></o:p></p>
<p class="xxmsonormal"><i><span style="font-size:10.0pt">I believe in
freedom of thought and
</span></i><o:p></o:p></p>
<p class="xxmsonormal"><i><span style="font-size:10.0pt">freedom of speech.
Do you?</span></i><o:p></o:p></p>
<p class="xxmsonormal"> <o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>Archivesspace_Users_Group mailing list<o:p></o:p></pre>
<pre><a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org" moz-do-not-send="true">Archivesspace_Users_Group@lyralists.lyrasis.org</a><o:p></o:p></pre>
<pre><a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" moz-do-not-send="true">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</a><o:p></o:p></pre>
</blockquote>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Archivesspace_Users_Group mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@lyralists.lyrasis.org</a>
<a class="moz-txt-link-freetext" href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</a>
</pre>
</blockquote>
</body>
</html>