<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style type="text/css" style="display:none"><!--P{margin-top:0;margin-bottom:0;} .ms-cui-menu {background-color:#ffffff;border:1px rgb(166, 166, 166) solid;font-family:'Segoe UI','Segoe WP','Segoe UI WPC',Tahoma,Arial,sans-serif;font-size:10pt;color:rgb(51, 51, 51);} .ms-cui-menusection-title {display:none;} .ms-cui-ctl {vertical-align:text-top;text-decoration:none;color:rgb(51, 51, 51);} .ms-cui-ctl-on {background-color:rgb(205, 230, 247);opacity: 0.8;} .ms-cui-img-cont-float {display:inline-block;margin-top:2px} .ms-cui-smenu-inner {padding-top:0px;} .ms-owa-paste-option-icon {margin: 0px 6px 0px 6px;vertical-align:middle!important;padding-bottom: 2px;display:inline-block;} .ms-rtePasteFlyout-option:hover {background-color:rgb(205, 230, 247) !important;opacity:1 !important;} .ms-rtePasteFlyout-option {padding:8px 4px 8px 4px;outline:none;} .ms-cui-menusection {float:left; width:85px;height:24px;overflow:hidden}.wf {speak:none; font-weight:normal; font-variant:normal; text-transform:none; -webkit-font-smoothing:antialiased; vertical-align:middle; display:inline-block;}.wf-family-owa {font-family:'o365Icons'}@font-face {  font-family:'o365IconsIE8';  src:url('https://r4.res.outlook.com/owa/prem/16.0.326.10/resources/styles/office365icons.ie8.eot?#iefix') format('embedded-opentype'),         url('https://r4.res.outlook.com/owa/prem/16.0.326.10/resources/styles/office365icons.ie8.woff') format('woff'),         url('https://r4.res.outlook.com/owa/prem/16.0.326.10/resources/styles/office365icons.ie8.ttf') format('truetype');  font-weight:normal;  font-style:normal;}@font-face {  font-family:'o365IconsMouse';  src:url('https://r4.res.outlook.com/owa/prem/16.0.326.10/resources/styles/office365icons.mouse.eot?#iefix') format('embedded-opentype'),         url('https://r4.res.outlook.com/owa/prem/16.0.326.10/resources/styles/office365icons.mouse.woff') format('woff'),         url('https://r4.res.outlook.com/owa/prem/16.0.326.10/resources/styles/office365icons.mouse.ttf') format('truetype');  font-weight:normal;  font-style:normal;}.wf-family-owa {font-family:'o365IconsMouse'}.ie8 .wf-family-owa {font-family:'o365IconsIE8'}.ie8 .wf-owa-play-large:before {content:'\e254';}.notIE8 .wf-owa-play-large:before {content:'\e054';}.ie8 .wf-owa-play-large {color:#FFFFFF/*$WFWhiteColor*/;}.notIE8 .wf-owa-play-large {border-color:#FFFFFF/*$WFWhiteColor*/; width:1.4em; height:1.4em; border-width:.1em; border-style:solid; border-radius:.8em; text-align:center; box-sizing:border-box; -moz-box-sizing:border-box; padding:0.1em; color:#FFFFFF/*$WFWhiteColor*/;}.ie8 .wf-size-play-large {width:40px; height:40px; font-size:30px}.notIE8 .wf-size-play-large {width:40px; height:40px; font-size:30px}.notIE8 .wf-owa-triangle-down-small:before {content:'\e052';}.ie8 .wf-owa-triangle-down-small:before { content:'\e052';}.ie8 .wf-owa-triangle-down-small {color:#666666/*$WFGreyColor*/;}.wf-size-x20 {font-size: 20px!important;}
<!--
@font-face
        {font-family:Wingdings}
@font-face
        {font-family:"Cambria Math"}
@font-face
        {font-family:Calibri}
@font-face
        {font-family:Tahoma}
@font-face
        {font-family:"Segoe UI"}
@font-face
        {font-family:o365IconsIE8}
@font-face
        {font-family:o365IconsMouse}
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif"}
a:link, span.MsoHyperlink
        {color:#0563C1;
        text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
        {color:#954F72;
        text-decoration:underline}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:8.0pt;
        font-family:"Tahoma","sans-serif"}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
        {margin-top:0in;
        margin-right:0in;
        margin-bottom:0in;
        margin-left:.5in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif"}
span.BalloonTextChar
        {font-family:"Tahoma","sans-serif"}
p.ms-cui-menu, li.ms-cui-menu, div.ms-cui-menu
        {margin:0in;
        margin-bottom:.0001pt;
        background:white;
        font-size:10.0pt;
        font-family:"Segoe UI","sans-serif";
        color:#333333}
p.ms-cui-menusection-title, li.ms-cui-menusection-title, div.ms-cui-menusection-title
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif"}
p.ms-cui-ctl, li.ms-cui-ctl, div.ms-cui-ctl
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";
        color:#333333}
p.ms-cui-ctl-on, li.ms-cui-ctl-on, div.ms-cui-ctl-on
        {margin:0in;
        margin-bottom:.0001pt;
        background:#CDE6F7;
        font-size:12.0pt;
        font-family:"Times New Roman","serif"}
p.ms-cui-img-cont-float, li.ms-cui-img-cont-float, div.ms-cui-img-cont-float
        {margin-top:1.5pt;
        margin-right:0in;
        margin-bottom:0in;
        margin-left:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif"}
p.ms-cui-smenu-inner, li.ms-cui-smenu-inner, div.ms-cui-smenu-inner
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif"}
p.ms-owa-paste-option-icon, li.ms-owa-paste-option-icon, div.ms-owa-paste-option-icon
        {margin-top:0in;
        margin-right:4.5pt;
        margin-bottom:0in;
        margin-left:4.5pt;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif"}
p.ms-rtepasteflyout-option, li.ms-rtepasteflyout-option, div.ms-rtepasteflyout-option
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif"}
p.ms-cui-menusection, li.ms-cui-menusection, div.ms-cui-menusection
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif"}
p.wf, li.wf, div.wf
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif"}
p.wf-family-owa, li.wf-family-owa, div.wf-family-owa
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:o365IconsMouse}
p.msochpdefault, li.msochpdefault, div.msochpdefault
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:10.0pt;
        font-family:"Calibri","sans-serif"}
p.wf-owa-play-large, li.wf-owa-play-large, div.wf-owa-play-large
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif"}
p.wf-size-play-large, li.wf-size-play-large, div.wf-size-play-large
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif"}
p.wf-owa-triangle-down-small, li.wf-owa-triangle-down-small, div.wf-owa-triangle-down-small
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif"}
p.wf-family-owa1, li.wf-family-owa1, div.wf-family-owa1
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:o365IconsIE8}
p.wf-owa-play-large1, li.wf-owa-play-large1, div.wf-owa-play-large1
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";
        color:white}
p.wf-owa-play-large2, li.wf-owa-play-large2, div.wf-owa-play-large2
        {margin:0in;
        margin-bottom:.0001pt;
        text-align:center;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";
        color:white}
p.wf-size-play-large1, li.wf-size-play-large1, div.wf-size-play-large1
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:22.5pt;
        font-family:"Times New Roman","serif"}
