<html><body><div style="font-family: georgia,serif; font-size: 10pt; color: #000000"><div>Hello,</div><div><br></div><div>I apologize if this has been addressed elsewhere, but I couldn't find an answer after searching in the Google Group or Pivotal Tracker (side note: is there an easy way to search this listserv's archives?).</div><div><br></div><div>I've noticed that the block text found in the Content fields of Notes, when exported as EAD, is wrapping that text in this:</div><div><br></div><div><p class="p1" style="margin: 0px;" data-mce-style="margin: 0px;"><![CDATA[ Text. text. text. ]]></p><p class="p1" style="margin: 0px;" data-mce-style="margin: 0px;"><br></p><p class="p1" style="margin: 0px;" data-mce-style="margin: 0px;">Any idea why this is or what we can do to adjust it?</p><p class="p1" style="margin: 0px;" data-mce-style="margin: 0px;"><br></p><p class="p1" style="margin: 0px;" data-mce-style="margin: 0px;">On a related topic, a lot of our Bio/Hist and Scope/Content are multi-paragraph notes that had <p> tags embedded appropriately in AT, but <span style="font-size: 13.63636302948px;" data-mce-style="font-size: 13.63636302948px;">we apparently lost these tags/embedded content for our notes in the migration to ASpace. ASpace applies bookend <p> tags around the entirety of the note on EAD export, but this results in code like this:</span></p><p class="p1" style="margin: 0px;" data-mce-style="margin: 0px;"><br></p><p class="p1" style="margin: 0px;" data-mce-style="margin: 0px;"><p>Paragraph.</p><p class="p1" style="margin: 0px;" data-mce-style="margin: 0px;"><br></p><p class="p1" style="margin: 0px;" data-mce-style="margin: 0px;">New paragraph.</p><p class="p1" style="margin: 0px;" data-mce-style="margin: 0px;"><br></p><p class="p1" style="margin: 0px;" data-mce-style="margin: 0px;">Last paragraph.</p></p><p class="p1" style="margin: 0px;" data-mce-style="margin: 0px;"><br></p><p class="p1" style="margin: 0px;" data-mce-style="margin: 0px;">We're currently preparing to republish all our finding aids using the ASpace API, but would love to fix this first. Does anyone have ideas on how we might remediate this without manually checking/editing every resource? We're still running 1.09, so if someone tells me the answer is an upgrade to 1.1, I will be thrilled!</p><p class="p1" style="margin: 0px;" data-mce-style="margin: 0px;"><br></p><p class="p1" style="margin: 0px;" data-mce-style="margin: 0px;">Thanks,</p><p class="p1" style="margin: 0px;" data-mce-style="margin: 0px;">Ben</p><p class="p1" style="margin: 0px;" data-mce-style="margin: 0px;"><br></p><p class="p1" style="margin: 0px;" data-mce-style="margin: 0px;"><br></p></div><div><br></div><div><span name="x"></span><span data-mce-style="color: #000000; font-size: small;" style="color: #000000; font-size: small;" size="2"><span style="font-family: georgia,serif; font-weight: bold;">Ben Goldman</span><br style="font-family: georgia,serif;"><span style="font-family: georgia,serif;">Digital Records Archivist</span><br style="font-family: georgia,serif;"><span style="font-family: georgia,serif;">Penn State University Libraries</span><br style="font-family: georgia,serif;"><span style="font-family: georgia,serif;">University Park, PA</span><br style="font-family: georgia,serif;"><span style="font-family: georgia,serif;">814-863-8333<br><a href="http://www.libraries.psu.edu/psul/speccolls.html">http://www.libraries.psu.edu/psul/speccolls.html</a><br></span></span><span name="x"></span><br></div></div></body></html>