Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Media Services Digital Tools topic
No spam. Unsubscribe anytime.
FCPS media services introduces parent book‑preference opt‑in; digital tools team outlines approval and accessibility process
Summary
Frederick County Public Schools media services and digital solutions staff updated the Curriculum & Instruction Committee on June 11 about a parent library book‑preference opt‑in, newly published library regulations and the district’s vendor review process for digital instructional tools.
Get email alerts on the Media Services Digital Tools topic
No spam. Unsubscribe anytime.
Frederick County Public Schools media services and digital solutions staff updated the Curriculum & Instruction Committee on June 11 about library services, a new parent book‑preference opt‑in, and the district’s process for evaluating digital instructional tools.
Mary Jankoski (media services) described this year’s launch of a parent “library book preferences” opt‑in feature that allows parents to create an account in the district’s library circulation system and block specific titles from checkout to their child. Jankoski said the feature went live in late September after an initial pilot and that staff have posted guidance and screenshots on the media services web page to assist parents with account setup. She told the committee that, to date, parent uptake has been limited and staff plan renewed communication and website refreshes over the summer to increase awareness.
Media services staff also summarized two recently published district regulations affecting library materials: Regulation 50101 (selection and approval of library materials) and Regulation 500‑06 (reconsideration of instructional materials already in use). The regulations formalize selection procedures and provide a process for considering concerns about materials; media staff emphasized those procedures apply to library and other instructional materials.
Eric Haines and the digital solutions team described their role supporting more than 70 premium digital tools: rostering, Schoology integrations, vendor liaison, accessibility reviews and troubleshooting. Haines said the team routes teacher support tickets through the district’s ServiceNow system and handled over 1,400 tickets this year. He explained that the district’s tool‑approval process includes curricular review (with curriculum specialists), accessibility review (digital solutions), data‑privacy review (Dr. Vedder’s team) and network/security review (Department of Technology Infrastructure) prior to procurement or deployment.
During Q&A board members raised concerns about parent awareness and usability of the opt‑in feature. Staff acknowledged an initial lag in communication when the feature debuted and said they will increase reminders, improve website placement and provide step‑by‑step screenshots. Staff also explained that the public catalog is searchable without opting in, and parents can filter by elementary/middle/high collections; the opt‑in preference list is a separate account setup that prevents checkout of opted‑out titles for the child tied to that account.
Board members asked about classroom/library time for book selection; media staff said elementary students receive a dedicated weekly media lesson (minimum 40 minutes) with at least 10 minutes commonly used for independent book selection and that secondary access varies by school and is more often scheduled collaboratively with teachers.
On digital tools, Haines reiterated that every digital product used by classrooms goes through the district’s approval workflow and that DTI is engaged for network/security review. He said his team evaluates accessibility features and works with vendors and curriculum teams to ensure tools meet state and district standards for assistive features where required.
No formal policy votes were taken. Staff said they will continue outreach to parents on the opt‑in tool, refresh website navigation in summer communications, monitor uptake and continue ensuring tools meet accessibility and privacy expectations before deployment.