p.wf-size-play-large2, li.wf-size-play-large2, div.wf-size-play-large2
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:22.5pt;
        font-family:"Times New Roman","serif"}
p.wf-owa-triangle-down-small1, li.wf-owa-triangle-down-small1, div.wf-owa-triangle-down-small1
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";
        color:#666666}
p.wf-family-owa2, li.wf-family-owa2, div.wf-family-owa2
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:o365IconsIE8}
p.wf-owa-play-large3, li.wf-owa-play-large3, div.wf-owa-play-large3
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";
        color:white}
p.wf-owa-play-large4, li.wf-owa-play-large4, div.wf-owa-play-large4
        {margin:0in;
        margin-bottom:.0001pt;
        text-align:center;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";
        color:white}
p.wf-size-play-large3, li.wf-size-play-large3, div.wf-size-play-large3
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:22.5pt;
        font-family:"Times New Roman","serif"}
p.wf-size-play-large4, li.wf-size-play-large4, div.wf-size-play-large4
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:22.5pt;
        font-family:"Times New Roman","serif"}
p.wf-owa-triangle-down-small2, li.wf-owa-triangle-down-small2, div.wf-owa-triangle-down-small2
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";
        color:#666666}
p.wf-family-owa3, li.wf-family-owa3, div.wf-family-owa3
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:o365IconsIE8}
p.wf-owa-play-large5, li.wf-owa-play-large5, div.wf-owa-play-large5
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";
        color:white}
p.wf-owa-play-large6, li.wf-owa-play-large6, div.wf-owa-play-large6
        {margin:0in;
        margin-bottom:.0001pt;
        text-align:center;
        border:none;
        padding:0in;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";
        color:white}
p.wf-size-play-large5, li.wf-size-play-large5, div.wf-size-play-large5
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:22.5pt;
        font-family:"Times New Roman","serif"}
p.wf-size-play-large6, li.wf-size-play-large6, div.wf-size-play-large6
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:22.5pt;
        font-family:"Times New Roman","serif"}
p.wf-owa-triangle-down-small3, li.wf-owa-triangle-down-small3, div.wf-owa-triangle-down-small3
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";
        color:#666666}
span.balloontextchar0
        {font-family:"Tahoma","sans-serif"}
span.emailstyle17
        {font-family:"Calibri","sans-serif";
        color:windowtext;
        font-weight:normal;
        font-style:normal;
        text-decoration:none none}
span.emailstyle41
        {font-family:"Calibri","sans-serif";
        color:windowtext;
        font-weight:normal;
        font-style:normal;
        text-decoration:none none}
