<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div>We do similar but have added a condition so it doesn't expand all for devices smaller than an iPad:</div>
<div><br>
</div>
<div>
<pre style="color: rgb(0, 0, 0); font-family: 'DejaVu Sans Mono'; font-size: 9pt;"><span style="color:#000080;font-weight:bold;">if </span>(<span style="font-style:italic;">$</span>(<span style="color:#660e7a;font-weight:bold;font-style:italic;">window</span>).<span style="color:#7a7a43;">width</span>() >= <span style="color:#0000ff;">768</span>) { <span style="font-style:italic;">collapse_all</span>(<span style="color:#008000;font-weight:bold;">'.note_panel'</span>,<span style="color:#000080;font-weight:bold;">true</span>); }</pre>
</div>
<div><br>
</div>
<div>Andrew.</div>
<div><br>
</div>
<div>On Fri, 2020-02-28 at 17:26 +0000, Majewski, Steven Dennis (sdm7g) wrote:</div>
<blockquote type="cite">
<div class="">We use the "open accordions by default" javascript method. </div>
<div class=""><br class="">
</div>
<div class="">In plugins/local/public/views/layout_head.html.erb, we have:</div>
<div class=""><br class="">
</div>
<div class="">
<div style="margin: 0px; font-stretch: normal; line-height: normal; background-color: rgb(203, 255, 254);" class="">
<span style="font-variant-ligatures: no-common-ligatures; font-size: 14px;" class=""><% if ( [ 'objects', 'resources' ].include?( controller.controller_name )) %></span></div>
<div style="margin: 0px; font-stretch: normal; line-height: normal; background-color: rgb(203, 255, 254);" class="">
<span style="font-variant-ligatures: no-common-ligatures; font-size: 14px;" class=""><!-- expand all --></span></div>
<div style="margin: 0px; font-stretch: normal; line-height: normal; background-color: rgb(203, 255, 254);" class="">
<span style="font-variant-ligatures: no-common-ligatures; font-size: 14px;" class=""><script type="text/javascript" ></span></div>
<div style="margin: 0px; font-stretch: normal; line-height: normal; background-color: rgb(203, 255, 254);" class="">
<span style="font-variant-ligatures: no-common-ligatures; font-size: 14px;" class=""> $( function() { collapse_all( '.note_panel', true ); } );</span></div>
<div style="margin: 0px; font-stretch: normal; line-height: normal; background-color: rgb(203, 255, 254);" class="">
<span style="font-variant-ligatures: no-common-ligatures; font-size: 14px;" class=""></script></span></div>
<div style="margin: 0px; font-stretch: normal; line-height: normal; background-color: rgb(203, 255, 254);" class="">
<span style="font-variant-ligatures: no-common-ligatures; font-size: 14px;" class=""><% end %><!-- end if controller.controller_name... --></span></div>
</div>
<div class=""><span style="font-variant-ligatures: no-common-ligatures" class=""><br class="">
</span></div>
<div class=""><br class="">
</div>
<div class="">I would also note that I’ve found that IF local mods can be done in javascript only, rather than customizing views, then it does make the local mods, on average, somewhat more maintainable. Changes are localized into that one layout_head template
and checking for conflicts in new releases is a bit simpler. ( My preference. Your mileage may vary! ) </div>
<div class=""><br class="">
</div>
<div class="">— Steve M.</div>
<div class=""><br class="">
</div>
<div><br class="">
<blockquote type="cite">
<div class="">On Feb 28, 2020, at 11:35 AM, Custer, Mark <<a href="mailto:mark.custer@yale.edu">mark.custer@yale.edu</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Menlo-Regular; font-size: 16px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;">
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
Jordon,<o:p class=""></o:p></div>
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<o:p class=""> </o:p></div>
<ol start="1" type="1" style="margin-bottom: 0in; margin-top: 0in;" class="">
<li class="MsoListParagraph" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
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" style="color: rgb(149, 79, 114); text-decoration: underline;">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 class=""></o:p></li></ol>
<div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<o:p class=""> </o:p></div>
<ol start="2" type="1" style="margin-bottom: 0in; margin-top: 0in;" class="">
<li class="MsoListParagraph" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
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" style="color: rgb(149, 79, 114); text-decoration: underline;">https://hollisarchives.lib.harvard.edu/repositories/24/resources/1248/digital_only</a><span class="Apple-converted-space"> </span> I
definitely think that feature (or something like it) needs to be part of the core public interface!<o:p class=""></o:p></li></ol>
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<o:p class=""> </o:p></div>
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
Mark<o:p class=""></o:p></div>
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<o:p class=""> </o:p></div>
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<o:p class=""> </o:p></div>
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<o:p class=""> </o:p></div>
<div class="">
<div style="border-style: solid none none; border-top-width: 1pt; border-top-color: rgb(225, 225, 225); padding: 3pt 0in 0in;" class="">
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<b class="">From:</b><span class="Apple-converted-space"> </span><a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" style="color: rgb(149, 79, 114); text-decoration: underline;">archivesspace_users_group-bounces@lyralists.lyrasis.org</a><span class="Apple-converted-space"> </span>[<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" style="color: rgb(149, 79, 114); text-decoration: underline;">mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org</a>]<span class="Apple-converted-space"> </span><b class="">On
Behalf Of<span class="Apple-converted-space"> </span></b>Jordon Steele<br class="">
<b class="">Sent:</b><span class="Apple-converted-space"> </span>Friday, 28 February, 2020 10:53 AM<br class="">
<b class="">To:</b><span class="Apple-converted-space"> </span>Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org" style="color: rgb(149, 79, 114); text-decoration: underline;">archivesspace_users_group@lyralists.lyrasis.org</a>><br class="">
<b class="">Subject:</b><span class="Apple-converted-space"> </span>[Archivesspace_Users_Group] Better notifying users of digital content presence<o:p class=""></o:p></div>
</div>
</div>
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<o:p class=""> </o:p></div>
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
Hello,<o:p class=""></o:p></div>
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<o:p class=""> </o:p></div>
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
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 class=""></o:p></div>
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<o:p class=""> </o:p></div>
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
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 class=""></o:p></div>
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<o:p class=""> </o:p></div>
<ol start="1" type="1" style="margin-bottom: 0in; margin-top: 0in;" class="">
<li class="MsoListParagraph" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
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 class=""></o:p></li><li class="MsoListParagraph" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
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<span class="Apple-converted-space"> </span><b class="">collection-level page</b><span class="Apple-converted-space"> </span>the
presence of digital content? If so, I’m all ears.<o:p class=""></o:p></li></ol>
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<o:p class=""> </o:p></div>
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
Thank you in advance, and sorry if this has been discussed before!<o:p class=""></o:p></div>
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<o:p class=""> </o:p></div>
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
Best,<o:p class=""></o:p></div>
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<o:p class=""> </o:p></div>
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
Jordon<o:p class=""></o:p></div>
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<o:p class=""> </o:p></div>
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
Jordon Steele<o:p class=""></o:p></div>
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
Hodson Curator of the University Archives<o:p class=""></o:p></div>
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
Sheridan Libraries<o:p class=""></o:p></div>
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
Johns Hopkins University<o:p class=""></o:p></div>
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
3400 N Charles St<o:p class=""></o:p></div>
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
Baltimore, MD 21218<o:p class=""></o:p></div>
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
410-516-5493<o:p class=""></o:p></div>
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<a href="mailto:jsteele@jhu.edu" style="color: rgb(149, 79, 114); text-decoration: underline;">jsteele@jhu.edu</a><o:p class=""></o:p></div>
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
he/him/his<o:p class=""></o:p></div>
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<o:p class=""> </o:p></div>
</div>
<span style="caret-color: rgb(0, 0, 0); font-family: Menlo-Regular; font-size: 16px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">_______________________________________________</span><br style="caret-color: rgb(0, 0, 0); font-family: Menlo-Regular; font-size: 16px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class="">
<span style="caret-color: rgb(0, 0, 0); font-family: Menlo-Regular; font-size: 16px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">Archivesspace_Users_Group
mailing list</span><br style="caret-color: rgb(0, 0, 0); font-family: Menlo-Regular; font-size: 16px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class="">
<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org" style="color: rgb(149, 79, 114); text-decoration: underline; font-family: Menlo-Regular; font-size: 16px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;">Archivesspace_Users_Group@lyralists.lyrasis.org</a><br style="caret-color: rgb(0, 0, 0); font-family: Menlo-Regular; font-size: 16px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class="">
<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" style="color: rgb(149, 79, 114); text-decoration: underline; font-family: Menlo-Regular; font-size: 16px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</a><br style="caret-color: rgb(0, 0, 0); font-family: Menlo-Regular; font-size: 16px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class="">
</div>
</blockquote>
</div>
<br class="">
<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>