<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div apple-content-edited="true">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.</div>
<div>
<div><br>
</div>
<div>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.</div>
<div>
<div><br>
</div>
<div>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. </div>
<div><br>
</div>
<div><a href="http://ckeditor.com">http://ckeditor.com</a>/</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>Chris Prom</div>
</div>
<div><br>
</div>
<div>Begin forwarded message:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;">
<span style="font-family:'Helvetica'; color:rgba(0, 0, 0, 1.0);"><b>From: </b></span><span style="font-family:'Helvetica';">Trevor Thornton <<a href="mailto:hellotrevorthornton@gmail.com">hellotrevorthornton@gmail.com</a>><br>
</span></div>
<div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;">
<span style="font-family:'Helvetica'; color:rgba(0, 0, 0, 1.0);"><b>Subject: </b>
</span><span style="font-family:'Helvetica';"><b>Re: [archivesspace] <title><emph render="italic"></b><br>
</span></div>
<div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;">
<span style="font-family:'Helvetica'; color:rgba(0, 0, 0, 1.0);"><b>Date: </b></span><span style="font-family:'Helvetica';">October 15, 2014 at 11:19:42 AM CDT<br>
</span></div>
<div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;">
<span style="font-family:'Helvetica'; color:rgba(0, 0, 0, 1.0);"><b>To: </b></span><span style="font-family:'Helvetica';"><a href="mailto:archivesspace@googlegroups.com">archivesspace@googlegroups.com</a><br>
</span></div>
<div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;">
<span style="font-family:'Helvetica'; color:rgba(0, 0, 0, 1.0);"><b>Reply-To: </b>
</span><span style="font-family:'Helvetica';"><a href="mailto:archivesspace@googlegroups.com">archivesspace@googlegroups.com</a><br>
</span></div>
<br>
<div>
<div dir="ltr">
<div>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.<br>
<br>
</div>
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).<br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Oct 15, 2014 at 11:10 AM, Al Matthews <span dir="ltr">
<<a href="mailto:prolepsis@gmail.com" target="_blank">prolepsis@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Wondering too, how you resolved, Trevor.</div>
<div class="HOEnZb">
<div class="h5">
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Oct 15, 2014 at 11:07 AM, Al Matthews <span dir="ltr">
<<a href="mailto:prolepsis@gmail.com" target="_blank">prolepsis@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">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.
<div><br>
</div>
<div>Is direct print-to-screen of mixed tag content, from a supported migration, really not a bug?</div>
</div>
<div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Oct 15, 2014 at 10:15 AM, Trevor Thornton <span dir="ltr">
<<a href="mailto:hellotrevorthornton@gmail.com" target="_blank">hellotrevorthornton@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">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><br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote"><span>On Wed, Oct 15, 2014 at 9:25 AM, Al Matthews <span dir="ltr">
<<a href="mailto:prolepsis@gmail.com" target="_blank">prolepsis@gmail.com</a>></span> wrote:<br>
</span>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span>
<div dir="ltr">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.
<div><br>
</div>
<div>Thanks much,</div>
<div><br>
</div>
<div>Al</div>
</div>
</span><span><font color="#888888"><span><font color="#888888">
<div><br class="webkit-block-placeholder">
</div>
-- <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>.</font></span><span><br>
For more options, visit <a href="https://groups.google.com/d/optout" target="_blank">
https://groups.google.com/d/optout</a>.<br>
</span></font></span></blockquote>
</div>
<br>
</div>
<div>
<div><br class="webkit-block-placeholder">
</div>
-- <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>.<br>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<div><br class="webkit-block-placeholder">
</div>
-- <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>.<br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<div><br class="webkit-block-placeholder">
</div>
-- <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>.<br>
</div>
</blockquote>
</div>
<br>
</body>
</html>