span.emailstyle42
        {font-family:"Calibri","sans-serif";
        color:#1F497D}
span.balloontextchar00
        {font-family:"Tahoma","sans-serif"}
span.emailstyle52
        {font-family:"Calibri","sans-serif";
        color:#1F497D}
span.EmailStyle60
        {font-family:"Calibri","sans-serif";
        color:#1F497D}
.MsoChpDefault
        {font-size:10.0pt}
@page WordSection1
        {margin:1.0in 1.0in 1.0in 1.0in}
-->
--></style>
</head>
<body dir="ltr" style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p><br>
</p>
<p>Hi Mark,</p>
<p><br>
</p>
<p>I did speak to a couple people about this to figure out the best approach. I think I'd say it's ultimately up to the end users on how they want to encode their <p> tags. That said, I think there's been a large request to have line breaks converted to <p>
 tags on export.</p>
<p><br>
</p>
<p>So, I think the solution is going to be to have the exporter wrap blocks of text seperated by line breaks into <p> tags, which is pretty easy to do. In additon, it seems that the EAD importer should also strip out <p> and convert those blocks into separated
 blocks of text.</p>
<p><br>
</p>
<p>Regardless, both line breaks and <p> ( and all other EAD tags) will be mapped into proper HTML that renders that gives the desired effect.</p>
<p><br>
</p>
<p>Does that sound like reasonable approach? </p>
<p><br>
</p>
<p>b,chris. <br>
</p>
<p><br>
</p>
<div id="Signature">
<div name="divtagdefaultwrapper" style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:; margin:0">
<div class="BodyFragment"><font size="2">
<div class="PlainText">Chris Fitzpatrick | <font size="2">Developer, ArchivesSpace</font><br>
Skype: chrisfitzpat  | Phone: 918.236.6048<br>
http://archivesspace.org/<br>
</div>
</font></div>
</div>
</div>
<div style="color: rgb(33, 33, 33);">
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt" color="#000000" face="Calibri, sans-serif"><b>From:</b> archivesspace_users_group-bounces@lyralists.lyrasis.org <archivesspace_users_group-bounces@lyralists.lyrasis.org> on behalf of Custer, Mark
 <mark.custer@yale.edu><br>
<b>Sent:</b> Friday, August 01, 2014 5:28 PM<br>
<b>To:</b> Archivesspace Users Group<br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] AT > ASpace migration questions</font>
<div> </div>
</div>
<div>
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Chris,</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">Rather than a change to the EAD importer/exporter, what I’d like to understand is the preferred ArchivesSpace way to manage paragraphs within the notes table (and therefore within the JSON snippets).  I assume
 that everything should be encoded explicitly with paragraph elements.  Is that a fair assumption?  If so, will that assumption remain true? 
</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">Or to put it another way:  if someone is writing a scopecontent note from scratch in ArchivesSpace, should they wrap each paragraph in the paragraph element?  I want our data to be consistent across the board,
 whichever route we go (implicitly or explicitly encoded).  </span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">Mark</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<div>
<div style="border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif""> archivesspace_users_group-bounces@lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org]
<b>On Behalf Of </b>Chris Fitzpatrick<br>
<b>Sent:</b> Wednesday, July 30, 2014 5:04 AM<br>
<b>To:</b> Archivesspace Users Group<br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] AT > ASpace migration questions</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<p><span style="font-family:"Calibri","sans-serif"; color:black">Hi Mark,</span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:black"> </span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:black">Well, you can always tweak the EAD exporter and importer to have them work the way you need it to. These could be incorporated as a plugin, so you wouldn't need to do a rebuild.
</span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:black"> </span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:black"> </span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:black">But what I'm hearing is that you would like blocks of text separated by line breaks ( two line breaks? ) to be wrapped in <p> tag when they are exported? I think this is a common request and it
 shouldn't be difficult for us to implement as the default. </span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:black"> </span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:black">best, chris. </span>
</p>
<p><span style="font-family:"Calibri","sans-serif"; color:black">  </span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:black"> </span></p>
<div id="Signature">
<div name="divtagdefaultwrapper">
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt; color:black">Chris Fitzpatrick | Developer, ArchivesSpace<br>
Skype: chrisfitzpat  | Phone: 918.236.6048<br>
</span><a href="http://archivesspace.org/"><span style="font-size:10.0pt">http://archivesspace.org/</span></a><span style="font-size:10.0pt; color:black"></span></p>
</div>
</div>
</div>
</div>
<div>
<div class="MsoNormal" style="text-align:center" align="center"><span style="font-size:12.0pt; color:#212121">
<hr align="center" size="2" width="98%">
</span></div>
<div id="divRplyFwdMsg">
<p class="MsoNormal"><b><span style="color:black">From:</span></b><span style="color:black">
</span><a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_group-bounces@lyralists.lyrasis.org</a><span style="color:black"> <</span><a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_group-bounces@lyralists.lyrasis.org</a><span style="color:black">>
 on behalf of Custer, Mark <</span><a href="mailto:mark.custer@yale.edu">mark.custer@yale.edu</a><span style="color:black">><br>
<b>Sent:</b> Tuesday, July 29, 2014 6:49 PM<br>
<b>To:</b> Archivesspace Users Group<br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] AT > ASpace migration questions</span><span style="font-size:12.0pt; color:#212121">
</span></p>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt; color:#212121"> </span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="color:#1F497D">Chris,</span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I’m wondering how we should proceed with paragraphs since Archivists’ Toolkit handles paragraphs quite differently, and this is likely going to affect how we conduct our migration from AT to ArchivesSpace since
 we depend upon EAD exports (side note:  how are paragraphs handled in the Archon database?). 
</span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D">In the AT, the EAD paragraph element was never stored in the database (the EAD import process always stripped those out, but would nevertheless serialize them upon export where need be).  Here’s an example note
 from the AT, which includes two paragraphs, neither of which are encoded in the database:</span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D"> </span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">Thomas Turner, 1729-1793, was a shop-keeper, and for a time the school-master, in the village of East Hoathly in Sussex, England. He also became church-warden in 1757. From 1754 to 1765
 Turner wrote the diary which forms the major part of the papers.</span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D"> </span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">Further biographical information may be found in <title render="italic">The Diary of Thomas Turner of East Hoathly (1754-1765)</title>, an abridged edition edited by Florence Maris Turner
 (Mrs. Charles Lamb), great-great-granddaughter of the diarist, with an introduction by J. B. Priestly, published in 1925 by John Lane, the Bodly Head Ltd., London.
