Evergreen DokuWiki

The Template Toolkit OPAC (TPac) is a new Evergreen catalog built using a combination Perl's Template Toolkit and Apache/mod_perl. The primary design goals for the new catalog are speed and accessibility. This is accomplished by leveraging server-generated content in lieu of JavaScript rendering on the client. The project started as a clone of the custom King County OPAC skin. The new skin uses the same design elements, but essentially all JavaScript has been removed and replaced with Template Toolkit components for page rendering.

Initially, TPac will be merged into Evergreen 2.2 as a drop-in replacement for the HTML-only Slimpac. With minor configuration, it can also act as a drop-in replacement for the standard OPAC. In time, …

• Speed (initial page loading and rendering)
• Cross-browser consistency
• Flexible template engine (overlays, etc.) improves skinning
• Accessibility
• gettext-based string translations
• Reduced per-feature speed cost
• Simplified error tracking. (Errors occur on the server).
• Reduced variability of code in the wild (JS caching)
• Reduced bandwidth requirements
• Reduced client resources (RAM/CPU) requirements
• JavaScript/AJAX is still an option when needed (e.g. added content, staff client integration)

The long-term community goal is implement all existing OPAC features in TPac. Not all features have yet been added. Some new features have been implemented along the way.

• Credit Card Payment
• Fines History with Receipt Email/Print Options
• Circulation History
• Holds History
• Action/Trigger Notification Preferences
• On-the-fly lists
• Batch holds from lists / bookbags
• Improved options for hold overrides
• Recent Staff Searches (pending merge)
• Bookbag Enhancements (pending merge)
  • Descriptions, Record Notes, Sorting, CSV Export, new bookbag search filter

• Facets Display
• Enhancements to the advanced search interface (details to follow)
• Patron Saved Searches

• Display MFHD-based serials holdings (2.0+ "new" serials do display, and users can place issue-level holds)
• Some added content components have not been re-integrated.
• Widget-based access to all search indexes (see "Advanced" button in current OPAC)
• Search Range
  • TPac does not presently maintain the concept of "Search Range" at the UI level like the current OPAC. In other words, it's not possible to search at Branch B while including results from System S. (In TPac, one would simply search at System S). This primarily affects the results page. In the current OPAC, you might see copy counts at different levels of the organizational hierarchy (consortium, system, branch, etc.). In TPac, you only see copy counts for the location (consortium, system, branch, etc.) you are searching.