<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1531721691;
mso-list-type:hybrid;
mso-list-template-ids:697068656 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1
{mso-list-id:1935093826;
mso-list-type:hybrid;
mso-list-template-ids:917921834 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US">
<div>Just a warning that <i>_record_innards.html.erb</i> is a large, complex and often-changed template. So if you override it in a plug-in, even just to move one value (<i>altformavail</i> in this case) between those two lists that Mark explained, you will
probably need to download the latest version of it and redo that change every time you upgrade ArchivesSpace in the future. If you don't then, for example, if you're currently running 2.6.0, then you upgrade to 2.7.1, languages of materials will disappear.
That is because changes to languages in 2.7.0 included modifications to <i>_record_innards.html.erb</i>.</div>
<div><br>
</div>
<div>The <i>folder</i> and <i>non_folder</i> lists could be turned into config file options, but that would make it easy to do bad things, display the same note twice, or end up with an empty additional description box. And it wouldn't allow re-ordering, removing,
or changing the contents of the other accordion boxes.</div>
<div><br>
</div>
<div>Andrew.</div>
<div><br>
</div>
<div><br>
</div>
<div>On Fri, 2020-02-28 at 16:35 +0000, Custer, Mark wrote:</div>
<blockquote type="cite">
<div class="WordSection1">
<p class="MsoNormal">Jordon,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level1 lfo3">As far as I know, you would have to do that in a plugin right now. Here’s an example, since it’s not obvious where one would do that:
<a href="https://github.com/YaleArchivesSpace/yale_pui_customizations/commit/18b7be17825cc84916d2b0ad6cd4cfe776545462#diff-7ff34653933e2e6d670c7b053db80db6">
https://github.com/YaleArchivesSpace/yale_pui_customizations/commit/18b7be17825cc84916d2b0ad6cd4cfe776545462#diff-7ff34653933e2e6d670c7b053db80db6</a> So, you just put a list of the notes you want to display above the accordions in the “non_folder” variable,
and include the ones that appear in the accordions” in the “folder” variable. All that said, I’d personally like to see the PUI try something else other than using accordions by default to hide notes.
<o:p></o:p></li></ol>
<p class="MsoListParagraph"><o:p> </o:p></p>
<ol style="margin-top:0in" start="2" type="1">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level1 lfo3">I also think that Digital Objects in general should be overhauled in ArchivesSpace (both on the staff and public side)…. I’d actually prefer something like the “File URI” subrecords
be something that you could associate with archival object, resource, an accession records, rather than have digital object records at all (we don’t isolate description in ASpace for anything else based on format). That said, some folks have used a plugin
to add a bit of javascript that opens all of the accordions by default so that the contents are immediately visible (and findable with a browser search). That might be another way rather than just re-ordering what notes display above the accordions. And
then Harvard did even more helpful customizations to highlight digital objects by making them their own tab on the collection-level pages. E.g.
<a href="https://hollisarchives.lib.harvard.edu/repositories/24/resources/1248/digital_only">
https://hollisarchives.lib.harvard.edu/repositories/24/resources/1248/digital_only</a> I definitely think that feature (or something like it) needs to be part of the core public interface!
<o:p></o:p></li></ol>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Mark<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> archivesspace_users_group-bounces@lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org]
<b>On Behalf Of </b>Jordon Steele<br>
<b>Sent:</b> Friday, 28 February, 2020 10:53 AM<br>
<b>To:</b> Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org><br>
<b>Subject:</b> [Archivesspace_Users_Group] Better notifying users of digital content presence<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hello,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">When our collections have digital content associated with them, our practice is to add an “Existence and Location of Copies” note to the collection level indicating the presence of digital content like digitized copies of the originals.
(We do other stuff at lower levels, too.) However, by default, this note only appears if you click the “Expand All” button. This means that users and staff often request boxes—especially small collections—without noticing that all or part of the collection
is scanned.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We’re considering changing the order of the notes so that this note features more prominently, above the “Expand All” fold. I have two questions.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo2">Is this something that is configurable in the standard staff-side interface of ASpace, or would the PUI plug-in need to be edited? (I think the answer is the latter, but just confirming
I am not missing something.)<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo2">Bumping the note above the “Expand All” fold is just the first idea that came to mind. Do you have other ways you signal to users on the
<b>collection-level page</b> the presence of digital content? If so, I’m all ears.<o:p></o:p></li></ol>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thank you in advance, and sorry if this has been discussed before!<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Jordon<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Jordon Steele<o:p></o:p></p>
<p class="MsoNormal">Hodson Curator of the University Archives<o:p></o:p></p>
<p class="MsoNormal">Sheridan Libraries<o:p></o:p></p>
<p class="MsoNormal">Johns Hopkins University<o:p></o:p></p>
<p class="MsoNormal">3400 N Charles St<o:p></o:p></p>
<p class="MsoNormal">Baltimore, MD 21218<o:p></o:p></p>
<p class="MsoNormal">410-516-5493<o:p></o:p></p>
<p class="MsoNormal"><a href="mailto:jsteele@jhu.edu">jsteele@jhu.edu</a><o:p></o:p></p>
<p class="MsoNormal">he/him/his<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<pre>_______________________________________________
Archivesspace_Users_Group mailing list
<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@lyralists.lyrasis.org</a>
<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</a>
</pre>
</blockquote>
</body>
</html>