</span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D">That same note in ArchivesSpace looks like the following after using the database migration tool (and after converting it back to JSON):</span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">{</span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">    "jsonmodel_type": "note_multipart",</span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">    "label": "THOMAS TURNER 1729-1793",</span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">    "subnotes": [</span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">        {</span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">            "content":
</span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:#1F497D">"Thomas Turner, 1729-1793, was a shop-keeper, and for a time the school-master, in the village of East Hoathly in Sussex, England. He also became church-warden in 1757. From 1754 to
 1765 Turner wrote the diary which forms the major part of the papers.</span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:#1F497D">\n\n</span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:#1F497D">Further biographical information may be found in <title render=\"italic\">The Diary of Thomas Turner of East Hoathly (1754-1765)</title>, an abridged edition edited by Florence Maris
 Turner (Mrs. Charles Lamb), great-great-granddaughter of the diarist, with an introduction by J. B. Priestly, published in 1925 by John Lane, the Bodly Head Ltd., London.
</span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:#1F497D">\n\n",</span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">            "jsonmodel_type": "note_text",</span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">            "publish": true,</span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">            "subnote_guid": "0fa3207256b91d8d9832d99b470a3aea"</span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">        }</span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">    ],</span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">    "type": "bioghist",</span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">    "persistent_id": "bb5cd3f9e05a0b21cce68e4fbf0e7951"</span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">}</span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D">In both cases, there are no paragraph elements stored in the database. 
</span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D">If I export this finding aid from Archivist’s Toolkit, here’s the EAD that I get (which is the EAD that I need):</span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">      <bioghist id="ref11"></span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">         <head>THOMAS TURNER 1729-1793</head></span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">        
<span style="background:yellow"><p></span>Thomas Turner, 1729-1793, was a shop-keeper, and for a time the school-master, in the village of East Hoathly in Sussex, England. He also became church-warden in 1757. From 1754 to 1765 Turner wrote the diary which
 forms the major part of the papers<span style="background:yellow">.</p></span></span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">        
<span style="background:yellow"><p></span>Further biographical information may be found in
</span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">                <title ns2:type="simple" render="italic">The Diary of Thomas Turner of East Hoathly (1754-1765)</title>, an abridged edition edited by Florence Maris Turner (Mrs. Charles
 Lamb), great-great-granddaughter of the diarist, with an introduction by J. B. Priestly, published in 1925 by John Lane, the Bodly Head Ltd., London<span style="background:yellow">.</p></span></span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">      </bioghist></span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Note the 2 paragraph elements.</span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D">When I export this from ArchivesSpace (v1.0.9) after using the migration tool, here’s the result that I get:</span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">    <bioghist id="bb5cd3f9e05a0b21cce68e4fbf0e7951"></span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">      <head>THOMAS TURNER 1729-1793</head></span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">      <span style="background:yellow">
<p></span>Thomas Turner, 1729-1793, was a shop-keeper, and for a time the school-master, in the</span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">        village of East Hoathly in Sussex, England. He also became church-warden in 1757. From 1754</span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">        to 1765 Turner wrote the diary which forms the major part of the papers. Further</span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">        biographical information may be found in <title render="italic">The Diary of Thomas Turner</span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">          of East Hoathly (1754-1765)</title>, an abridged edition edited by Florence Maris Turner</span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">        (Mrs. Charles Lamb), great-great-granddaughter of the diarist, with an introduction by J. B.</span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">        Priestly, published in 1925 by John Lane, the Bodly Head Ltd., London.
<span style="background:yellow"></p></span></span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">    </bioghist></span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Now there’s just a single paragraph element, where two paragraph elements should be, and this won’t work for us.</span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D">But here’s where things get tricky/problematic with ArchivesSpace.   If I were to upload this EAD file into ArchivesSpace (i.e. not using the migration tool), then two paragraphs would be explicitly encoded in
 the database.  Here’s the JSON that you’ll get after an EAD import:</span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D">{</span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D">    "jsonmodel_type": "note_multipart",</span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D">    "subnotes": [</span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D">        {</span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D">            "jsonmodel_type": "note_text",</span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D">            "content": "</span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D; background:yellow"><p></span><span style="color:#1F497D">Thomas Turner, 1729-1793, was a shop-keeper, and for a time the school-master, in the village of East Hoathly in Sussex, England.
 He also became church-warden in 1757. From 1754 to 1765 Turner wrote the diary which forms the major part of the papers<span style="background:yellow">.</p></span></span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">\n        
</span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D; background:yellow"><p></span><span style="color:#1F497D">Further biographical information may be found in \n                <title ns2:type=\"simple\" render=\"italic\">The Diary of Thomas
 Turner of East Hoathly (1754-1765)</title>, an abridged edition edited by Florence Maris Turner (Mrs. Charles Lamb), great-great-granddaughter of the diarist, with an introduction by J. B. Priestly, published in 1925 by John Lane, the Bodly Head Ltd., London<span style="background:yellow">.</p></span>",</span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D">            "subnote_guid": "1ab692d612a83b056388d77fcba36872"</span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D">        }</span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D">    ],</span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D">    "type": "bioghist",</span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D">    "persistent_id": "ref11",</span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D">    "label": "THOMAS TURNER 1729-1793"</span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D">}</span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D">This is a considerable difference from what happens when using the migration tool.  Also, as I noted in my previous message, the ASpace user interface encourages encoding paragraphs explicitly since the p tag
 is available when a user types in the less-than sign (‘<’) within a notes field.</span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D">So, given these discrepancies with how paragraphs are handled in ArchivesSpace (as well as the AT-to-ASpace migration tool), what’s the best way for us to proceed? 
