<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: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)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.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";}
span.EmailStyle17
{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;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I agree with Chris (and related concerns that have been brought up by Mark Custer and others). I would like to second his request to have our representatives
on the user and technical groups to do some deep thinking about error-resistant ways to handle mixed content/formatting.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Maureen<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Maureen Callahan<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#404040">Archivist, Metadata Specialist<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#404040">Manuscripts & Archives<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#404040">Yale University Library<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#548DD4"><a href="mailto:maureen.callahan@yale.edu"><span style="color:#548DD4">maureen.callahan@yale.edu</span></a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#404040">203.432.3627<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#7F7F7F"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#404040">Webpage:</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#7F7F7F">
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#548DD4"><a href="web.library.yale.edu/mssa"><span style="color:#548DD4">web.library.yale.edu/mssa</span></a></span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#7F7F7F"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#404040">Collections:</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#7F7F7F">
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#548DD4"><a href="drs.library.yale.edu"><span style="color:#548DD4">drs.library.yale.edu</span></a></span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#7F7F7F"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #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>Prom, Christopher John<br>
<b>Sent:</b> Wednesday, October 15, 2014 12:56 PM<br>
<b>To:</b> Archivesspace Users Group<br>
<b>Subject:</b> [Archivesspace_Users_Group] Fwd: [archivesspace] <title><emph render="italic"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">I’d like to ask that the techical and user groups look at issues relate to the wrap in tag editor seriously as part of planning future work, not as a one off focusing on specific bugs, but on the assumption that we should review alternatives
for the core architecture.<o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I have always been skeptical of having a purpose built editor for this editing and storing EAD or formatting in the DB. Using the wrap-in-tage feature is very difficult in our staff testing, and there seem to be a huge number of support
requests which is taking time away from more important (IMHO) issues.<o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">As a design consideration, open source WYSIWYG editors such as ckeditor seem like a much a better way to accomplish what users want to accomplish. We would also benefit from a broader community that has already hashed out most of the
difficult design issues for formatting markup, and we could extend this library in other ways, for example to include the sematic markup in a more usable interface than the wrap in tag editor. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><a href="http://ckeditor.com">http://ckeditor.com</a>/<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I am not saying this is the ‘solution’ the problem, but it does seem to me that something is fundamentally broken at an architecture level here, and we should evaluate alternate strategies, given the large number or bugs and feature requests
related to wrap-in-tag editor.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Chris Prom<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Begin forwarded message:<o:p></o:p></p>
</div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<div>
<p class="MsoNormal"><b><span style="font-family:"Helvetica","sans-serif"">From: </span>
</b><span style="font-family:"Helvetica","sans-serif"">Trevor Thornton <<a href="mailto:hellotrevorthornton@gmail.com">hellotrevorthornton@gmail.com</a>></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-family:"Helvetica","sans-serif"">Subject: Re: [archivesspace] <title><emph render="italic"></span></b><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-family:"Helvetica","sans-serif"">Date: </span>
</b><span style="font-family:"Helvetica","sans-serif"">October 15, 2014 at 11:19:42 AM CDT</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-family:"Helvetica","sans-serif"">To: </span>
</b><span style="font-family:"Helvetica","sans-serif""><a href="mailto:archivesspace@googlegroups.com">archivesspace@googlegroups.com</a></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-family:"Helvetica","sans-serif"">Reply-To:
</span></b><span style="font-family:"Helvetica","sans-serif""><a href="mailto:archivesspace@googlegroups.com">archivesspace@googlegroups.com</a></span><o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">We didn't resolve it - we removed the XML tags from the titles prior to the final migration (I wrote a script to do this over the copy of the AT database we used for the migration). Not a solution, just an elimination
of the problem.<o:p></o:p></p>
</div>
<p class="MsoNormal">Given that XML is permitted within many elements for which AS doesn't provide support for mixed content, I'd say that it seems like an oversight in the design, not a bug per se, but a missing feature that would better support a fairly common
practice (or a legacy practice that persists in the data).<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Wed, Oct 15, 2014 at 11:10 AM, Al Matthews <<a href="mailto:prolepsis@gmail.com" target="_blank">prolepsis@gmail.com</a>> wrote:<o:p></o:p></p>
<div>
<p class="MsoNormal">Wondering too, how you resolved, Trevor.<o:p></o:p></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Wed, Oct 15, 2014 at 11:07 AM, Al Matthews <<a href="mailto:prolepsis@gmail.com" target="_blank">prolepsis@gmail.com</a>> wrote:<o:p></o:p></p>
<div>
<p class="MsoNormal">I follow some of the logic for the feature -> bug -> feature trajectory here: invisible is bad. But we experience this (or perhaps, something vaguely similar) with <chronlist><chronitem> as well.
<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Is direct print-to-screen of mixed tag content, from a supported migration, really not a bug?<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Wed, Oct 15, 2014 at 10:15 AM, Trevor Thornton <<a href="mailto:hellotrevorthornton@gmail.com" target="_blank">hellotrevorthornton@gmail.com</a>> wrote:<o:p></o:p></p>
<div>
<p class="MsoNormal">We had the same problem when we migrated from AT (where there was XML in some of the titles, especially for components). Looks like this feature has already been requested:<br>
<a href="https://www.pivotaltracker.com/s/projects/386247/stories/74516352" target="_blank">https://www.pivotaltracker.com/s/projects/386247/stories/74516352</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Wed, Oct 15, 2014 at 9:25 AM, Al Matthews <<a href="mailto:prolepsis@gmail.com" target="_blank">prolepsis@gmail.com</a>> wrote:<o:p></o:p></p>
<div>
<p class="MsoNormal">Hello. What I've indicated in subject line, <title><emph render="italic">, appears to be valid EAD per <a href="http://www.loc.gov/ead/tglib/elements/emph.html" target="_blank">http://www.loc.gov/ead/tglib/elements/emph.html</a>. However,
based on some quick testing, there does not appear to be a way to make wrap-and-tag appear in Basic Information, Title, at least at item level. Moreover, <emph> is printed directly. Please tell me what I'm missing before I mistakenly report a bug.
<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thanks much,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Al<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="color:#888888"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span style="color:#888888">-- <br>
You received this message because you are subscribed to the Google Groups "ArchivesSpace" group.<br>
To unsubscribe from this group and stop receiving emails from it, send an email to
<a href="mailto:archivesspace+unsubscribe@googlegroups.com" target="_blank">archivesspace+unsubscribe@googlegroups.com</a>.<br>
For more options, visit <a href="https://groups.google.com/d/optout" target="_blank">
https://groups.google.com/d/optout</a>.</span><o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">-- <br>
You received this message because you are subscribed to a topic in the Google Groups "ArchivesSpace" group.<br>
To unsubscribe from this topic, visit <a href="https://groups.google.com/d/topic/archivesspace/yQClbTl4ZpI/unsubscribe" target="_blank">
https://groups.google.com/d/topic/archivesspace/yQClbTl4ZpI/unsubscribe</a>.<br>
To unsubscribe from this group and all its topics, send an email to <a href="mailto:archivesspace+unsubscribe@googlegroups.com" target="_blank">
archivesspace+unsubscribe@googlegroups.com</a>.<br>
For more options, visit <a href="https://groups.google.com/d/optout" target="_blank">
https://groups.google.com/d/optout</a>.<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">-- <br>
You received this message because you are subscribed to the Google Groups "ArchivesSpace" group.<br>
To unsubscribe from this group and stop receiving emails from it, send an email to
<a href="mailto:archivesspace+unsubscribe@googlegroups.com" target="_blank">archivesspace+unsubscribe@googlegroups.com</a>.<br>
For more options, visit <a href="https://groups.google.com/d/optout" target="_blank">
https://groups.google.com/d/optout</a>.<o:p></o:p></p>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">-- <br>
You received this message because you are subscribed to the Google Groups "ArchivesSpace" group.<br>
To unsubscribe from this group and stop receiving emails from it, send an email to
<a href="mailto:archivesspace+unsubscribe@googlegroups.com">archivesspace+unsubscribe@googlegroups.com</a>.<br>
For more options, visit <a href="https://groups.google.com/d/optout">https://groups.google.com/d/optout</a>.<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>