<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 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Segoe UI";
panose-1:2 11 5 2 4 2 4 2 2 3;}
@font-face
{font-family:o365IconsIE8;}
@font-face
{font-family:o365IconsMouse;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p
{mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
p.ms-cui-menu, li.ms-cui-menu, div.ms-cui-menu
{mso-style-name:ms-cui-menu;
mso-style-priority:99;
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
{mso-style-name:ms-cui-menusection-title;
mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
display:none;}
p.ms-cui-ctl, li.ms-cui-ctl, div.ms-cui-ctl
{mso-style-name:ms-cui-ctl;
mso-style-priority:99;
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
{mso-style-name:ms-cui-ctl-on;
mso-style-priority:99;
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
{mso-style-name:ms-cui-img-cont-float;
mso-style-priority:99;
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
{mso-style-name:ms-cui-smenu-inner;
mso-style-priority:99;
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
{mso-style-name:ms-owa-paste-option-icon;
mso-style-priority:99;
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
{mso-style-name:ms-rtepasteflyout-option;
mso-style-priority:99;
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
{mso-style-name:ms-cui-menusection;
mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.wf, li.wf, div.wf
{mso-style-name:wf;
mso-style-priority:99;
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
{mso-style-name:wf-family-owa;
mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:o365IconsMouse;}
p.msochpdefault, li.msochpdefault, div.msochpdefault
{mso-style-name:msochpdefault;
mso-style-priority:99;
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
{mso-style-name:wf-owa-play-large;
mso-style-priority:99;
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
{mso-style-name:wf-size-play-large;
mso-style-priority:99;
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
{mso-style-name:wf-owa-triangle-down-small;
mso-style-priority:99;
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
{mso-style-name:wf-family-owa1;
mso-style-priority:99;
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
{mso-style-name:wf-owa-play-large1;
mso-style-priority:99;
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
{mso-style-name:wf-owa-play-large2;
mso-style-priority:99;
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
{mso-style-name:wf-size-play-large1;
mso-style-priority:99;
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
{mso-style-name:wf-size-play-large2;
mso-style-priority:99;
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
{mso-style-name:wf-owa-triangle-down-small1;
mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:#666666;}
span.emailstyle17
{mso-style-name:emailstyle17;
font-family:"Calibri","sans-serif";
color:windowtext;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.EmailStyle41
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.EmailStyle42
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.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;}
/* List Definitions */
@list l0
{mso-list-id:1597789292;
mso-list-type:hybrid;
mso-list-template-ids:-437888212 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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 bgcolor="white" lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<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,
<a href="https://www.pivotaltracker.com/s/projects/386247/stories/72606134">https://www.pivotaltracker.com/s/projects/386247/stories/72606134</a>, and how this is going to be addressed in future releases of ArchivesSpace? <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></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:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">This is a story.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">It has a break.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">Then it ends.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></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:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></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><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D"><o:p> </o:p></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:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D"><p>This is a story.</p><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D"><p>It has a break.</p><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D"><p>Then it ends.</p><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></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? <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></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?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></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:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><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.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">Hard-coded namespace prefixes for XLink will need to change from ns2: (in the AT) to xlink: (in ASpace)
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></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.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Mark<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></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>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<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Chris,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks for your responses…let me try to answer back in <span style="color:red">
red </span>below.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Ed<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> <a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">
archivesspace_users_group-bounces@lyralists.lyrasis.org</a> [<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org</a>]
<b>On Behalf Of </b>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<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p><span style="font-family:"Calibri","sans-serif";color:black">Hi Ed,<o:p></o:p></span></p>
<p><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></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...<o:p></o:p></span></p>
<p><span style="font-family:"Calibri","sans-serif";color:black">Some responses:<o:p></o:p></span></p>
<p><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></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="font-size:12.0pt;background:white"><o:p></o:p></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?
<o:p></o:p></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).<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="color:red"><o:p> </o:p></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:black"><o:p></o:p></span></p>
<p><span style="font-family:"Calibri","sans-serif";color:black"> <o:p></o:p></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...<o:p></o:p></span></p>
<p><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p> </o:p></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><title render=”italic”>Ed’s Book</title>. <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-size:10.0pt;font-family:"Calibri","sans-serif";color:red"><o:p></o:p></span></p>
<p><span style="font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p><span style="font-size:7.0pt;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:black"><o:p></o:p></span></p>
<p><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
<p><span style="font-family:"Calibri","sans-serif";color:black">This is a known issue...https://www.pivotaltracker.com/story/show/75502994<o:p></o:p></span></p>
<p><span style="font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:red">OK<o:p></o:p></span></p>
<p><span style="font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p> </o:p></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..
<a href="https://www.pivotaltracker.com/story/show/72606134">https://www.pivotaltracker.com/story/show/72606134</a></span><span style="font-size:12.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:red">Ok<o:p></o:p></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="font-size:12.0pt;color:black"><o:p></o:p></span></p>
<p><span style="font-size:7.0pt;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:black"><o:p></o:p></span></p>
<p><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
<p><span style="font-family:"Calibri","sans-serif";color:black">How are you adding these urls to the note?
<o:p></o:p></span></p>
<p><span style="font-family:"Calibri","sans-serif""><o:p> </o:p></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="<a href="http://digital.library.pitt.edu/images/pittsburgh/cityphotographer.html">http://digital.library.pitt.edu/images/pittsburgh/cityphotographer.html</a>">online</extref>.”
The links work just fine in our current online guides.<o:p></o:p></span></p>
<p><span style="font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p><span style="font-size:7.0pt;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:black"><o:p></o:p></span></p>
<p><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></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 :<o:p></o:p></span></p>
<p><span style="font-family:"Calibri","sans-serif";color:black"><a href="https://www.pivotaltracker.com/story/show/75503592" id="lnk319932">https://www.pivotaltracker.com/story/show/75503592</a><o:p></o:p></span></p>
<p><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></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"">
<o:p></o:p></span></p>
<p><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p> </o:p></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:black"><o:p></o:p></span></p>
<p><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></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.
<o:p></o:p></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 :
<a href="https://www.pivotaltracker.com/story/show/66505844">https://www.pivotaltracker.com/story/show/66505844</a><o:p></o:p></span></p>
<p><span style="font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:red">Ok<o:p></o:p></span></p>
<p><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></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:black"><o:p></o:p></span></p>
<p><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></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? <o:p></o:p></span></p>
<p><span style="font-family:"Calibri","sans-serif""><o:p> </o:p></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-size:11.0pt;font-family:"Calibri","sans-serif";color:red"><o:p></o:p></span></p>
<p><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:red"><o:p> </o:p></span></p>
<p><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:red">Thanks!<o:p></o:p></span></p>
<p><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p><span style="font-family:"Calibri","sans-serif";color:black">best, chris. <o:p>
</o:p></span></p>
<p><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
<p><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></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>
<a href="http://archivesspace.org/">http://archivesspace.org/</a><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
<div>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:12.0pt;color:#212121">
<hr size="2" width="98%" align="center">
</span></div>
<div id="divRplyFwdMsg">
<p class="MsoNormal"><b><span style="color:black">From:</span></b><span style="color:black">
<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_group-bounces@lyralists.lyrasis.org</a> <<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_group-bounces@lyralists.lyrasis.org</a>>
on behalf of Galloway, Ed <<a href="mailto:edwardg@pitt.edu">edwardg@pitt.edu</a>><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">
<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:#212121"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="color:#212121">All,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#212121"> <o:p></o:p></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:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#212121"> <o:p></o:p></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.<o:p></o:p></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).<o:p></o:p></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.<o:p></o:p></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).<o:p></o:p></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.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#212121"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#212121">Bug?<o:p></o:p></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!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#212121"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#212121">Interface questions:<o:p></o:p></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?<o:p></o:p></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).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#212121"> <o:p></o:p></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.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#212121"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#212121">Thanks, Ed<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#212121"> <o:p></o:p></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"><o:p></o:p></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"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#212121"><a href="http://www.facebook.com/pittarchives"><span style="color:blue">facebook.com/pittarchives</span></a></span><span style="color:#212121"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#212121"><a href="http://pittarchives.tumblr.com/"><span style="color:blue">pittarchives.tumblr.com</span></a></span><span style="color:#212121"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#212121"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#212121"> <o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</body>
</html>