</span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D">It seems to me that we should proceed by updating all of our notes in the AT to have explicitly encoded paragraph elements so that our ASpace JSON values will look like the second example; doing this would ensure
 that our EAD files will export correctly right now.  However, I do not know what changes are happening in ArchivesSpace, so I’d like advice on this before we conduct our migration.  Is it intended that ArchiveSpace will manage both implicit paragraphs as well
 as explicitly encoded paragraphs?  Right now, ASpace will only manage the latter.  If that’s going to continue to be the case, then I think that a lot of users (AT users at least) will need assistance either pre- or post-migration to address this issue.  Does
 that make more sense?</span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Mark</span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:#212121"></span></p>
<div>
<div style="border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"; color:#212121">From:</span></b><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"; color:#212121">
</span><a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"">archivesspace_users_group-bounces@lyralists.lyrasis.org</span></a><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"; color:#212121">
 [</span><a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"">mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org</span></a><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"; color:#212121">]
<b>On Behalf Of </b>Chris Fitzpatrick<br>
<b>Sent:</b> Tuesday, July 29, 2014 4:26 AM<br>
<b>To:</b> Archivesspace Users Group<br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] AT > ASpace migration questions</span><span style="color:#212121"></span></p>
</div>
</div>
<p class="MsoNormal"><span style="color:#212121"> </span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:black"> </span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:black">Hi Mark,</span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:black"> </span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:black">Sorry this got lost in the tread...had another user ask about this and I wanted to follow up..</span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:black"> </span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:black">Yes, the ticket I have now is just for display.
</span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:black"> </span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:black">In regards to actually adding text into the note field, you're asking if line breaks could be converted into wrapping the blocks of text in <p> tags and added to the note's text? Or, are you just
 wanting the EAD exporter to do this to blocks of text? </span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:black"> </span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:black">b,chris. </span>
<span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:black"> </span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<div id="Signature">
<div name="divtagdefaultwrapper">
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt; color:black">Chris Fitzpatrick | Developer, ArchivesSpace<br>
Skype: chrisfitzpat  | Phone: 918.236.6048<br>
</span><a href="http://archivesspace.org/"><span style="font-size:10.0pt">http://archivesspace.org/</span></a><span style="color:#212121"></span></p>
</div>
</div>
</div>
</div>
<div>
<div class="MsoNormal" style="text-align:center" align="center"><span style="font-size:12.0pt; color:#212121">
<hr align="center" size="2" width="98%">
</span></div>
<div id="divRplyFwdMsg">
<p class="MsoNormal"><b><span style="color:black">From:</span></b><span style="color:black">
</span><a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_group-bounces@lyralists.lyrasis.org</a><span style="color:black"> <</span><a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_group-bounces@lyralists.lyrasis.org</a><span style="color:black">>
 on behalf of Custer, Mark <</span><a href="mailto:mark.custer@yale.edu">mark.custer@yale.edu</a><span style="color:black">><br>
<b>Sent:</b> Wednesday, July 23, 2014 4:24 PM<br>
<b>To:</b> Archivesspace Users Group<br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] AT > ASpace migration questions</span><span style="font-size:12.0pt; color:#212121">
</span><span style="color:#212121"></span></p>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt; color:#212121"> </span><span style="color:#212121"></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="color:#1F497D">To follow up on one point of this thread specifically, I wonder if there is any more clarification regarding Ed’s question about “Lengthy text in Scope & Contents Notes,” its corresponding user story,
</span><a href="https://www.pivotaltracker.com/s/projects/386247/stories/72606134">https://www.pivotaltracker.com/s/projects/386247/stories/72606134</a><span style="color:#1F497D">, and how this is going to be addressed in future releases of ArchivesSpace?
   </span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D">The above user story only applies to how this note
<i>displays in ArchivesSpace</i>, but what I need to address currently is how this note
<i>exports in the EAD</i>.  In the example at Pivotal Tracker, the note looks like this:</span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">This is a story.</span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D"> </span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">It has a break.</span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D"> </span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">Then it ends.</span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D">In version 1.0.9 (and earlier), that same note will exports like this in the EAD:</span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D"><p>This is a story. It has a break. Then it ends.</p></span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D"> </span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Is this going to be changed in the next release of ArchivesSpace, or should we update our AT database prior to the migration to ensure that the following is migrated into ArchivesSpace instead:</span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D"><p>This is a story.</p></span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D"><p>It has a break.</p></span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D"><p>Then it ends.</p></span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I ask this second question since it seems to be aligned with how ArchivesSpace handles mixing in EAD elements in general, since the paragraph element pops up as an option in the user interface after a user types
 in the less-than sign, < (see the attached screen shot).  In other words, if the user interface is expecting paragraphs to be encoded explicitly, I assume that ArchivesSpace does not have plans not to interpret double-line breaks as paragraph separations for
 the EAD export process as Archivists’ Toolkit does.  Is that correct?  </span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Furthermore, if the paragraphs are explicitly encoded in ArchivesSpace (which will ensure that the correct EAD is exported in the current version), will having them encoded explicitly break the EAD export for
 future versions of ArchivesSpace?</span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D">There are also at least two other hard-coded EAD issues in the AT that we’ll likely need to update prior to our migration (since if we don’t do these things the EAD will be invalid upon export from ArchivesSpace),
 which I’ll list here again just in case no one else has been considering these yet:</span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:#212121"></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-family:Symbol; color:#1F497D">·</span><span style="font-size:7.0pt; font-family:"Times New Roman","serif"; color:#1F497D">        
