<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)">
<!--[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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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:Verdana;
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:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:"Arial Narrow";
panose-1:2 11 6 6 2 2 2 3 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
{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:12.0pt;
font-family:"Times New Roman","serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.pl-c1
{mso-style-name:pl-c1;}
span.pl-k
{mso-style-name:pl-k;}
span.pl-s
{mso-style-name:pl-s;}
span.pl-pds
{mso-style-name:pl-pds;}
span.EmailStyle26
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle27
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle28
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle29
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle30
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle31
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle33
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle34
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle35
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle36
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.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 am so glad to see this being discussed again. Quick point regarding #1 (collection-level) below: While it makes sense that people wouldn’t always want imported
resources immediately published, an institution migrating large numbers of finding aids (<6,000 in our case) won’t want to have to publish each resource manually. The last time I tried to get around the currently incorrect handling of audience/publish in the
importer by supplying explicit audience=”external” values, the importer failed outright. If the fix could respect an explicit audience attribute=”external” at the collection-level, we could pre-process the finding aids to add that.<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">Robin<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">Robin Wendler<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Library Technology Services<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Harvard University<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">90 Mt. Auburn St.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Cambridge, MA 02138<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">617-495-3724<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">r_wendler@harvard.edu<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"><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>
<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>Cobourn, Alston<br>
<b>Sent:</b> Wednesday, April 06, 2016 3:47 PM<br>
<b>To:</b> Archivesspace Users Group<br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] EAD Import trouble with audience/publish<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thank you Mark and Noah for giving this so much thought. As someone with a public interface, I agree that the suggested changes make a lot of sense.<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>
<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"">
<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>Noah Huffman<br>
<b>Sent:</b> Wednesday, April 06, 2016 11:02 AM<br>
<b>To:</b> Archivesspace Users Group<br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] EAD Import trouble with audience/publish<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Mark, I tend to agree with your suggested behavior now that you’ve laid out the logic so well</span><span style="font-size:11.0pt;font-family:Wingdings;color:#1F497D">J</span><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"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">So, if I read it right, you are suggesting these changes to the current EAD importer behavior?:<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">1.</span><span style="font-size:7.0pt;color:#1F497D">
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">EAD imports should result in resource records marked as “unpublished” at the collection level<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">2.</span><span style="font-size:7.0pt;color:#1F497D">
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">The EAD importer should, by default, mark all components and notes as “published” unless EAD tags include @audience=”internal”<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">Because we currently don’t use the public interface at Duke, I hadn’t thought through the consequences of publishing everything by default on import.<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">To your last point (#3), we’ve definitely experienced issues with the “publish all” button unintentionally publishing components at lower levels that had been
selectively marked as ‘internal only’ for various reasons. On this point, I think it would be nice to have some indication in the staff interface--at the collection level---that a resource contains some components or notes at lower levels that are not marked
as published. It’s impractical to click open every component to see if it’s published or not.<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">Also, just to add one more issue to the mix, the importer currently ignores eadheader/@findingaidstatus values. See:
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.atlassian.net_browse_AR-2D1282&d=CwMFAg&c=WO-RGvefibhHBZq3fL85hQ&r=JKUSUWdXrLBGP_rNc_JtcJNO9wvGRzWSZ2uoZzcT59w&m=n9TID9-EvwwWqVDUObvk9YPr-QSL9RqOp5EQSk1-a10&s=hLBnLT1Iyg0dKk6fVXXiZBWs4fHGKJlauLp-VCGoAZg&e=">
https://archivesspace.atlassian.net/browse/AR-1282</a> <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">We currently use a local vocabulary in the Finding Aid Status field to help manage our workflows. For example, we use values like “published,” “completed,”
“temp_record,” and “placeholder_record” to help identify resource records in various stages of completion. These values also appear as facets in browse and search results.<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">-Noah<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"><o:p> </o:p></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="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">
<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>Custer, Mark<br>
<b>Sent:</b> Wednesday, April 06, 2016 10:15 AM<br>
<b>To:</b> Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@lyralists.lyrasis.org</a>><br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] EAD Import trouble with audience/publish<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">And Noah, all:<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">Here’s what the EAD 2002 tag library states about the audience attribute:<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" style="line-height:12.1pt;background:white"><span style="font-size:8.5pt;font-family:"Verdana","sans-serif";color:#333333">AUDIENCE -- An attribute that helps control whether the information contained in the element should be available
to all viewers or only to repository staff. Available for all elements except line break <lb>. The audience attribute can be set to "external" in <archdesc> to allow access to all the information about the materials being described in the finding aid, but
specific elements within <archdesc> can be set to "internal" to reserve that information for repository access only.
<span style="background:yellow;mso-highlight:yellow">This feature is intended to assist application software in restricting access to particular information by explicitly coding data that is potentially sensitive or may otherwise have a limited audience</span>.
Special software capability may be needed, however, to prevent the export of an element marked "internal" when a whole finding aid is displayed in a networked environment. Values are:<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:7.5pt;text-indent:-.25in;line-height:15.0pt;background:white">
<span style="font-size:10.0pt;font-family:Symbol;color:#333333;background:yellow;mso-highlight:yellow">·</span><span style="font-size:7.0pt;color:#333333;background:yellow;mso-highlight:yellow">
</span><span style="font-size:9.5pt;font-family:"Verdana","sans-serif";color:#333333;background:yellow;mso-highlight:yellow">external
<b>(default value)<o:p></o:p></b></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:7.5pt;text-indent:-.25in;line-height:15.0pt;background:white">
<span style="font-size:10.0pt;font-family:Symbol;color:#333333">·</span><span style="font-size:7.0pt;color:#333333">
</span><span style="font-size:9.5pt;font-family:"Verdana","sans-serif";color:#333333">internal<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Because of that, I think the community has already made that decision (and that’s how the AT EAD importer behaved; anyone know what the Archon importer did?).<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">That said, I still think it would be wise, as I mentioned previously, if the ASpace importer would always set an imported finding aid to be unpublished due
to the fact that the ASpace staff interface and public interface are so tightly coupled together. Plus, it’s quite easy to hit “publish” after the fact, once you’re really ready for things to go live.<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"><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>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">
</span><a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">archivesspace_users_group-bounces@lyralists.lyrasis.org</span></a><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">
[</span><a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org</span></a><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">]
<b>On Behalf Of </b>Custer, Mark<br>
<b>Sent:</b> Wednesday, 06 April, 2016 9:59 AM<br>
<b>To:</b> Archivesspace Users Group<br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] EAD Import trouble with audience/publish<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks to you both. I’ll try to dig into the importer code next week.<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">I’m not sure if this is entirely an “if the community agrees” type of change, though. It seems to me that this is just following the EAD standard (i.e. respecting
the audience attribute, rather than ignoring it.. at least almost all of the time, which I’ll explain below).
<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">If I understand correctly, the current EAD importer ignores the audience attribute entirely. Instead, it takes the following three actions by default, regardless
of what the metadata says:<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="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">1.</span><span style="font-size:7.0pt;color:#1F497D">
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Publish the finding aid<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">2.</span><span style="font-size:7.0pt;color:#1F497D">
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Publish all components of the finding<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">3.</span><span style="font-size:7.0pt;color:#1F497D">
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Unpublish all notes in the finding aid<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">Is that right? (I haven’t tested this in a while, so I’m not entirely sure)<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">If so, I think that each of those three actions need to be reconsidered, and here’s why:<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="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">1.</span><span style="font-size:7.0pt;color:#1F497D">
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">If you’re using the ASpace PUI, do you really want a newly imported EAD finding aid to be added immediately to the PUI? My hunch is no, for the following reasons:<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">a.</span><span style="font-size:7.0pt;color:#1F497D">
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">You probably want to review the record first.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">b.</span><span style="font-size:7.0pt;color:#1F497D">
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">You might have to update some of the metadata, depending on the state of the EAD importer (I’m primarily thinking of how those physdesc elements are interpreted upon import).<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">c.</span><span style="font-size:7.0pt;color:#1F497D">
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">You might be importing a partial finding aid, like a new series, that you plan to merge with a pre-existing finding aid. In that case, this newly-imported file is only meant
to be temporary, so having that indexed and showing up as a new finding aid in the PUI would be problematic to say the least.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">So, this is the one and only place where I’d prefer the EAD importer to ignore the EAD metadata. By default, all imported resources
(whether MARC or EAD) should be set to unpublished. Setting the entire finding aid to published by default is only going to cause problems, it seems. Plus, once the finding aid is truly ready to be published, all that you have to do is select the publish
checkbox and hit save. Simple and safe.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">2.</span><span style="font-size:7.0pt;color:#1F497D">
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">What if you have 150 of 2000 components in an EAD file set to internal only? Since the current importer sets every component to be published, you’d have to unpublish those
150 components after an import, which would be extremely problematic, especially because those components will probably show up in the PUI before you have a chance to update the records. Much simpler would be if the importer would unpublish the 150 components
(the ones that have an audience attribute set to “internal”), and publish the other 1850 components (the ones that either don’t have an audience attribute, or the ones that have an audience attribute set to “external”).<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">3.</span><span style="font-size:7.0pt;color:#1F497D">
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">This is the strangest default option, I think. Why do the components get published by default, but the notes get unpublished? Just like with action 2, I think that the
EAD importer should respect the audience attribute here in the EAD source file. We definitely have finding aids where a few notes are marked as internal, but the bulk are set to be published. Because of this, the “publish all” button is actually very dangerous
in those cases where the entire contents of a finding aid are not intended to be public.<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">What do others think?<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">Mark<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"><o:p> </o:p></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="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">
</span><a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">archivesspace_users_group-bounces@lyralists.lyrasis.org</span></a><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">
[</span><a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org</span></a><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">]
<b>On Behalf Of </b>Galligan, Patrick<br>
<b>Sent:</b> Wednesday, 06 April, 2016 9:09 AM<br>
<b>To:</b> Archivesspace Users Group<br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] EAD Import trouble with audience/publish<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Noah,<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">Yeah, in my experience the EAD importer modifications that we made should apply to all levels on import, but as you called out, you have to make some more tweaks
for different types of notes, but it’s pretty easy to find those in the importer file.<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">Patrick Galligan<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Rockefeller Archive Center<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Assistant Digital Archivist<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">914-366-6386<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"">
</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"">
[</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"">]
<b>On Behalf Of </b>Noah Huffman<br>
<b>Sent:</b> Wednesday, April 06, 2016 9:06 AM<br>
<b>To:</b> Archivesspace Users Group<br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] EAD Import trouble with audience/publish<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Mark,<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">I’m not aware of any pull requests for modifying the EAD converter. I think it’d be nice to include in the core code assuming that everyone (the community)
agrees that publishing everything by default is the expected behavior.<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">I’m pretty sure the changes I made will apply to notes at any level (component or collection), but I could be wrong and I haven’t tested extensively. It’s
also possible I missed some notes. I just took the example code that Patrick shared and applied it to some other locations (for both single and multi-part notes).<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">-Noah<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>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">
</span><a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">archivesspace_users_group-bounces@lyralists.lyrasis.org</span></a><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">
[</span><a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org</span></a><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">]
<b>On Behalf Of </b>Custer, Mark<br>
<b>Sent:</b> Tuesday, April 05, 2016 4:38 PM<br>
<b>To:</b> Archivesspace Users Group <</span><a href="mailto:archivesspace_users_group@lyralists.lyrasis.org"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">archivesspace_users_group@lyralists.lyrasis.org</span></a><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">><br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] EAD Import trouble with audience/publish<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">This is great, Noah (and Patrick!). Do you know if anyone created a pull request yet to put this into the core code? If not, I’ll be happy to do that at some
point next week since it would make the most sense for this type of update to live in the core code.<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">Also, did you (or anyone else) modify the importer so that @audience=’internal’ was respected at the collection and component level? I seem to remember that
the importer always publishes the components, but it’s been a while since I looked at what happens there.
<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">Mark<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"><o:p> </o:p></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="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">
</span><a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">archivesspace_users_group-bounces@lyralists.lyrasis.org</span></a><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">
[</span><a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org</span></a><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">]
<b>On Behalf Of </b>Noah Huffman<br>
<b>Sent:</b> Tuesday, 05 April, 2016 4:06 PM<br>
<b>To:</b> Archivesspace Users Group<br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] EAD Import trouble with audience/publish<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hi Jane,<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">I noticed that Patrick G. from the Rockefeller Archives shared a solution to this same issue back on Nov. 16 (Subject line: Audience Question).
<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">Basically, you can modify the EAD converter that Chris mentions to set all imported notes to ‘published’ by default unless EAD elements have @audience=’internal’.<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">You can set up the modified EAD converter as a plugin.<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">I needed to do this locally, so I went ahead a wrote a plugin.<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">Here is the modified EAD converter:
</span><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_noahgh221_archivesspace-2Dduke-2Dplugins_blob_master_plugins_duke-2Dead-2Dimporter_backend_converters_duke-5Fead-5Fconverter.rb&d=AwMFAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=s7ciGQfUJeaV_ryx908hbeXDoU9aqDwDN0Z0VbfsJ3Y&m=9aIZ08dKR_unOY5i_HM10zQCPnpzrJDXPBGW92jXDHo&s=WkRhMfjAmf0w1Qrvy0yZxKi3QTUG3oZzLXDrWLpsW84&e="><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">https://github.com/noahgh221/archivesspace-duke-plugins/blob/master/plugins/duke-ead-importer/backend/converters/duke_ead_converter.rb</span></a><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"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Here’s how to set up the plugin:<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">1.</span><span style="font-size:7.0pt;color:#1F497D">
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Download the modified EAD converter file above (click ‘Raw’, save as, etc.)<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">2.</span><span style="font-size:7.0pt;color:#1F497D">
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Save the file to the plugins directory in your ASpace application files: plugins/duke-ead-importer/backend/converters/duke_ead_converter.rb (you’ll need to create the duke-ead-importer/backend/converters/
directory structure)<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span class="pl-s"><span style="font-size:9.0pt;font-family:Consolas;color:#183691">3.</span></span><span class="pl-s"><span style="font-size:7.0pt;color:#183691">
</span></span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Open the config/config.rb file, add the name of the plugin to the line that begins AppConfig[:plugins], and save it. For example:
</span><span class="pl-c1"><span style="font-size:9.0pt;font-family:Consolas;color:#0086B3;background:white">AppConfig</span></span><span style="font-size:9.0pt;font-family:Consolas;color:#333333;background:white">[</span><span class="pl-c1"><span style="font-size:9.0pt;font-family:Consolas;color:#0086B3;background:white">:plugins</span></span><span style="font-size:9.0pt;font-family:Consolas;color:#333333;background:white">]
</span><span class="pl-k"><span style="font-size:9.0pt;font-family:Consolas;color:#A71D5D;background:white">=</span></span><span style="font-size:9.0pt;font-family:Consolas;color:#333333;background:white">
</span><span class="pl-s"><span style="color:#183691">[</span>'</span><span class="pl-s"><span style="font-size:9.0pt;font-family:Consolas;color:#183691;background:white">local</span>', ‘<span style="color:#183691">duke-ead-converter’]</span></span><span class="pl-s"><span style="font-size:9.0pt;font-family:Consolas;color:#183691;background:white"><o:p></o:p></span></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">4.</span><span style="font-size:7.0pt;color:#1F497D">
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Restart the archivesspace application (archivesspace/archivesspace.sh or archivesspace/archivesspace.bat on Windows)<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">5.</span><span style="font-size:7.0pt;color:#1F497D">
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Start a new EAD import job<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">For more info on how plugins work, see:
</span><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__archivesspace.github.io_archivesspace_user_archivesspace-2Dplug-2Dins-2Dreadme_&d=AwMFAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=s7ciGQfUJeaV_ryx908hbeXDoU9aqDwDN0Z0VbfsJ3Y&m=9aIZ08dKR_unOY5i_HM10zQCPnpzrJDXPBGW92jXDHo&s=ODjNtfXXQlhFC0zTFc1Lu-zq3QU2cSPF64lRy7BGKQ0&e="><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">http://archivesspace.github.io/archivesspace/user/archivesspace-plug-ins-readme/</span></a><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"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I ran a couple of EAD import tests using this plugin and it seems to publish all imported notes by default unless EAD tags include @audience=”internal”. Still,
I’d test this before importing all your EADs to production.<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">Hope this helps.<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">-Noah<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:10.0pt;font-family:"Arial Narrow","sans-serif";color:#404040">================<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial Narrow","sans-serif";color:#404040">Noah Huffman<o:p></o:p></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<o:p></o:p></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<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial Narrow","sans-serif";color:#404040">Duke University<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>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">
</span><a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">archivesspace_users_group-bounces@lyralists.lyrasis.org</span></a><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">
[</span><a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org</span></a><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">]
<b>On Behalf Of </b>Chris Fitzpatrick<br>
<b>Sent:</b> Tuesday, April 05, 2016 2:45 AM<br>
<b>To:</b> </span><a href="mailto:archivesspace_users_group@lyralists.lyrasis.org"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">archivesspace_users_group@lyralists.lyrasis.org</span></a><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] EAD Import trouble with audience/publish<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div id="divtagdefaultwrapper">
<p style="background:white"><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
<p style="background:white"><span style="font-family:"Calibri","sans-serif";color:black">Hi,
<o:p></o:p></span></p>
<p style="background:white"><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
<p style="background:white"><span style="font-family:"Calibri","sans-serif";color:black">Yes, it looks like the
</span><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_archivesspace_archivesspace_blob_master_backend_app_converters_ead-5Fconverter.rb-23L108&d=AwMFAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=s7ciGQfUJeaV_ryx908hbeXDoU9aqDwDN0Z0VbfsJ3Y&m=9aIZ08dKR_unOY5i_HM10zQCPnpzrJDXPBGW92jXDHo&s=8IrDk6ha3gPgGoM7aphSqz3AnVMqr6mwUNUijZrZaFI&e="><span style="font-family:"Calibri","sans-serif"">EAD
converter</span></a><span style="font-family:"Calibri","sans-serif";color:black"> only looks at @audience for archdesc and c tags. <o:p></o:p></span></p>
<p style="background:white"><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
<p style="background:white"><span style="font-family:"Calibri","sans-serif";color:black">b,chris.
<o:p></o:p></span></p>
<p style="background:white"><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" style="background:white"><span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:black">Chris Fitzpatrick | Developer, ArchivesSpace<br>
Skype: chrisfitzpat | Phone: 918.236.6048<br>
</span><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__archivesspace.org_&d=AwMFAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=s7ciGQfUJeaV_ryx908hbeXDoU9aqDwDN0Z0VbfsJ3Y&m=9aIZ08dKR_unOY5i_HM10zQCPnpzrJDXPBGW92jXDHo&s=Jls-8V7jtaJVF7ZDaDEcnLttL7qE33gGuI8xrm1I10s&e="><span style="font-size:10.0pt;font-family:"Calibri","sans-serif"">http://archivesspace.org/</span></a><span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:black"><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt;background:white"><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
<div>
<div class="MsoNormal" align="center" style="text-align:center;background:white">
<span style="font-family:"Calibri","sans-serif";color:black">
<hr size="2" width="98%" align="center">
</span></div>
<div id="divRplyFwdMsg">
<p class="MsoNormal" style="background:white"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">
</span><a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">archivesspace_users_group-bounces@lyralists.lyrasis.org</span></a><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">
<</span><a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">archivesspace_users_group-bounces@lyralists.lyrasis.org</span></a><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">>
on behalf of Jane LaBarbara <</span><a href="mailto:jane.labarbara@mail.wvu.edu"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">jane.labarbara@mail.wvu.edu</span></a><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">><br>
<b>Sent:</b> Monday, April 04, 2016 8:34 PM<br>
<b>To:</b> </span><a href="mailto:archivesspace_users_group@lyralists.lyrasis.org"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">archivesspace_users_group@lyralists.lyrasis.org</span></a><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"><br>
<b>Subject:</b> [Archivesspace_Users_Group] EAD Import trouble with audience/publish</span><span style="font-family:"Calibri","sans-serif";color:black">
<o:p></o:p></span></p>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Calibri","sans-serif";color:black"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p style="background:white"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">Dear all,<o:p></o:p></span></p>
<p style="background:white"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"> <o:p></o:p></span></p>
<p style="background:white"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">I’m using legacy EAD XML to test ArchivesSpace’s EAD Import in preparation for a mass migration to ArchivesSpace. I’ve noticed that I can add the attribute
audience=”external” to <archdesc> and all of my “notes” (e.g. <relatedmaterial>, <bioghist>, and many more), but the resulting Resource Record is only published at the highest level—the notes themselves are not published. Once we migrate, I’m guessing this
will mean that staff will have to go into each Resource Record and click the “publish” checkboxes for everything we need to show up in the public view, and we have over 4000 collections.<o:p></o:p></span></p>
<p style="background:white"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"> <o:p></o:p></span></p>
<p style="background:white"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">Has anyone else noticed that the EAD Import does not respect audience=”external”, or found a solution or workaround for this?<o:p></o:p></span></p>
<p style="background:white"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"> <o:p></o:p></span></p>
<p style="background:white"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">Thanks,<o:p></o:p></span></p>
<p style="background:white"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">Jane<o:p></o:p></span></p>
<p style="background:white"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"> <o:p></o:p></span></p>
<p style="background:white"><span style="font-size:10.0pt;font-family:"Segoe UI","sans-serif";color:black">Jane Metters LaBarbara</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"><o:p></o:p></span></p>
<p style="background:white"><span style="font-size:10.0pt;font-family:"Segoe UI","sans-serif";color:black">Assistant Curator</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"><o:p></o:p></span></p>
<p style="background:white"><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__wvrhc.lib.wvu.edu_&d=AwMFAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=s7ciGQfUJeaV_ryx908hbeXDoU9aqDwDN0Z0VbfsJ3Y&m=9aIZ08dKR_unOY5i_HM10zQCPnpzrJDXPBGW92jXDHo&s=3DizfA4Cr8171ah5VvpQI_W1wPlXIjnUOOmh2Jm3moU&e="><span style="font-size:10.0pt;font-family:"Segoe UI","sans-serif";color:#0563C1">West
Virginia & Regional History Center</span></a><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"><o:p></o:p></span></p>
<p style="background:white"><span style="font-size:10.0pt;font-family:"Segoe UI","sans-serif";color:black">West Virginia University Libraries</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"><o:p></o:p></span></p>
<p style="background:white"><span style="font-size:10.0pt;font-family:"Segoe UI","sans-serif";color:black">Reference desk: 304-293-3536</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"><o:p></o:p></span></p>
<p style="background:white"><span style="font-size:10.0pt;font-family:"Segoe UI","sans-serif";color:black">Office phone: 304-293-0352</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"><o:p></o:p></span></p>
<p style="background:white"><span style="font-size:10.0pt;font-family:"Segoe UI","sans-serif";color:black">Email:
</span><a href="mailto:jane.labarbara@mail.wvu.edu"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#0563C1">jane.labarbara@mail.wvu.edu</span></a><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"><o:p></o:p></span></p>
<p style="background:white"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"> <o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>