[aisle] Tracking Loaner Chromebooks/Chargers

[pippine]

I have a set amount of loaners cataloged into the library catalog and check they get checked out to students. When they get checked out, I tell them to bring them back at the end of the day and 95% of the time they do. I have also in the past had help at the end of the day and use that help to go around and collect the devices that are checked out.

Lizz Pippin
Media Specialist
Charleston Middle School
________________________________
From: AISLE <aisle-bounces at list.railslibraries.info> on behalf of Beth Goodrum via AISLE <aisle at list.railslibraries.info>
Sent: Wednesday, May 18, 2022 1:20 PM
To: AISLE-Share: Association of Illinois School Library Educators discussion list <aisle at list.railslibraries.info>; lochs at ms.k12.il.us <lochs at ms.k12.il.us>
Cc: Beth Goodrum <bgoodrum at rccu1.net>
Subject: Re: [aisle] Tracking Loaner Chromebooks/Chargers

We use a program called Incident IQ. To track devices daily, I use a paper spreadsheet then input the info into IQ at the end of the day. There, you can see how many times the student has had "tickets" (that is what IQ calls it), why they needed a device (forgot, not charged, broken, etc). IT can see every ticket made and who has each Chromebook.

Hope this helps!

On Wed, May 18, 2022 at 12:35 PM Lauren Ochs via AISLE <aisle at list.railslibraries.info<mailto:aisle at list.railslibraries.info>> wrote:
Hi all!

Can anyone who has to lend loaner chromebooks/chargers talk to me about how you keep track of them? I'm looking for a way to only see current items out throughout the day, but also be able to analyze past data like how many times someone has borrowed something.

Backstory: We have the items barcoded and keep track of them using a spreadsheet shared with IT staff. We check them off when students return them and hide the row, but this makes it difficult to use the spreadsheet for data without duplicating the tab every time we want to know how many times a student has checked out a loaner. Filtering doesn't really work because there are too many variables. We also tried using Destiny to do loaners, but IT staff couldn't easily see the loaner situation, and I have to differentiate between loaners for repairs and loaners for forgetfulness so I can get passes to those that didn't return equipment at the end of each day, and Destiny doesn't differentiate that very well.

I would appreciate any tips/hacks/programs, etc. that may save me some time next year!

Thanks!
Lauren Ochs
School Librarian
Mahomet-Seymour High School
lochs at ms.k12.il.us<mailto:lochs at ms.k12.il.us>

Confidentiality Notice: This message and any attachment thereto is for the sole use of the intended recipient(s), and is covered by the Electronic Communications Privacy Act (18 USC 2510 et seq). It may contain information that is confidential and legally privileged within the meaning of applicable law. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.MAILMAN_MIMEDEFANG
_______________________________________________
AISLE mailing list
AISLE at list.railslibraries.info<mailto:AISLE at list.railslibraries.info>

For list archives and subscription options, visit:
http://list.railslibraries.info/cgi-bin/mailman/listinfo/aisle

To unsubscribe, send a message to:
aisle-leave at list.railslibraries.info<mailto:aisle-leave at list.railslibraries.info>

https://www.aisled.org/


--
Beth Goodrum
Secretary - IT/Library Assistant
Richland County High School
618-393-2191 x 3225

Currently Reading<https://www.goodreads.com/user/email_signature_destination/141134101?utm_medium=reading_link&utm_source=email_signature>
[Book Cover]<https://www.goodreads.com/user/email_signature_destination/141134101?utm_medium=cover&utm_source=email_signature>
[Goodreads Logo] <https://www.goodreads.com/?utm_medium=gr_logo&utm_source=email_signature>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.railslibraries.info/pipermail/aisle/attachments/20220518/83b54979/attachment.html>