<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=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:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
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.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@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">Benn,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Alex is exactly right. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">At Yale, we use the length configuration to help ensure a basic level of validity (one of our repositories has 9 character barcodes, and the rest have 14 character barcodes). I can also add that during the development of the top container
module, I was hopeful that we might be able to include the ability to validate check digits for a few different barcoding systems as additional configuration options. It was decided not to pursue that option at the time, but I imagine that such a thing could
definitely be handled in a plugin. I’m not entirely sure how it would be handled throughout the application, but I expect that it could be baked into the JSON and database schemas.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I wrote a process in XSLT to verify barcode check digits according to the Luhn algorithm (<a href="https://en.wikipedia.org/wiki/Luhn_algorithm">https://en.wikipedia.org/wiki/Luhn_algorithm</a>), if that would be of interest. What types
of barcodes do you use? I had been meaning to add the barcode-digit check to our EAD validation process at some point anyway, so this is a good reminder to do that
<span style="font-family:"Segoe UI Emoji",sans-serif">😊</span>. So far, I have just been using that check during a project to reconcile item records in our ILS with top container records in ArchivesSpace. In each case, I’ve stumbled across a handful of barcodes
with invalid check digits, so you’re right that those errors definitely will creep in when left unchecked.<o:p></o:p></p>
<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>
<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>Alexander Duryee<br>
<b>Sent:</b> Monday, 24 June, 2019 10:22 AM<br>
<b>To:</b> Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org><br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] barcode validation for ASpace<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">Benn,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">It's possible to validate barcodes for length via ASpace by modifying config.rb (ref.
<a href="https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Farchivesspace%2Farchivesspace%2Fblob%2Fmaster%2Fdocs%2Fuser%2Fconfiguring-archivesspace.md&data=02%7C01%7Cmark.custer%40yale.edu%7C3c207da319d44f12d2e608d6f8af5bbc%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C636969829396148931&sdata=7a4EoOyA3sfChlyeoaqLZbYgMyPDzXF9k7hQKrnIaQA%3D&reserved=0">
https://github.com/archivesspace/archivesspace/blob/master/docs/user/configuring-archivesspace.md</a>). If the min and max values are set to the same length, then barcodes will only validate if they're either 0 or that exact length. You won't need to do anything
elaborate to implement this - just add the correct values to config.rb and restart ASpace, and it'll immediately go into effect.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I'm not aware of anything in ASpace that will do more elaborate validation (e.g. verifying that a barcode's check digits are correct); this would likely require either a plugin or feature request.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">--Alex<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Fri, Jun 21, 2019 at 1:39 PM Benn Joseph <<a href="mailto:benn.joseph@northwestern.edu">benn.joseph@northwestern.edu</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">Good afternoon,</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">Over the past few years, our standard procedure when processing a new collection has been to barcode the finished boxes and assign those barcodes to
their Top Containers in ASpace. </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">ArchivesSpace does a great job of keeping a user from assigning a barcode that has already been assigned elsewhere--which we recently discovered after
mistakenly being given a sheet of piggyback barcodes that had already been assigned to various other collections. The system reports an error: “Barcode – A barcode must be unique within a repository”. Great!</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">One thing it doesn’t do is check for valid barcodes against a schema. For instance, we try to be very careful about only using barcode scanners to enter
barcodes into ArchivesSpace, but every now and then one will get entered by hand, or there will be an accidental keystroke after scanning. In those cases, it would be ideal if ASpace were able to validate this number to ensure that it’s correct (I understand
that Alma does this using a Codabar 13 validation routine, though there are other validation options that would also look for a check digit). Would this be a plugin? A feature request? Would it even be possible?
</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">The reason it’s important for us to ensure barcode accuracy is that a large volume of our collections get sent offsite to a facility that uses GFA as
their inventory system. So, if we enter the barcode for a box that is incorrect in ASpace and GFA records it differently, it ends up being very difficult to recall that box if a researcher requests it.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">Thanks!</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">--Benn</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#0D0D0D">Benn Joseph</span></b><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#0D0D0D">Head of Archival Processing</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#0D0D0D">Northwestern University Libraries</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#4E2A84">Northwestern University</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:9.0pt;font-family:"Arial",sans-serif"><a href="https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.library.northwestern.edu&data=02%7C01%7Cmark.custer%40yale.edu%7C3c207da319d44f12d2e608d6f8af5bbc%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C636969829396158926&sdata=C9sj3YAaZjki5ritzmUdBTYMN1ncT7rvMA7B7LRotYI%3D&reserved=0" target="_blank"><span style="color:windowtext">www.library.northwestern.edu</span></a></span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:9.0pt;font-family:"Arial",sans-serif"><a href="mailto:benn.joseph@northwestern.edu%0d" target="_blank"><span style="color:windowtext">benn.joseph@northwestern.edu</span></a></span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#0D0D0D">847.467.6581</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal">_______________________________________________<br>
Archivesspace_Users_Group mailing list<br>
<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org" target="_blank">Archivesspace_Users_Group@lyralists.lyrasis.org</a><br>
<a href="https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group&data=02%7C01%7Cmark.custer%40yale.edu%7C3c207da319d44f12d2e608d6f8af5bbc%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C636969829396158926&sdata=kUMdoCxPj3F3zc3QIfInjShvGGAW%2BZA%2Fe438NVHZJLw%3D&reserved=0" target="_blank">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</a><o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"><br clear="all">
<br>
-- <o:p></o:p></p>
<div>
<div>
<div>
<div>
<p class="MsoNormal">Alexander Duryee<o:p></o:p></p>
<div>
<p class="MsoNormal">Metadata Archivist<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">New York Public Library<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">(917)-229-9590<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><a href="mailto:alexanderduryee@nypl.org" target="_blank">alexanderduryee@nypl.org</a><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>