NVLSL Consortium CSLA 2008.

655
-1

Published on

An overview of Napa Valley School Library Consortium

Published in: Education, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
655
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

NVLSL Consortium CSLA 2008.

  1. 1. Napa Valley School Library Consortium<br />A different solution for a very difficult time<br />Kate MacMillan, Sandy Biale, Michelle Holguin <br />
  2. 2. Who We Are & What We look Like<br />Napa Valley School Library Consortium Members *<br />Michelle, Susan, Lisa, Paula: SHUSD<br />Janis, Cathy: CJUSD<br />Michelle W, Alissa, Matilda; PARTNER<br />Loreen, Sandy ,Suzanne, Anne, Colette, Cathy, Roberta, Sean, Stefani, Pam<br />Terry, Diane, Amy, Nancy, Terry, Julie, Roberta, Janine, Deana, Tina, Bobbie, Grace, Joanne, Linda, Laura, Lorrie, Melissa, Louisa, Cathy, Deb: NVUSD<br />Kate: Library Services<br />Tim: IT: Bea, Aeries<br />
  3. 3. con·sor·ti·um<br /> <br /> a. An association or a combination…..for the purpose of engaging in a joint venture.<br />b. A cooperative arrangement among groups or institutions: a library consortium<br />
  4. 4. The Rationale for School Library Consortiums*<br /> Innovative solutions to support library management at the district and site level<br />Keep libraries open<br />Databases and automation programs stable<br /> Equal access to resources for all students<br />*An integrated Web based library system is required for this type of school library consortium<br />
  5. 5. What the NVSL Consortium Can Do<br />Provide technical hardware, stability and support<br />Provide training/networking<br />Host automation software & library databases <br />Provide managed library services as per MOU<br />
  6. 6. What the NVSL Consortium Cannot Do<br />Mandate District or Site staffing <br /> Mandate District or Site budgets<br />Deviate from the MOU* <br />*Agreed upon by member administrations<br />
  7. 7. What Are the Benefits?Consortium members benefit from peer support <br />Consortium host provides:<br />Up-to-date technology<br />Technical support<br />Hardware/Servers<br />Software upgrades<br />Database hosting/including backups<br />
  8. 8. What Other Benefits?<br />Autonomous cost efficient funding<br />Agreed upon managed library services as per MOU<br />District/Admin buy-in<br />Strength of numbers<br />Training and networking opportunities<br />
  9. 9. Cost Efficient Funding<br />
  10. 10. Fees = Funding<br />
  11. 11. Background: California School Districts<br />1998 – 2001 State funds for school libraries<br />Updated Collections <br />Sophisticated library automation programs<br />Outcome: improved school libraries <br />
  12. 12. Post California Public School Library Act of 1998 <br />Library and technology staffing not keeping pace with school library needs. <br /> Districts have difficulty funding necessary library services<br />…..or even keeping their libraries operational<br />
  13. 13. Background: Tough Times Require Innovative Solutions ( 2004 – 200?)<br />
  14. 14. Background: Funding Shortages<br />
  15. 15. Background … Spread All Over<br />Napa County: 612 square miles <br />Small rural districts: tiny remote sites: private/parochial schools <br />Little federal funding: average poverty level<br /> Minimal funding, less purchasing power of larger districts<br />
  16. 16. Background: NVUSD <br />NVUSD = acts as a COE<br /> ISP for the county <br />Established business relationship with surrounding districts, private/parochial schools<br />Technology and library staff to implement and support a library consortium <br />
  17. 17. Background: How It All Began…….<br />2003 Napa COE Curriculum Library<br />Server crash<br />Web Collection goes offline<br />Curriculum Library can’t circulate<br />IT asks NVUSD for assistance<br />Partnership formed<br />
  18. 18. Background: Consortium Partners<br />Napa Valley USD<br />Napa County Office of Education: 2004<br />Calistoga Joint Unified: 2005<br />Justin Siena High School: 2005<br />St. Apollinaris: 2006<br />St. Helena Unified: 2007<br />Blue Oak School: 2008<br />
  19. 19. Strength in Numbers<br />Consortium = members = power<br />
  20. 20. So What Technology Does the Member Need ?<br />Web based ILS program<br />Sufficient internal bandwidth<br />Sufficient to internet <br />Ensure speed<br />Variable depends on District size<br />.<br />
  21. 21. What Technology Does the Host Need?<br />Stable ILS-trained IT department<br />SQL based server<br />Sufficient bandwidth<br />Available staff to provide support to sites<br />
  22. 22. So …. What’s the Next Step?<br />Consortium host and member(s) agree upon<br />Memorandum of Understanding<br />MOU = a business plan <br />MOU = a menu of services <br />
  23. 23. The Glue That Holds It Altogether<br />The MOU (Memorandum of Understanding)<br />Board approved document that outlines services and charges<br />Protects both parties<br />A form of business plan<br />* ILS Lead included<br /> Memorandum<br /> of <br />Understanding<br />
  24. 24. Different districts, schools and libraries<br />Require<br />Different solutions while maintaining centralizedautomation services<br />Recommended Reading<br /> Management <br />
  25. 25. Management Styles<br /> Centralization = clearly defined structure<br /> Consortium = collaboration, loose structure <br />Centralization = top down management Consortium = open ended leadership<br />
  26. 26. Centralized Management<br />Centralization = all resources under one authority<br />All decisions from one source<br />Top down ‘spider’ management<br />
  27. 27. 3 C’s of Consortium Member Management<br />Members provide peer management through <br /><ul><li>Cooperation
  28. 28. Collaboration
  29. 29. Consensus </li></li></ul><li>Centralized ILS <br />Holdings on a single server <br /> Centralized automation administrators<br />Single point of contact <br />Standard automation features<br /> Standard student management queries<br />*Agreed upon at implementation<br />
  30. 30. The Relationships<br />
  31. 31. Most Important Relationship<br />
  32. 32. IT <br />Facilitates ILS implementation at the hardware level <br />ILS upgrades<br />Data queries and updates <br />Troubleshoot and/or fix the problem(s)<br />
  33. 33. Library Services<br />*ILS Administrator represents consortium and host <br />*DL: Site Teacher Librarian/ Media Specialist represents district <br />
  34. 34. Implementation Team<br />Vendor Relationship Vital<br />Training<br />Support<br />Communication<br />
  35. 35. Who Does What? <br />Library Services<br />IT/Technology<br /> Support<br />Training<br />
  36. 36. Technology<br />IT support includes*<br />*IT administrator<br />Student management specialist<br />Technicians<br />Bandwidth<br /> ILS Program<br /> SQL based Server<br />(Implementation Team) <br />
  37. 37. Library Services<br />Facilitates and supports ILS implementation at the consortium level<br />Provides managed library services including<br />Administrative guidelines<br />Initial training sessions<br />
  38. 38. Managed Services(as per MOU) <br /> District and/or site reports<br /> Library committee and district site visits<br />Collection development <br />Trainings; cohort meetings<br />Library 101 Help Page <br />Liaise with technical support <br />
  39. 39. Managed Services Collaboration<br />
  40. 40. Support: Annual Reports<br />Collection/circulation data including: <br />Collection maps; Collection reports <br />Annual inventory results<br />Weeding lists with recommendations <br />Site and aggregate reports to consortium schools and School Boards <br />
  41. 41. Library Services/Collection Development <br />Recommend curriculum/ standard based materials <br />Participate in site library committee <br />Provide current collection maps <br />
  42. 42. Collection Development Communication<br />Keeping track of list and requests<br />Titlewave Accounts<br />Baker and Taylor Web lists<br />Permabound Web lists<br />One account per site<br />Common password<br />
  43. 43. Staff <br />Provide growth and staff development opportunities to all members<br />User group/open circle training model<br />Network<br />Collaborate<br />Share<br />
  44. 44. Training*<br /> Training = all library staff<br /> Consortium decides needs and presenters<br />Correlates training sessions to needs<br />Provide networking and feedback opportunities<br />Request professional resources as needed <br />Open ended circle model <br />*biggest change <br />
  45. 45. Communicating, Networking & Sharing<br />How to keep the information lines open<br />How to keep information current<br />How to keep information available 24/7<br />How to keep information relevant <br />
  46. 46. Library 101 Help Page <br />Support Available 24/7<br />Archived trainings<br />Current Library information<br />Areas of interest for parents, students, teachers and library staff<br />Online resource links<br />Current newsletter<br />
  47. 47. Logical Hosts = County Offices of Education <br />Form consortium with member districts<br /> Node for the DCP (Digital California Project) and the Internet Service Provider (ISP)<br /> Expand existing technology to include school libraries<br />
  48. 48. The Outcome and the Result<br />Consortiums are cost efficient <br />Generate income to support the consortium host and pay for general support of the consortium member <br />Offer much needed support and direction to school libraries<br />
  49. 49. Thanks for taking Napa Valley USD School Library Consortium Guided Tour <br />Any questions or comments, please contact<br />Kate MacMillan<br />
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×