</span><span style="color:#1F497D">@target attributes in <ref> elements.  The last time that I checked and reported, the migration tool updates @id attributes, but not the @target attributes that link to those ids.</span><span style="color:#212121"></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-family:Symbol; color:#1F497D">·</span><span style="font-size:7.0pt; font-family:"Times New Roman","serif"; color:#1F497D">        
</span><span style="color:#1F497D">Hard-coded namespace prefixes for XLink will need to change from  ns2: (in the AT) to  xlink: (in ASpace) 
</span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Right now, though, I’m primarily concerned with this question of paragraphs, specifically with how these should be encoded in the ArchivesSpace database in light of the AT migration tool and import/export mechanisms
 of ArchivesSpace.</span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Mark</span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:#212121"></span></p>
<div>
<div style="border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"; color:#212121">From:</span></b><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"; color:#212121">
</span><a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"">archivesspace_users_group-bounces@lyralists.lyrasis.org</span></a><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"; color:#212121">
 [</span><a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"">mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org</span></a><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"; color:#212121">]
<b>On Behalf Of </b>Galloway, Ed<br>
<b>Sent:</b> Wednesday, July 23, 2014 9:17 AM<br>
<b>To:</b> Archivesspace Users Group<br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] AT > ASpace migration questions</span><span style="color:#212121"></span></p>
</div>
</div>
<p class="MsoNormal"><span style="color:#212121"> </span></p>
<p class="MsoNormal"><span style="color:#212121">Chris,</span></p>
<p class="MsoNormal"><span style="color:#212121"> </span></p>
<p class="MsoNormal"><span style="color:#212121">Thanks for your responses…let me try to answer back in
</span><span style="color:red">red </span><span style="color:#212121">below.</span></p>
<p class="MsoNormal"><span style="color:#212121"> </span></p>
<p class="MsoNormal"><span style="color:#212121">Ed</span></p>
<p class="MsoNormal"><span style="color:#212121"> </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="color:#212121">From:</span></b><span style="color:#212121">
</span><a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_group-bounces@lyralists.lyrasis.org</a><span style="color:#212121"> [</span><a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org</a><span style="color:#212121">]
<b>On Behalf Of </b>Chris Fitzpatrick<br>
<b>Sent:</b> Wednesday, July 23, 2014 6:31 AM<br>
<b>To:</b> Archivesspace Users Group<br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] AT > ASpace migration questions</span></p>
</div>
</div>
<p class="MsoNormal"><span style="color:#212121"> </span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:black">Hi Ed,</span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:black"> </span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:black">Glad to hear about your migration and thanks for letting us know about these issues...</span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:black">Some responses:</span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:black"> </span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:12.0pt; color:#4BA524; background:white">Agents do not display in the Public interface, meaning no Creators or Personal/Corporate names appear in the search results or as an option to
 browse; nothing displays when the “Names” category is selected. It says “No records,” but they’re there on the Staff side.</span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:12.0pt; color:black"><br>
Hm... For the agents to display, they need to be associated to a published resource. Do you have an agent that is associated to a published resource? Can you see that agent in the published resource on the public side?
</span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="color:red">If you mean is an agent (ie corporate name) linked to a resource (ie finding aid) from the Staff side, then
<u>yes</u> most definitely. All of our finding aids (almost 1000) have Creators or Personal/Corporate names that we created in AT and appear in our current online guides. But when we look at them in the Public ASpace view, none of them appear anywhere (but
 they are there in Staff).</span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="color:red"> </span><span style="color:#212121"></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="color:#4BA524">HTML markup does not display; instead it shows the mark-up itself (I believe this is a known ASpace bug and being addressed).</span><span style="color:#212121"></span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:black"> </span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:black">Which context is this in? Notes or titles? Also, be aware adding certain HTML to your data can make your EAD export invalid...</span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#212121"> </span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:red">Using the wrap-in tag feature in AT, we created italics fairly regularly for unittitles such as
</span><span style="font-family:"Calibri","sans-serif"; color:#212121"><title render=”italic”>Ed’s Book</title>.
</span><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:red">This markup was migrated exactly as you see it in my example. In other words, it doesn’t actually display in italics but we used the AT tools provided.</span><span style="font-size:10.0pt; font-family:"Calibri","sans-serif"; color:red">
</span><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:red">It happens anywhere we used <emph> tags whether it was unittitle or scope notes or anywhere else. We did not get any EAD export errors.</span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:#212121"> </span></p>
<p><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#212121"> </span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-size:7.0pt; font-family:"Calibri","sans-serif"; color:#4BA524">  
</span><span style="font-family:"Calibri","sans-serif"; color:#4BA524">Similarly though, if a <unittitle> begins with an <emph> tag, the title does not display at all and neither does any of its children. If for example, the name of a subseries started with
 an <emph> tag, none of the folders in that subseries display.</span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:black"> </span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:black">This is a known issue...https://www.pivotaltracker.com/story/show/75502994</span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:#212121"> </span></p>
