1. iboss pilot testing What are our goals? What can you expect? What do you need to do? When do you need to do it?

2. Goal: Familiarize staff with iboss filtering technology. Expectations:  Filtering will initially be enabled for wired staff PCs only.  VPN sites will be slightly delayed in this respect. (a routing issue affects MCM, STP, HPB and MOO) What you need to do:  Tell Greg B. your preferred start date for the staff pilot.  Share goals and expectations with staff.  Demonstrate the block page and adult bypass form.  http://www.scls.info/technology/erate/iboss-urls.html http://www.scls.info/technology/erate/iboss-urls.html Near term (Feb-Mar)

3. Goal: Familiarize staff with iboss, and test wireless filtering. Expectations:  The “Staff” channel of Enterprise Wireless will have filtering enabled after SCLS completes prep work.  Sites not having EW cannot pilot test wireless filtering at this stage of the project. What you need to do:  Share information and wait for more news.  Communicate with SCLS about non-EW wireless systems. Near term (Feb-Mar)

4. Goal: Test iboss for overblocking or underblocking. Expectations:  Filtering will have minimal impact on typical staff Internet use (ideally, no impact at all). What you need to do:  Have staff go about their normal business.  Use the adult bypass web form to temporarily work around any overblocking that may be discovered.  Report incidents of blocking errors (over or under). Medium term (Feb-Apr)

5. Goal: Adapt as needed to the adult bypass process. Expectations:  You may need to change policy and procedures for temporary library cards or passes.  Patrons may need their Koha date of birth field updated. What you need to do:  Think about possible impacts of bypass authentication.  Share information with staff, SCLS and other libraries. Medium term (Feb-Apr)

6. Goal: Fully articulate the block page and bypass form(s). Expectations:  Policy language and presentation style will go through a process of iterative improvements.  The final outcome will incorporate a mix of technical requirements and style preferences. What you need to do:  Poke the block page and think about its format and content; share feedback with SCLS and peers.  Post your policy on your website and let Greg know of any URL(s) that you want linked to the block page. Medium term (Feb-Apr)

7. Goal: Prepare for a patron pilot test and/or full deployment. Expectations:  The block page & bypass needs to be more polished first.  SCLS and library policies need to be updated first.  SCLS needs time to update network configurations before patron systems may have iboss filtering enabled. What you need to do:  Share information and wait for news of milestone dates.  Complete and publish your revised policies, PR, etc.  Let SCLS know of preferred testing or “go live” dates. Longer term (Mar-May)

8. Goal: Address any site-specific needs for full service. Expectations:  Each library may have unique needs or desired outcomes of implementing filtering on patron PCs or public wireless.  SCLS will consult with you regarding what is feasible and how our policies and final implementation plans might be fine tuned to accommodate your needs. What you need to do:  Think about desired outcomes, and share information.  Participate in the SCLS policy development process. Longer term (Mar-May)