[ISLMA-Share] Chromebook cart management question

[Email list for the Illinois School Library Media Association]

We don't keep track of which cart Chromebook goes to which student but they
do have to login to the computer so activity is tracked. I'm not sure why
they don't track which student has which number in case one goes missing
though. That's our IT guy's realm.

We do however have 15 Chromebooks that can be checked out from the library
-- we just use Destiny's Asset Manager for this and other tech items. They
can only have them for one class period and never overnight.



On 6 December 2017 at 12:53, Email list for the Illinois School Library
Media Association <islma at list.railslibraries.info> wrote:

> This is a question for any schools, particularly high schools not 1:1 who
> have Chromebook or laptop carts shared between teachers throughout the day,
> or if you had carts before you went 1:1, which is our situation.
>
> Do your teachers track which student uses which device? If so how?
> If not why not?
>
> Also, do you now or did you ever check devices out individually while at
> school from the library to students, and if so how do/did you track that?
>
> Thanks much for any ideas you can share.
> Pam
>
>
> *Pamela Huff*
> Teacher/Librarian
> Learning Center Director
> *Johnsburg High School*
> 2002 W. Ringwood Road
> Johnsburg IL 60051
> *815-385-9233 <(815)%20385-9233>*
>
> phuff at johnsburg12.org
>
>
>
> _______________________________________________
> ISLMA-Share mailing list
> islma at list.railslibraries.info
> For list archives and subscription options, visit:
> http://list.railslibraries.info/cgi-bin/mailman/listinfo/islma
> To unsubscribe, send a message to:
> islma-leave at list.railslibraries.info
>



-- 
*Kari Stevenson*, *MLIS*
Teacher-Librarian / Castle View HS
Douglas County Public Schools
303.387.9100
klstevenson at dcsdk12.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.railslibraries.info/pipermail/aisle/attachments/20171206/2ca7a111/attachment-0002.html>