<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:x="urn:schemas-microsoft-com:office:excel" 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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.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="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Yeah, that seems to be the gist of it: if the ampersands look like “&” in the web forms, rather than “&”, they should continue to export okay in the note
fields in the newest release; if they look like “&” in a unit title, then those should still export fine; but if they look like “&” in a notes field, that will cause problems in the export. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">The bug has to do with how the exporter decides whether or not it should wrap the note in a paragraph element, probably to guard against instances when the “p”
elements are stored as text in the database (i.e. “<p>first paragraph</p>”, instead of “first paragraph”.)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I’m just now testing the problem with the attributes, and it seems that the paragraph elements will not export correctly in version 1.5 if a namespace prefix
(like ns2, used by the AT upon export, or xlink, used by ASpace) is present anywhere in the note. To be valid EAD 2002, though, one of your extref examples would need to be exported by the system like like this:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="background:white;text-autospace:none"><span style="color:black;background:white;mso-highlight:white">
</span><span style="color:#000096;background:white;mso-highlight:white"><p></span><span style="color:black;background:white;mso-highlight:white">Selected materials from the collection have been digitized and can be viewed by<br>
clicking the link below. </span><span style="color:#000096;background:white;mso-highlight:white"><extref</span><span style="color:black;background:white;mso-highlight:white"><br>
</span><span style="color:#F5844C;background:white;mso-highlight:white"> xlink:href</span><span style="color:#FF8040;background:white;mso-highlight:white">=</span><span style="color:#993300;background:white;mso-highlight:white">"http://library.ucsd.edu/dc/collection/bb5496475c"</span><span style="color:black;background:white;mso-highlight:white"><br>
</span><span style="color:#F5844C;background:white;mso-highlight:white"> xlink:title</span><span style="color:#FF8040;background:white;mso-highlight:white">=</span><span style="color:#993300;background:white;mso-highlight:white">"Items available
online"</span><span style="color:#000096;background:white;mso-highlight:white">></span><span style="color:black;background:white;mso-highlight:white">Items available online</span><span style="color:#000096;background:white;mso-highlight:white"></extref></span><span style="color:black;background:white;mso-highlight:white"><br>
</span><span style="color:#000096;background:white;mso-highlight:white"></p></span><span style="background:white;mso-highlight:white"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">But you can’t get that exported right now, since if you have “xlink:” (or “ns:”) on those attributes, then you won’t get a paragraph wrapper element (and I think
that behavior is new to version 1.5, but I’m not sure). I’m pretty sure it was required to have the “xlink:” prefix in previous versions of ASpace, though.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">*Both of these issues could probably be fixed with a minor patch to the exporter code in the short term, but I’d still prefer a holistic look into how XML is
handled upon import and export of the system in the long term.*<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">It’s probably a bad idea, for just one example, to include those namespace prefixes as text in the database (unless they were stored as XML, so that they could
be manipulated as XML rather than just text), since when ASpace gets an option to export EAD3, those prefixes can’t be included in the exports, and so, additional logic would have to be added to strip that information.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">In any event, I’ll add a few notes to the JIRA ticket that you created once I’ve looked into this a little more.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",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><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> archivesspace_users_group-bounces@lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org]
<b>On Behalf Of </b>McPhee, Laurel<br>
<b>Sent:</b> Monday, 25 July, 2016 12:11 PM<br>
<b>To:</b> Archivesspace Users Group<br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] RC candidates and v1.5.0 not creating <p> tags in EAD export<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Hi Mark,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Thanks for looking into it. So, if I may paraphrase you, if an organization upgrades to 1.5, and they have 500 resource records that they migrated a year ago
from AT (into, say, 1.4.2), all of their records with ampersands that previously exported just fine will now have trouble exporting as valid EAD. But if they create a NEW resource record in 1.5 from scratch, or import (not migrate) a new EAD in, loaded with
ampersands, it will export correctly with <p> tags. Is this correct?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">On Friday, I created a bug report for this issue:
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.atlassian.net_browse_AS-2D98&d=CwMFAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=s7ciGQfUJeaV_ryx908hbeXDoU9aqDwDN0Z0VbfsJ3Y&m=uz1FZfx7XilbqoApFXJbFygfmLZXmNfitL2QpazUF98&s=viVBfdqLLv2-6g_mT5fKq41nIgFsxYqr1075kigl8fI&e=">
https://archivesspace.atlassian.net/browse/AS-98</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">The language might need to be refined to address the full scope/details of the problem. Thanks for your input!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Laurel<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",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><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">
<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>Custer, Mark<br>
<b>Sent:</b> Monday, July 25, 2016 8:57 AM<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] RC candidates and v1.5.0 not creating <p> tags in EAD export<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div id="divtagdefaultwrapper">
<div>
<p style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Laurel, all:</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
<p style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
<p style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Following up on this issue, I tried to replicate it in the newest version of ArchivesSpace, but I haven’t had any luck (well, I uncovered a few other minor
bugs, but nothing as problematic as the ones you reported). Anyhow, here’s the file that I uploaded for testing, which is in the GoneRepo repository:
<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__test.archivesspace.org_resources_151&d=CwMFAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=s7ciGQfUJeaV_ryx908hbeXDoU9aqDwDN0Z0VbfsJ3Y&m=uz1FZfx7XilbqoApFXJbFygfmLZXmNfitL2QpazUF98&s=dCYMK0Y40R4njCVgy3xA12GGHUF7GJY_wziHodgP8g8&e=" id="LPlnk728498">
<span style="color:#0563C1">http://test.archivesspace.org/resources/151</span></a>.
</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
<p style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
<p style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">So, it appears that the problem is being caused by how previous importers (or migrators) handled the ampersands versus what the exporter expects now. For
example, this is text from one of our scope and content notes that was imported from AT, I think: “individual cards measuring 300 by 360mm & captioned.” (</span><span style="font-size:11.5pt;font-family:"Calibri",sans-serif;color:#1F497D">and</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> that
ampersand is not encoded as "&", which is how it is imported in versions 1.5, and possibly earlier). That ampersand no longer exports okay in version 1.5, but it exports fine in version 1.4.2 Ideally, the importers and exporters would have one way to
handle XML data but it seems like there have been different ways to do that in the past. I've no clue how best to handle that </span><span style="font-size:11.5pt;font-family:"Calibri",sans-serif;color:#1F497D">with</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> the
ASpace architecture, aside to say that it should be consistent in all aspects of the application.</span><span style="font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
<p style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<p style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Mark</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
<p style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
<p style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p style="background:white"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">
<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>Custer, Mark<br>
<b>Sent:</b> Thursday, 21 July, 2016 5:12 PM<br>
<b>To:</b> Archivesspace Users Group<br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] RC candidates and v1.5.0 not creating <p> tags in EAD export<o:p></o:p></span></p>
</div>
</div>
<p style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> <o:p></o:p></span></p>
<p style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Hi, Laurel:</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
<p style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
<p style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">What timing! I remember Brad mentioning this issue before, but I had completely forgotten about it until seeing your message about the exact same time
that I was testing a new automatic EAD export service for ArchivesSpace. Right before I read your message, I was wondering why so many of our files failed to produce valid EAD files. The main problem, it turns out, is the bug that’s not putting paragraph
elements around text that has ampersands. But this only happens in the 1.5 versions. I can confirm that in version 1.4.2 this problem doesn’t exist (that’s our production version), but that it does exist in 1.5 (that’s our test version). I haven’t tested
anything with the altformavail/extref issues, though. </span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
<p style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
<p style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I haven’t looked into the exporter code too much yet, but the history of updates to the EAD exporter file should provide clues (to the developers, at least):
</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_archivesspace_archivesspace_commits_master_backend_app_exporters_serializers_ead.rb&d=CwMFAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=s7ciGQfUJeaV_ryx908hbeXDoU9aqDwDN0Z0VbfsJ3Y&m=dURyN9dLHMTStr2wd50oCQjXJwVfE97zD-TWh4fTqus&s=bBnV5XYygTQhUg2JF6pLIPSbdbdXi-bu1T_qRF2ycdo&e="><span style="color:#0563C1">https://github.com/archivesspace/archivesspace/commits/master/backend/app/exporters/serializers/ead.rb</span></a></span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">
</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
<p style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
<p style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Mark</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
<p style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
<p style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
<p style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p style="background:white"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">
<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org"><span style="color:#0563C1">archivesspace_users_group-bounces@lyralists.lyrasis.org</span></a> [<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org"><span style="color:#0563C1">mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org</span></a>]
<b>On Behalf Of </b>McPhee, Laurel<br>
<b>Sent:</b> Thursday, 21 July, 2016 3:45 PM<br>
<b>To:</b> <a href="mailto:archivesspace_users_group@lyralists.lyrasis.org"><span style="color:#0563C1">archivesspace_users_group@lyralists.lyrasis.org</span></a><br>
<b>Subject:</b> [Archivesspace_Users_Group] RC candidates and v1.5.0 not creating <p> tags in EAD export<o:p></o:p></span></p>
</div>
</div>
<p style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> <o:p></o:p></span></p>
<p style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Hello,<o:p></o:p></span></p>
<p style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> <o:p></o:p></span></p>
<p style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">UC San Diego discovered an issue in R2 that we informally reported to B. Westbrook in early June. The bug is this: note fields containing either an & entity
ref and/or an <extref> tag do not get properly wrapped in a <p> tag upon EAD export. For example, all of our <prefercite> notes contain the term “Special Collections & Archives”, and because of the presence of the ampersand in the note, do not get wrapped.
Similarly, if a bioghist note has an & somewhere in it, none of the paragraphs get wrapped in a <p> tag, leaving us with giant block of text. And last, in altformavail, where we record the existence of digital versions of our collections with a link, the existence
of an <extref> causes the whole note to not get wrapped in a <p> tag when we export the EAD.<o:p></o:p></span></p>
<p style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> <o:p></o:p></span></p>
<p style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">This issue breaks our local scripts and also prevents validation on the Online Archive of California. At the time, I didn’t create a JIRA ticket, because
we were told the problem was being worked on…but now I’m going through the steps to create the ticket. Is there any feedback/observations on this in the member community before I do so? It’s happening in v1.5.0, which we tested this morning. Thanks!<o:p></o:p></span></p>
<p style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> <o:p></o:p></span></p>
<p style="background:white"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Laurel McPhee</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
<p style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Supervisory Archivist, Special Collections & Archives Program<o:p></o:p></span></p>
<p style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">UC San Diego Library |
</span><span style="font-size:10.0pt;font-family:Wingdings;color:black">(</span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">
</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">858-534-5619 |</span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">
</span><span style="font-size:10.0pt;font-family:Wingdings;color:black">*</span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">
</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><a href="mailto:lmcphee@ucsd.edu"><span style="color:#0563C1">lmcphee@ucsd.edu</span></a><o:p></o:p></span></p>
<p style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> <o:p></o:p></span></p>
<p style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> <o:p></o:p></span></p>
</div>
</div>
</div>
</body>
</html>