<div dir="ltr">The EAD3 exporter we're working on will attempt to convert mixed content stored in the database to valid EAD3, either by renaming tags/attributes, adding new elements when appropriate (e.g. wrapping contents of controlled access elements in <part>), or "unwrapping" tagged content when a suitable substitution can't be easily determined. It's highly unlikely that it will account for every situation in every repository, but the output should have far fewer validation problems than it would otherwise, and there should be opportunities for incremental improvement to this functionality in the future.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Sep 11, 2017 at 11:40 AM, Bowers, Kate A. <span dir="ltr"><<a href="mailto:kate_bowers@harvard.edu" target="_blank">kate_bowers@harvard.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="white" lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="m_-1914205575060922715WordSection1">
<p class="MsoNormal"><span style="color:#1f497d">Mark:<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">This is a great summary of the issues, and because we have all kinds of mixed content migrated into AS in unit titles, I can see that <cringe>lots</cringe> of our EAD3 from AS will be invalid. <sigh/><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">Kate<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></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" target="_blank">archivesspace_users_group-<wbr>bounces@lyralists.lyrasis.org</a> [mailto:<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" target="_blank">archivesspace_users_<wbr>group-bounces@lyralists.<wbr>lyrasis.org</a>]
<b>On Behalf Of </b>Custer, Mark<br>
<b>Sent:</b> Thursday, September 07, 2017 4:49 PM</p><div><div class="h5"><br>
<b>To:</b> Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org" target="_blank">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a>><br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] Pointer to choices for formatting the title of an archival object, such as an article title<u></u><u></u></div></div><p></p>
</div>
</div><div><div class="h5">
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Kari, all:<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">I’d also add that even though the ArchivesSpace note fields look like they can support EAD markup (and proclaim to be “Mixed Content Enabled”), it’s not really full-blown support like you’d get with an XML editor or a WYSIWYG interface.
For example, if I use the current tag-suggestion feature to add a “title” element within a note, there’s no indication in the interface that I can then add an “emph” element child, or even an empty “lb” element child, etc. If you do, fine, then you’ll still
wind up with valid EAD 2002 exports. But if you add a “persname” child here, ASpace isn’t going to say anything is wrong, but you’ve just invalided your EAD since EAD2002 doesn’t permit “persname” within a “title” element. Or if I just make up a tag name,
like “<whathaveidonenow></<wbr>whathaveidonenow>”, everything will still look fine (and be highlighted in green) in ASpace.
<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">All that said, as a literary archive, the Beinecke uses that “title” tag a lot, and it’s often used in the title fields of ASpace. So, locally we do permit mixed content for a few things that EAD allows, but definitely not everything
(even though you <i>could</i> add “title” element to container elements in EAD2002, that is definitely not allowed by our best practices!!!
<span style="font-family:Wingdings">J</span>). That said, we don’t currently rely on ASpace to ensure that we’re following those best practices right now since we don’t (yet) have a local-best-practices-<wbr>validation button in ASpace, so for now we still ensure
that our best practices are being followed by having EAD files exported and validated against a Schematron file.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">So Kari, I guess that’s a longwinded way of saying two things:<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal">At Yale, we’re moving toward restricting the elements that are allowed in ASpace’s title fields, most likely down to just two: “title” and “emph”, even though ASpace does not encourage entering any data
there. Before ASpace, we permitted 16 different elements here, although most of those were rarely if ever used.<u></u><u></u></li><li class="MsoNormal">Be wary of adding mixed-content elements to the ASpace notes, as well! The wrap feature is limited, and it doesn’t preclude folks from typing in anything they want (including HTML, MODS, PREMIS, whatever
their poison), including just made up stuff that will still look like it’s valid as long as the start tag name matches the end tag. Usually that’s pretty harmless… but typos. I haven’t yet figured out what limited elements of EAD that we should support within
ASpace notes moving forward, but that’s likely going to depend on the work that Noah is doing with Trevor to enable EAD3 support, since I’d like to start exporting valid EAD3 ASAP.<u></u><u></u></li></ul>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Mark<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">p.s. here’s a sample EAD export that illustrates the point about notes + the Mixed Content Enable feature in ASpace:<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal" style="background:white;text-autospace:none"><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:black;background:white">
</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#000096;background:white"><scopecontent></span><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:black;background:white"><br>
</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#000096;background:white"><head></span><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:black;background:white">Scope
and Contents</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#000096;background:white"></head></span><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:black;background:white"><br>
</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#000096;background:white"><p><title></span><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:black;background:white">title
with an </span><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#000096;background:white"><emph></span><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:black;background:white">emph</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#000096;background:white"></emph></title></span><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:black;background:white">;
all legal</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#000096;background:white"></p></span><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:black;background:white"><br>
</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#000096;background:white"><p></span><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:black;background:white">type
and then a </span><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#000096;background:white"><title></span><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:black;background:white">title
and a </span><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#000096;background:white"><persname></span><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:black;background:white">persname</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#000096;background:white"></persname><<wbr>/title></span><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:black;background:white">;
not so fast, 'cause that's invalid according to EAD2002.</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#000096;background:white"></p></span><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:black;background:white"><br>
</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#000096;background:white"><p><whathaveidonenow></span><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:black;background:white">but
seriously, someone might type in a tag name that looks like EAD, even though it’s not; and everything looks fine and valid in ASpace.</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#000096;background:white"></whathaveidonenow</p></span><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:black;background:white"><br>
</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#000096;background:white"></scopecontent></span><span style="font-size:12.0pt;font-family:"Times New Roman",serif;background:white"><u></u><u></u></span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><u></u> <u></u></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" target="_blank">
archivesspace_users_group-<wbr>bounces@lyralists.lyrasis.org</a> [<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" target="_blank">mailto:archivesspace_users_<wbr>group-bounces@lyralists.<wbr>lyrasis.org</a>]
<b>On Behalf Of </b>Noah Huffman<br>
<b>Sent:</b> Thursday, 07 September, 2017 4:13 PM<br>
<b>To:</b> Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org" target="_blank">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a>><br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] Pointer to choices for formatting the title of an archival object, such as an article title<u></u><u></u></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><span style="color:#1f497d">Hi Kari,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">Just to add to Dave’s comments. We’ve been doing some testing of a new EAD3 exporter for ArchivesSpace and mixed content tagging creates all sorts or complications for producing valid EAD3 exports when tags
stored in ArchivesSpace note fields and title fields are valid EAD2002 but not valid EAD3.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">-Noah<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial Narrow",sans-serif;color:#404040"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial Narrow",sans-serif;color:#404040">================<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial Narrow",sans-serif;color:#404040">Noah Huffman<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial Narrow",sans-serif;color:#404040">Archivist for Metadata, Systems, and Digital Records<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial Narrow",sans-serif;color:#404040">David M. Rubenstein Rare Book & Manuscript Library<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial Narrow",sans-serif;color:#404040">Duke University | <a href="tel:(919)%20660-5982" value="+19196605982" target="_blank">919-660-5982</a><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial Narrow",sans-serif;color:#404040"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__library.duke.edu_rubenstein_&d=DwMGaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=wE2o0IUu9kQhWW-i5a9h2HkT3iy90G6vN7OXuLu53mo&s=8JD-M2Q_Y3IewpDkfhu1tF3BGbN9nHMNgl3fXPtHjMo&e=" target="_blank"><span style="color:#404040">http://library.duke.edu/<wbr>rubenstein/</span></a>
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></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" target="_blank">
archivesspace_users_group-<wbr>bounces@lyralists.lyrasis.org</a> [<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" target="_blank">mailto:archivesspace_users_<wbr>group-bounces@lyralists.<wbr>lyrasis.org</a>]
<b>On Behalf Of </b>Mayo, Dave<br>
<b>Sent:</b> Thursday, September 07, 2017 3:59 PM<br>
<b>To:</b> Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org" target="_blank">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a>><br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] Pointer to choices for formatting the title of an archival object, such as an article title<u></u><u></u></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Hi Kari,<br>
<br>
I’m on the techy side of things, so I may be out in “strictly accurate but not practical” land, but fundamentally, mixed content is more “allowed in by accident” than “explicitly supported” in ArchivesSpace. Markup in title fields isn’t handled specially,
and, in the case of EAD markup, only works in cases where it _<i>accidentally</i>_ overlaps with HTML. So, I think in an ideal world, the dos and don’ts would be “please don’t.” I realize that isn’t necessarily practical for all use cases. Bobbi Fox (and
others) have done some mitigation work in the new PUI, but there’s not really a “safe” subset of markup that’s guaranteed to be ok.<br>
<br>
- Dave Mayo<br>
Senior Digital Library Software Engineer<br>
Harvard University > HUIT > LTS > OSC Dev Team<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in 0in 0in">
<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" target="_blank">archivesspace_users_group-<wbr>bounces@lyralists.lyrasis.org</a>> on behalf of Kari R Smith <<a href="mailto:smithkr@mit.edu" target="_blank">smithkr@mit.edu</a>><br>
<b>Reply-To: </b>Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org" target="_blank">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a>><br>
<b>Date: </b>Thursday, September 7, 2017 at 3:03 PM<br>
<b>To: </b>"Archivesspace Users Group (<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org" target="_blank">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a>)" <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org" target="_blank">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a>><br>
<b>Subject: </b>[Archivesspace_Users_Group] Pointer to choices for formatting the title of an archival object, such as an article title</span><span style="font-size:12.0pt;color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif"><u></u> <u></u></span></p>
</div>
<div>
<div>
<p class="MsoNormal">Hello,<u></u><u></u></p>
<p class="MsoNormal">Is there guidance about the dos and don’ts for formatting (markup) of titles of archival objects? We are trying to find information about adding markup in a title field like when we want to have it formatted with italics or underlining,
as we might for a bibliography or to include an “article title” as part of a folder title.<u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal">I see that within Note fields you can wrap EAD markup but not in the archival objects.
<u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal">Thanks for help pointing to AS user info or organizational specific user manuals.<u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal">Kari<u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal"><span style="color:#1f497d">Kari R. Smith</span><u></u><u></u></p>
<p class="MsoNormal"><span style="color:#1f497d">Digital Archivist and Program Head for Born-digital Archives</span><u></u><u></u></p>
<p class="MsoNormal"><span style="color:#1f497d">Institute Archives and Special Collections</span><u></u><u></u></p>
<p class="MsoNormal"><span style="color:#1f497d">Massachusetts Institute of Technology Libraries, Cambridge, Massachusetts</span><u></u><u></u></p>
<p class="MsoNormal"><span style="color:#1f497d"><a href="tel:(617)%20253-5690" value="+16172535690" target="_blank">617.253.5690</a> smithkr at <a href="http://mit.edu" target="_blank">mit.edu</a>
</span><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__libraries.mit.edu_archives_&d=DwMFAg&c=WO-RGvefibhHBZq3fL85hQ&r=_Mv1dY22K7jvT5MD7xjbvGVzRDOUMhx4WYcnPSIzYnE&m=lCWyETDpjXsDuRKUPzUu6UlKN4EfDV3HJDtojFHzBFo&s=Vf0Wcti9niQaLMt_ONXZuzSLySf664w67xSRgVVIv4k&e=" target="_blank">http://libraries.mit.edu/<wbr>archives/</a><span style="color:#1f497d">
@karirene69</span><u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
</div></div></div>
</div>
<br>______________________________<wbr>_________________<br>
Archivesspace_Users_Group mailing list<br>
<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@<wbr>lyralists.lyrasis.org</a><br>
<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>archivesspace_users_group</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><font size="2" style="background-color:rgb(255,255,255)" color="#666666">Trevor Thornton</font><div><font size="2" style="background-color:rgb(255,255,255)" color="#666666">Applications Developer, Digital Library Initiatives</font></div><div><font size="2" style="background-color:rgb(255,255,255)" color="#666666">North Carolina State University Libraries</font></div></div></div></div></div></div></div>
</div>