User Tools

Site Tools


dev:opac:template-toolkit:release_notes

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
dev:opac:template-toolkit:release_notes [2011/09/07 15:13] ericksondev:opac:template-toolkit:release_notes [2022/02/10 13:34] (current) – external edit 127.0.0.1
Line 1: Line 1:
-==== The Template Toolkit OPAC Release Notes ====+====== The Template Toolkit OPAC Release Notes ======
  
 The Template Toolkit OPAC (TPac) is a new Evergreen catalog built using a combination Perl's [[http://template-toolkit.org/|Template Toolkit]] and [[http://perl.apache.org/|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 [[http://catalog.kcls.org|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. The Template Toolkit OPAC (TPac) is a new Evergreen catalog built using a combination Perl's [[http://template-toolkit.org/|Template Toolkit]] and [[http://perl.apache.org/|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 [[http://catalog.kcls.org|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, ...+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, ...
  
-=== Design Benefits ===+===== Design Benefits =====
  
   * Speed (initial page loading and rendering)   * Speed (initial page loading and rendering)
Line 19: Line 19:
   * JavaScript/AJAX is still an option when needed (e.g. added content, staff client integration)   * JavaScript/AJAX is still an option when needed (e.g. added content, staff client integration)
  
-=== Features ===+===== Features =====
  
-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. +There is new location for [[dev:opac:template-toolkit:plan|the list of TPAC features and pending TPAC features]]
- +
-== New Features == +
- +
-  * 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 +
- +
-== Pending Features (Sponsored) == +
-  * Facets Display +
-  * Enhancements to the advanced search interface (details to follow) +
- +
-== Pending Features (Unsponsored) == +
-  * 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 configured search indexes  +
-    * See the "Advanced" button just below the search input box on the results page in current OPAC +
-    * In other words, widget-based access to search against any field configured in config.metabib_field where search_field=true +
-  * 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 +
  
dev/opac/template-toolkit/release_notes.1315422806.txt.gz · Last modified: 2022/02/10 13:34 (external edit)

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki

© 2008-2022 GPLS and others. Evergreen is open source software, freely licensed under GNU GPLv2 or later.
The Evergreen Project is a U.S. 501(c)3 non-profit organization.