<p><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:red">OK</span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:#212121"> </span></p>
<p><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#212121"> </span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt; font-family:Symbol; color:black">·</span><span style="font-size:7.0pt; font-family:"Times New Roman","serif"; color:#4BA524">        
</span><span style="font-size:12.0pt; color:#4BA524">Lengthy text in Scope & Contents Notes (eg) do not show paragraph breaks, but instead display as one long paragraph. When viewed on the Staff side, it does format properly when viewed as Formatted Text (not
 Raw).</span><span style="font-size:12.0pt; font-family:Symbol; color:black"><br>
<br>
</span><span style="font-size:12.0pt; color:black">A feature request has been added for this..
</span><a href="https://www.pivotaltracker.com/story/show/72606134"><span style="font-size:12.0pt">https://www.pivotaltracker.com/story/show/72606134</span></a><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#212121"> </span></p>
<p class="MsoNormal"><span style="color:red">Ok</span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt; font-family:Symbol; color:black"><br>
</span><span style="font-size:7.0pt; font-family:"Times New Roman","serif"; color:black">    
</span><span style="color:#212121"></span></p>
<p><span style="font-size:7.0pt; font-family:"Calibri","sans-serif"; color:#4BA524">   
</span><span style="font-family:"Calibri","sans-serif"; color:#4BA524">External links (URLs) we’ve inserted in a S&C note do not actually link out.</span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:black"> </span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:black">How are you adding these urls to the note?
</span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:#212121"> </span></p>
<p><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:red">Using the AT wrap-in tag feature <extref> so the markup looks like this: “Digital reproductions of the collection are available <extref href="</span><a href="http://digital.library.pitt.edu/images/pittsburgh/cityphotographer.html"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"">http://digital.library.pitt.edu/images/pittsburgh/cityphotographer.html</span></a><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:red">">online</extref>.”
 The links work just fine in our current online guides.</span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:#212121"> </span></p>
<p><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#212121"> </span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-size:7.0pt; font-family:"Calibri","sans-serif"; color:#4BA524">    
</span><span style="font-family:"Calibri","sans-serif"; color:#4BA524">Perform an Advanced Search and view first set of results; then advance to next page of results. This second set of results is not based on the original search but appears to be the results
 of searching everything!</span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:black"> </span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:black">Yikes. I just replicated that. Definitely a bug...hard to believe nobody has caught that one yet. Make a ticket for that here :</span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><a href="https://www.pivotaltracker.com/story/show/75503592" id="lnk319932"><span style="font-family:"Calibri","sans-serif"">https://www.pivotaltracker.com/story/show/75503592</span></a><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:black"> </span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p style="margin-bottom:12.0pt"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:red">Ok…glad we could help!</span><span style="font-family:"Calibri","sans-serif"; color:#212121">
</span></p>
<p><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#212121"> </span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-size:7.0pt; font-family:"Calibri","sans-serif"; color:#4BA524"> </span><span style="font-family:"Calibri","sans-serif"; color:#4BA524">Search does not highlight your search terms. Can it?</span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:black"> </span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:black">Short answer is yes. This is actually a Solr configuration that would need to be made to return highlight text in the search results.
</span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:black">However, there is a feature request to have this native  in the application here :
</span><a href="https://www.pivotaltracker.com/story/show/66505844"><span style="font-family:"Calibri","sans-serif"">https://www.pivotaltracker.com/story/show/66505844</span></a><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:#212121"> </span></p>
<p><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:red">Ok</span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#212121"> </span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:black"> </span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:#4BA524">There is no Go to Next Folder (eg Component) feature; in other words when viewing any folder, it would be nice to simply click a button to see the next (or preceding) folder (or item).</span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:black"> </span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:black">Ok, so is this in the public interface only? So, if youre looking at a resource in a folder, you'd like a button just to take you to the next folder rather than having to go back to the top level
 view and select the next folder? </span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:#212121"> </span></p>
<p><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:red">Yes in the Public interface. Yes most definitely!
</span><span style="font-size:11.0pt; font-family:Wingdings; color:red">J</span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:red"> </span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:red">Thanks!</span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#212121"> </span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:black">best, chris. </span>
<span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:black"> </span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<p><span style="font-family:"Calibri","sans-serif"; color:black"> </span><span style="font-family:"Calibri","sans-serif"; color:#212121"></span></p>
<div id="Signature">
<div name="divtagdefaultwrapper">
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt; color:black">Chris Fitzpatrick | Developer, ArchivesSpace<br>
Skype: chrisfitzpat  | Phone: 918.236.6048<br>
</span><a href="http://archivesspace.org/"><span style="font-size:10.0pt">http://archivesspace.org/</span></a><span style="color:#212121"></span></p>
</div>
</div>
</div>
</div>
<div>
<div class="MsoNormal" style="text-align:center" align="center"><span style="font-size:12.0pt; color:#212121">
<hr align="center" size="2" width="98%">
</span></div>
<div id="divRplyFwdMsg">
<p class="MsoNormal"><b><span style="color:black">From:</span></b><span style="color:black">
</span><a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_group-bounces@lyralists.lyrasis.org</a><span style="color:black"> <</span><a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_group-bounces@lyralists.lyrasis.org</a><span style="color:black">>
 on behalf of Galloway, Ed <</span><a href="mailto:edwardg@pitt.edu">edwardg@pitt.edu</a><span style="color:black">><br>
