Hi Emma

 

We have Mifare chips in our student/staff ID cards to get in and out of buildings. On our cards the 7-digit ID number is in sector 1,  block 0 and the 14-digit barcode (which includes the ID number) in sector 1, block 1.

 

Our D-Tech selfcheck machines have a proximity reader and also a barcode scanner - we have external users who just get a paper library card with no chip, so we need to provide both options for checking out books.

 

Our Lapsafe laptop cabinet only has a proximity reader.

 

At the helpdesk we use barcode scanners to scan ID cards.

 

When the University was setting up Mifare cards, the library insisted that they should still have barcodes printed on them. If a student loses a card, the replacement will have a different barcode, so we can block the original in Sierra. The library receives an email when a replacement card has been issued, and we update Sierra manually.

 

We get a nightly feed from our student record system and this is loaded into Sierra overnight with Scheduler. The file includes student IDs and barcodes.  I don’t know anything about Sierra APIs but it would certainly be useful to have patron records updated more frequently, especially around registration time!

 

Best wishes

Claire

 

Claire Beach

Senior Learning Resources Assistant (Systems)

Library and Learning Resources
London South Bank University
103 Borough Road, London, SE1 0AA

Tel: +44 (0)20 7815 6659
Email: [log in to unmask]

 

 

Hi all,

 

We currently use proximity readers to get in and out of our library building but are still using barcodes with the self service machines (from 3M) and self service laptop machines (from Lapsafe).  Our student data, including the barcode information, all comes from our student registry system (SITS).

 

Our IT team are keen for us to move away from using barcodes to using proximity readers at our self service systems so I have been tasked with gathering information and was wondering if the helpful people in the EIUG community can help with answering the following:

 

1.       Do you use proximity readers at your self service systems?

2.       If so what information is programmed on to the chip in the card to identify the user?

3.       How is this information added to your Library system? (ie does it come through from your registry system or elsewhere and how often is the record feed)

 

Any information you can provide is gratefully received.  Also, as a Sierra site does anyone know if there is an API currently available to allow real time updating of our LMS from registry and if there is one is anyone currently using it?

 

Thanks in advance

Emma

 

 

 

 

Emma Hollinshead BA (HONS), PGDip ILM, MA

Systems Specialist

Library Services

Aston University

Aston Triangle

Birmingham

B4 7ET

 

Direct dial:     0121 204 4503

Internal dial:   4503

 

 

Library web page: http://www.aston.ac.uk/library

 

ü   Please consider the environment before printing this email