<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:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" 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 12 (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: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:Consolas;
panose-1:2 11 6 9 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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.5pt;
font-family:Consolas;}
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";}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:Consolas;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;}
@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="2050" />
</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=MsoPlainText><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Columbus
Metropolitan has for as long as I'm aware accepted just the library card number
for customers to check out materials. In fact, many of our customers memorize
their library card numbers and store the physical card in a secure place in
order to be sure that no one else can access the account. Not being able to use
just the number to check out would be a major inconvenience for many of our
customers, especially those who have multiple family members' cards to keep
track of, and would likely create more work for staff as we would have to check
IDs and/or look up accounts for customers who would otherwise just be able to
enter their card numbers.<o:p></o:p></span></p>
<p class=MsoPlainText><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoPlainText><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Requiring
customers to present the physical card in order to check out is essentially the
library attempting to control access to the card, which regardless of whether
or not the restriction is in place is ultimately the customer's responsibility.
That being the case, it's better customer service to allow the customer to
manage access to their account as they see fit. As long as we put reasonable
security measures in place (such as PINs and a process for blocking lost cards)
there shouldn’t be any difference between using the physical card or just using
the number. Credit cards allow you to use the card number to make purchases online
or over the phone (usually with a PIN or security code, just as we do), and
require you to monitor activity on your account and immediately report a lost
or stolen card. I can't see any reason why a library card should be any
different.<o:p></o:p></span></p>
<p class=MsoPlainText><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>C.
Nicholas Tepe<br>
Circulation Division Manager<br>
Columbus Metropolitan Library<br>
96 South Grant Avenue<br>
Columbus, OH 43215<br>
(614) 849-1203 fax (614) 849-1303<br>
<a href="mailto:ntepe@columbuslibrary.org"><span style='color:blue'>ntepe@columbuslibrary.org</span></a><o:p></o:p></span></p>
<div class=MsoNormal align=center style='text-align:center'><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
<hr size=2 width="100%" align=center>
</span></div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><a
href="http://www.columbuslibrary.org/"><span style='color:blue'>Columbus
Metropolitan Library</span></a> </span><a
href="http://twitter.com/columbuslibrary"><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif";color:blue;text-decoration:none'><img
border=0 width=14 height=14 id="Picture_x0020_2"
src="cid:image001.png@01CC60C5.ADC64DE0" alt="twitter_icon"></span></a><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> </span><a
href="http://www.facebook.com/columbuslibrary"><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif";color:blue;text-decoration:none'><img
border=0 width=14 height=14 id="Picture_x0020_3"
src="cid:image002.png@01CC60C5.ADC64DE0" alt="comments_facebook_icon"></span></a><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> </span><a
href="http://www.youtube.com/user/columbuslibrary"><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif";color:blue;text-decoration:none'><img
border=0 width=14 height=14 id="Picture_x0020_4"
src="cid:image003.gif@01CC60C5.ADC64DE0" alt=you-tube-icon></span></a><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
<div class=MsoNormal align=center style='text-align:center'><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
<hr size=2 width="100%" align=center>
</span></div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>-----Original Message-----<br>
From: Avery Shifflett [mailto:shifflav@oplin.org] <br>
Sent: Monday, August 22, 2011 11:43 AM<br>
To: oplinlist@oplin.org<br>
Subject: Re: [OPLINLIST] Smart phone Library Card application<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>I'd actually like to see some more discussion on the
security aspect of using barcode apps on smart phones. I think Dan Will
brought up an excellent point about patrons being able to enter any number they
like. I can see this becoming a huge problem. Anyone tech savvy enough to use
such an app will figure out that they can enter any number they like. As long
as the barcode meets the check digit, they can literally use anyone's account.
<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Personally, I'm thinking that if we accept it, we need a
photo ID as well (as the original poster asked). <o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>One person said: "there isn’t a way to verify that
the person holding the card is the person you issued the card to, so why would
the device be any different?", but I see it as being very different. A
physical card would have to be lost for someone else to use it, and the patron
can report it lost/missing. With a barcode app, anybody can use my account
even though my physical card is safely tucked away.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Thoughts anyone?<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Thanks,<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Avery Shifflett<o:p></o:p></p>
<p class=MsoPlainText>Carroll County District Library<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>========================================================================================<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Bruce,<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText> I have not seen this and since I don’t have a
“smartphone” I won’t be using it but, my opinion is that the library card was
given to the patron as their method of identification. They knew that when they
got the card. They cannot (reasonably) expect you to accept something else.
What prevents the user from putting just any number in the app and have it
create a barcode that might actually be someone else’s number? I can see where
this might be something to work towards for our patrons but, I think we need a
way to control the id creation (unless there is security controls that I am
unaware of).<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Be interesting to see how this plays out.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText> <o:p></o:p></p>
<p class=MsoPlainText>Dan Will<o:p></o:p></p>
<p class=MsoPlainText>Technology Supervisor<o:p></o:p></p>
<p class=MsoPlainText>Meigs County District Public Library<o:p></o:p></p>
<p class=MsoPlainText>willda@oplin.org<o:p></o:p></p>
<p class=MsoPlainText>740.992.5813<o:p></o:p></p>
<p class=MsoPlainText>740.992.6140 (fax)<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
</div>
</body>
</html>