<b>Sent:</b> Tuesday, July 22, 2014 3:32 PM<br>
<b>To:</b> Archivesspace Users Group<br>
<b>Subject:</b> [Archivesspace_Users_Group] AT > ASpace migration questions</span><span style="font-size:12.0pt; color:#212121">
</span><span style="color:#212121"></span></p>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt; color:#212121"> </span><span style="color:#212121"></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="color:#212121">All,</span></p>
<p class="MsoNormal"><span style="color:#212121"> </span></p>
<p class="MsoNormal"><span style="color:#212121">The University of Pittsburgh has successfully migrated its data from AT to ASpace, meaning we have worked out any transfer problems so 100% of our records migrate. Now we are carefully reviewing the data in the
 Public ASpace interface and have observed the following which we’d like comments on:</span></p>
<p class="MsoNormal"><span style="color:#212121"> </span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-family:Symbol; color:#212121">·</span><span style="font-size:7.0pt; font-family:"Times New Roman","serif"; color:#212121">        
</span><span style="color:#212121">Agents do not display in the Public interface, meaning no Creators or Personal/Corporate names appear in the search results or as an option to browse; nothing displays when the “Names” category is selected. It says “No records,”
 but they’re there on the Staff side.</span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-family:Symbol; color:#212121">·</span><span style="font-size:7.0pt; font-family:"Times New Roman","serif"; color:#212121">        
</span><span style="color:#212121">HTML markup does not display; instead it shows the mark-up itself (I believe this is a known ASpace bug and being addressed).</span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-family:Symbol; color:#212121">·</span><span style="font-size:7.0pt; font-family:"Times New Roman","serif"; color:#212121">        
</span><span style="color:#212121">Similarly though, if a <unittitle> begins with an <emph> tag, the title does not display at all and neither does any of its children. If for example, the name of a subseries started with an <emph> tag, none of the folders
 in that subseries display.</span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-family:Symbol; color:#212121">·</span><span style="font-size:7.0pt; font-family:"Times New Roman","serif"; color:#212121">        
</span><span style="color:#212121">Lengthy text in Scope & Contents Notes (eg) do not show paragraph breaks, but instead display as one long paragraph. When viewed on the Staff side, it does format properly when viewed as Formatted Text (not Raw).</span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-family:Symbol; color:#212121">·</span><span style="font-size:7.0pt; font-family:"Times New Roman","serif"; color:#212121">        
</span><span style="color:#212121">External links (URLs) we’ve inserted in a S&C note do not actually link out.</span></p>
<p class="MsoNormal"><span style="color:#212121"> </span></p>
<p class="MsoNormal"><span style="color:#212121">Bug?</span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-family:Symbol; color:#212121">·</span><span style="font-size:7.0pt; font-family:"Times New Roman","serif"; color:#212121">        
</span><span style="color:#212121">Perform an Advanced Search and view first set of results; then advance to next page of results. This second set of results is not based on the original search but appears to be the results of searching everything!</span></p>
<p class="MsoNormal"><span style="color:#212121"> </span></p>
<p class="MsoNormal"><span style="color:#212121">Interface questions:</span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-family:Symbol; color:#212121">·</span><span style="font-size:7.0pt; font-family:"Times New Roman","serif"; color:#212121">        
</span><span style="color:#212121">Search does not highlight your search terms. Can it?</span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-family:Symbol; color:#212121">·</span><span style="font-size:7.0pt; font-family:"Times New Roman","serif"; color:#212121">        
</span><span style="color:#212121">There is no Go to Next Folder (eg Component) feature; in other words when viewing any folder, it would be nice to simply click a button to see the next (or preceding) folder (or item).</span></p>
<p class="MsoNormal"><span style="color:#212121"> </span></p>
<p class="MsoNormal"><span style="color:#212121">I would appreciate any feedback you can give me. We’re at the stage of determining what we need to address versus what is a bug or other issue that the ASpace developers need to address.</span></p>
<p class="MsoNormal"><span style="color:#212121"> </span></p>
<p class="MsoNormal"><span style="color:#212121">Thanks, Ed</span></p>
<p class="MsoNormal"><span style="color:#212121"> </span></p>
<p class="MsoNormal"><span style="font-size:10.0pt; color:#212121">Edward A. Galloway<br>
Head, Archives Service Center</span><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt; color:#212121">University Library System<br>
University of Pittsburgh<br>
412-648-5901</span><span style="color:#212121"></span></p>
<p class="MsoNormal"><a href="http://www.facebook.com/pittarchives"><span style="font-size:10.0pt; color:blue">facebook.com/pittarchives</span></a><span style="color:#212121"></span></p>
<p class="MsoNormal"><a href="http://pittarchives.tumblr.com/"><span style="font-size:10.0pt; color:blue">pittarchives.tumblr.com</span></a><span style="color:#212121"></span></p>
<p class="MsoNormal"><span style="color:#212121"> </span></p>
<p class="MsoNormal"><span style="color:#212121"> </span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>