<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:mv="http://macVmlSchemaUri" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (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:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:DengXian;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:Calibri;}
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.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;}
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:Calibri;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:Tahoma;}
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:12.0pt;
font-family:"Times New Roman";}
span.EmailStyle20
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle22
{mso-style-type:personal;
font-family:Calibri;
color:#1F497D;}
span.EmailStyle23
{mso-style-type:personal;
font-family:Calibri;
color:#1F497D;}
span.EmailStyle24
{mso-style-type:personal;
font-family:Calibri;
color:#1F497D;}
span.EmailStyle25
{mso-style-type:personal-reply;
font-family:Calibri;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.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:437142939;
mso-list-type:hybrid;
mso-list-template-ids:-1297285212 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;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style>
</head>
<body bgcolor="white" lang="EN-US" link="#0563C1" vlink="#954F72">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p>Hi All-</p>
<p><br>
</p>
<p>I'm closing in on releasing a test version of the label printing plugin but I had a few questions for the group.</p>
<p><br>
</p>
<p>1) The data model for top containers allows a top container to be linked to multiple resources, series and creators. What I've done for the moment is take all of the above and produce a concatenated list for each. So a resource title for a top container
could look something like:</p>
<p><br>
</p>
<p>"Resource 1 title; Resource 2 title"</p>
<p><br>
</p>
<p>Ditto for the resource id, series id and creator. Is that an approach that works for the group? The other choice that I've thought of would be to take the first entry for each. I'm also open to other ideas if someone has a brilliant suggestion!</p>
<p><br>
</p>
<p>1b) Since these could get very long, should they be truncated at all? And to how many characters/words?<br>
</p>
<p><br>
</p>
<p>2) Our current Dartmouth plugin includes a feature to enable searching by indicators only - either a space separated list or a numeric range, though the range search will produce some bizarre results for non-numeric indicators....
<br>
</p>
<p><br>
</p>
<p>Examples would be "1 3 5" or "[1 to 10]" Is this a feature that I should include or leave out for this generalized plugin?</p>
<p><br>
</p>
<p>Thanks!</p>
<p>Joshua<br>
</p>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> archivesspace_users_group-bounces@lyralists.lyrasis.org <archivesspace_users_group-bounces@lyralists.lyrasis.org> on behalf of Joshua D. Shaw
<Joshua.D.Shaw@dartmouth.edu><br>
<b>Sent:</b> Wednesday, August 17, 2016 11:18:15 AM<br>
<b>To:</b> Archivesspace Users Group<br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] Label Printing in the Browser - Whatwould be useful?</font>
<div> </div>
</div>
<div>
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">Hi All-<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">It definitely sounds like the best option would be to provide a picklist of fields/data to include on a label. I think that’s doable with a bit of extra head scratching....though maybe not in v.1;-)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">At worst, the plugin will provide a roadmap for others to enhance or adapt the plugin for their local needs. Given all of the variables and vagaries of printing, this will almost certainly not be a “perfect
out of the box” type plugin and will likely (certainly?) require some fiddling with the CSS to make things work properly in the local printing environment.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">The complicating factor here is that labels are physical objects (duh!) and have a limited & fixed amount of space available to shoehorn pieces in. Additionally, different browsers & printers don’t necessarily
obey the same rules when it comes to sizing, scaling and margins, etc. Allowing a picklist will make the procedure for setting up/printing a label a bit trickier as that will either<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-size:11.0pt"><span style="mso-list:Ignore">1)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt">require the end user to pick a set of fields, then check the print output and make sure it all fits on the desired label and then potentially go back and remove a field or two until things fit OR<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-size:11.0pt"><span style="mso-list:Ignore">2)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt">have a developer type (or anyone with CSS chops) muck about with the label CSS to get things to sit nicely for all of the locally defined layout/field choices<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">#2 will probably have to happen anyway if people are defining additional label types. And as mentioned above, there’s the additional fun factor of browser….irregularity… when it comes to printing and complying
with various CSS standards, which means that #2 will almost certainly have to happen no matter what.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Would it make the most sense to get things to a point where there’s a predefined set of fields that actually works in a couple of label types across most browsers and then make that available for others to
contribute to and help setup the picklist functionality?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Thoughts?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Joshua<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></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"><archivesspace_users_group-bounces@lyralists.lyrasis.org> on behalf of "Bowers, Kate A." <kate_bowers@harvard.edu><br>
<b>Reply-To: </b>Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org><br>
<b>Date: </b>Wednesday, August 17, 2016 at 10:45 AM<br>
<b>To: </b>Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org><br>
<b>Subject: </b>Re: [Archivesspace_Users_Group] Label Printing in the Browser - Whatwould be useful?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman""><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">I’m assuming that each of these datum are optional? In other words, it’s a configurable choice from among these pieces of information?</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">One that I would add would be collection creator.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Kate</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span><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><span style="font-size:11.0pt">From:</span></b><span style="font-size:11.0pt"> archivesspace_users_group-bounces@lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org]
<b>On Behalf Of </b>Caldera, Mary<br>
<b>Sent:</b> Wednesday, August 17, 2016 10:38 AM<br>
<b>To:</b> Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org><br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] Label Printing in the Browser - Whatwould be useful?</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Joshua, this is great. Thank you for sharing. Suggested additions are in blue, deletions and reasoning in red. Best, Mary</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#00B0F0">Parent Institution name</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#00B0F0">Repository name</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Resource Title</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Resource ID</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#00B0F0">Level of description (if “series”)</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#00B0F0">Component unique ID (if level of description is “Series”)</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#00B0F0">Top container label (“Container” or “Box”—this would have to be hardcoded, not come from AS data, I think)</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Top Container Indicator</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:red">Top Container Barcode (presumably the barcode is located somewhere else on the box, leave off to save space?)</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:red">Location String (locations change – wouldn’t want to reprint labels every time that happened, and maybe should not be public)</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:red">Location Barcode (locations change – wouldn’t want to reprint labels every time that happened, and maybe should not be public)</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span><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><span style="font-size:11.0pt">From:</span></b><span style="font-size:11.0pt">
<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>Brian Thomas<br>
<b>Sent:</b> Wednesday, August 17, 2016 10:11 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] Label Printing in the Browser - Whatwould be useful?</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">For us in TSLAC, this seems too specific. We have had a few situations that may necessitate the location string being omitted from the label. In case someone ever breached security after paging
a box, we wouldn’t want them to know where the box lives. Is there a way in the plugin, or code from the plugin, to choose to remove that specific detail? My 2 cents.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Thanks,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Brian Thomas</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Electronic Records Specialist</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Texas State Library and Archives Commission</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">1201 Brazos Street</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Austin, TX 78701</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">PH: (512) 475-3374</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">e-mail: </span>
<a href="bthomas@tsl.texas.gov"><span style="font-size:11.0pt;color:blue">bthomas@tsl.texas.gov</span></a><o:p></o:p></p>
<p class="MsoNormal"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__tsl.texas.gov_&d=CwMGaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=NYF1LGD79bUMnZ_xocCs-I49uGpSnJGyOTeVzDMh5Zs&m=sJiEwi4t0e_noS-fsyITvMdfEI7xSmsqszIDF6Fh4T0&s=W6zUfFppNJSXKheVwB82UhgUteb9LlNV8wFerUliptk&e="><span style="font-size:11.0pt;color:blue">tsl.texas.gov</span></a><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><img border="0" width="60" height="72" id="Picture_x005f_x0020_1" alt="id:image001.jpg@01D029A2.37194C70" src="cid:image001.png@01D1F879.0C431830"></span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span><o:p></o:p></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">From:</span></b><span style="font-size:10.0pt;font-family:Tahoma">
</span><a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org"><span style="font-size:10.0pt;font-family:Tahoma">archivesspace_users_group-bounces@lyralists.lyrasis.org</span></a><span style="font-size:10.0pt;font-family:Tahoma"> [</span><a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org"><span style="font-size:10.0pt;font-family:Tahoma">mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org</span></a><span style="font-size:10.0pt;font-family:Tahoma">]
<b>On Behalf Of </b>Joshua D. Shaw<br>
<b>Sent:</b> Wednesday, August 17, 2016 6:56 AM<br>
<b>To:</b> Archivesspace Users Group<br>
<b>Subject:</b> [Archivesspace_Users_Group] Label Printing in the Browser - Whatwould be useful?</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Hi all-</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">For those of you who were at the member forum in Atlanta, I briefly mentioned that we had had a plugin developed for us by HM (and have subsequently tweaked and modified) that allows us to print labels directly
from the browser. There were a few people who expressed some interest in this, so I thought I’d see what types of information people might find useful to see on a label in the hopes of taking what we already have and de-Dartmouthizing it so that it would *<b>hopefully</b>*
work for a wider audience.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">I was thinking that there are so many ways that people can potentially describe a collection that the baseline info on a label would probably be something along the lines of</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Resource ID</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Resource Title</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Top Container Indicator</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Top Container Barcode</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Location String</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Location Barcode</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Are there other pieces that people think are generic enough to include? Are the above too specific in some cases – ie are there cases where a container holds AOs from multiple resources?</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">The plugin will depend on the container manager functionality and will be (at least) v1.5.1 compatible assuming I can get things into shape;-) I plan to include at least two layouts so that others can get
a feel for what is possible in terms of label types. One will be a thermal roll type (a Dymo 30256 label) that we use and an Avery 5163 2x5 portrait layout.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Thanks!</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Joshua</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
</div>
</div>
</div>
</div>
</body>
</html>