Why are we sending people out to separate systems to do all of the things that they need to do as a customer? Let's talk about keeping them within the context of Drupal through the use of API's and creative theming! By doing this sort of thing whenever possible, we can present a more consistent brand to the customer and help make their experience with our organization more delightful.

Mark and Sarah, lead developers at Richland Library will walk you through:

• Our ultimate goal to trying to keep users out of the PAC and inside Drupal.
• The methods available to libraries in the Polaris ILS API.
• How we implemented My Account and fine payments.
• How you can allow new patrons to register online for a library card.
• How users can place items on hold and renew.
• Theming Polaris data to look like our Drupal data.
• Our "bento box" approach to create a combined site/catalog search.

This presentation will be a useful case study for site builders, developers, and decision makers in the library space and will also be useful for those who are interested in working with a large API set and pulling that functionality into the context of a Drupal site. If you are one of the many people regularly attend the Libraries BoF at DrupalCon, you should take a serious look at this session.

Learning Outcomes
By the end of this session, participants will be able to:

• Think critically about keeping the customer on their Drupal site via APIs when possible.
• Explain what's possible within a public library website when using the Polaris catalog system.
• Start thinking about a combined search that doesn't prompt the user to make a choice between catalog/site search.
• Walk away with a list of contrib modules and resources that are useful in building a public library site.