LISTSERV mailing list manager LISTSERV 16.5

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

CODE4LIB Home

CODE4LIB Home

CODE4LIB  April 2007

CODE4LIB April 2007

Subject:

Re: Temporary library cards via Unicorn?

From:

Michael McCulley <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Tue, 24 Apr 2007 08:43:02 -0700

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (101 lines)

 
See interlaced notes below, Don..
 
P. Michael McCulley, Librarian II / Information & Technology
San Diego Public Library, 820 E Street, CA 92101-4806
Phone: 619-238-6678 / FAX: 619-238-6639
E-mail: [log in to unmask] 

>>> [log in to unmask] 4/23/2007 4:29 PM >>>

If I understand you correctly, you want to allow "instant
registration" so that a user can register and immediately use online
databases, without having to step foot in a library?  Further, this is
something you anticipate for the future, and not something you want
_just_ for migration?

>> Yes, exactly.. we have the option of doing it now with DRA Classic, if we can without too much heavy lifting.. but, we also can just work on the Unicorn upgrade for this, deploying it as a new eCard option when we hopefully launch that on/about August 2, 2007..

Assuming I'm understanding your correctly, I have a couple ideas.  All
in all, it depends really on how you authenticate access to your
databases (SIP/NCIP or just dummy 'Does this meet the rules for a
valid number'?-type authentication).  I'm going to assume that it's
the second (or, perhaps if you use number 1 you can also check number
2 if number 1 comes back with a 'soft' failure [user not registered...
denial would be caused by delinquency/expiration/etc]).

>> Authentication varies here, like I imagine most libraries.. we do have EZProxy, and I was looking again yesterday at Useful Utilities for possible notions to use.. right now, card number and PIN failure are pretty dead-end for users, except to call in the problem and "we" fix it manually in the system (renew their card, change the PIN, etc.)..

My first thought would be to create a "dummy" registration system.  A
person fills out a form online.  The contents of this form are
e-mailed to a library.  The system generates a number that meets the
validation criteria for the databases, but would not be valid for the
PAC or the like.  For example, if your libraries use a patron barcode
scheme 2BBBBXXXXXXXXC (where B is a branch ID number, XXXXXXXX is the
patrons' "serial number" at that particular branch and C is a
mathematically-calculated checkdigit), your "electronically-generated"
barcode numbers could use a branch ID of something you'd be unlikely
to utilize in the system (such as 9999, so a sample barcode may be
29999000000014).

>> This may indeed work, and I'm thinking to host this dummy system off the server with EZProxy running on it.. our schema for the card numbers is 01336xxxxxxxxx, but I don't know if we can allow either DRA Classic or Unicorn to accept other faux numbering schemes, perhaps.. good ideas!

A second option may be to frequently create a number of "dummy" patron
records with real barcode numbers.  These barcode numbers will then be
placed in a database on your web site.  A patron will register using a
web form, and when he/she clicks "submit" the application will be
e-mailed to the library staff.  He will then get his real card number
and PIN and can use this for requesting items in the PAC/etc.  He
would then be instructed to come to the library to get his actual
card.  The staff would take the e-mail application and update the
"dummy" registration to reflect his actual data.

>> We envisioned these temp cards to be upgradable to permanent (real) cards, by any visit to any library.. the temp record would just be updated manually with the holder's information, and a "real" barcode would be added (via scan) to the record, replacing and overwriting any "temp" number.. you can see the way this was done on the Sirsi Horizon system by Boston Public/Metro-Boston Library Network here..
http://catalog.mbln.org/ipac20/ipac.jsp 
 
>> I like how the user/patron gets to pick their own PIN (personal identification number)..

A third option would be to not utilize numbers at all.  If you can add
an authentication to your database provider to support access from a
referer page, you could create a temporary-use form on your web site.
A user would have to fill this out, and upon completion he can access
your databases (because the referer would be your web site).  A
downside is not all database vendors support this type of
"authentication", and many firewalls are beginning to block
HTTP_REFERER.
 
>> Interesting notion.. but, with the variations in the some 80-odd databases here, this would be a more problematic route to go down..

As a final note, if Patron Self Registration from the OPAC is a
feature you may find useful (for databases or otherwise), file an
enhancement request with SIRSI.  Quite a number of systems' DO support
a self-registration mechanism, and chances are it's probably on their
"to-do list" anyway... But, if people start asking for it, the
priority will rise!
 
>> I'm just getting access to the Sirsi Support Forums, and yes, I intended to ask the members there about ideas for this, and recommend via channels they officially try to do this as a system enhancement.. maybe it will shoot up the priority list ;)..

Good luck in your migration, and I hope this helps!
--Don McMorris

>> Incredibly helpful, Don.. I owe you beer+ :)..
 
Best,
Michael

On 4/23/07, Michael McCulley <[log in to unmask]> wrote:
> We have the older Sirsi DRA Classic system here at SDPL, and while we are migrating soon to Unicorn from SirsiDynix, we already can see something we're interested in doing that seems "beyond" Unicorn's capabilities.
>
> Has anyone seen or heard of coding/scripts or hacks/workarounds to provide eCards (temporary library cards) via Unicorn? We'd like to issue temporary cards via the Unicorn interface or our public Web site for "immediate" access to the databases, say good for 30-60 days, and, later, they can be upgraded at any of our library to a full-access library card. As an aside, we'll have the hosted version of Unicorn, so we won't have the system/files on any local servers we can access.
>
> We've noticed with interest that some Horizon systems, III, CARL, etc. can do this, but thus far, I can't see anyone with Unicorn that has done this. Any type of library (academic or public) is a good source, if you've heard of something. Please drop me a note via e-mail, or post here.
>
> Thanks in advance,
> Michael
>
>
> P. Michael McCulley, Librarian II / Information & Technology
> San Diego Public Library, 820 E Street, CA 92101-4806
> Phone: 619-238-6678 / FAX: 619-238-6639
> E-mail: [log in to unmask] 
>

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager