Hi Thomas!

Since we are a Google Apps school, we have two systems in place. For the school's two computer labs, I created separate calendars for them and then shared them to all my teachers with editing privileges. They sign up for the two labs (outside of the library) independently through their own Google calendar. The only flaw so far is that you cannot see who makes changes - no revision history. So it is an honor system.
Inline image 1

For the mobile equipment such as Projector carts, I set up a Google Doc with a school-year monthly calendar. I put all the docs in one folder labeled AV Equip and shared the folder to all my teachers. They can add themselves to the Google Doc for the days they want. There is revision history on Google Docs, so it works pretty well. My biggest problem is with teachers taking equipment and not signing up on the calendars. 

Inline image 2

Shannon McNeice
Library Media Specialist
Sedgwick Middle School
West Hartford, CT 06107
shannon_mcneice@whps.org



On Mon, Dec 17, 2012 at 8:26 AM, Vaghini, Thomas <vaghinit@stafford.k12.ct.us> wrote:
Good Morning Fellow Librariae,
 
We are now a 'Google school' and I'd like to use google calendar for signing up / displaying bookings for computer labs, carts, and resources. I want to know how some of your schools might handle using google calendar for these purposes. I want teachers to see the bookings and be able to 'book' thier own times into the calendar for these resources. But maybe to keep it orderly library staff should be the ones updating the calendar bookings.
 
How might you be utilizing google calendar? Best practices?
 
Thanks folks,
 
Thomas

_______________________________________________
CASL-L mailing list
CASL-L@mylist.net
http://mylist.net/listinfo/casl-l




--






CONFIDENTIALITY NOTE:
This West Hartford Public Schools e-mail may contain confidential information. It is intended solely for the original designated recipient(s). 
Any other use is prohibited and access to this email by anyone else is unauthorized. 
Any opinions expressed are those of the author and are not necessarily endorsed by WHPS.