Differences

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

--- opac:bibtemplate [2010/05/05 12:21] – created miker
+++ opac:bibtemplate [2022/02/10 13:34] (current) – external edit 127.0.0.1
@@ Line 7: / Line 7: @@
 Before BibTemplate, only a portion of the total bibliographic data was readily available to Evergreen admins and developers for the purpose of customizing the OPAC.  With BibTemplate we hope to break out of this situation, and make OPAC customization more flexible and future-proof.
-====How to use BibTemplate in Evergreen 1.6====
+=====How to use BibTemplate in Evergreen 1.6=====
 BibTemplate arrived in Evergreen version 1.6.0.0.  In this first version the capabilities are somewhat limited, and while you can access all of the bibliographic data that unAPI can deliver, formatting is not as flexible as we want.  Also, BibTemplate only knows how to retrieve bibliographic records, not metarecords or direct holdings data, in Evergreen 1.6.  However, even with these formatting and display restrictions, enormous progress has been made in providing better and more useful bibliographic data display.
-===HTML API===
+====HTML API====
 BibTemplate follows the Dojo convention of adding attributes to existing (X)HTML in order to progressively change its behavior.  The 1.6.0 HTML API consists of a set of attributes that are added to existing OPAC markup, and fall into two classes:
@@ Line 45: / Line 45: @@
 </code>
-===JavaScript API===
+====JavaScript API====
 In order for BibTemplate to find the **slot markers** and invoke the **slot formatters** JavaScript renderer must be instantiated and called.  This must be done for each record that is to contribute to a pages display.  The API for this is simple and straight-forward:
@@ Line 59: / Line 59: @@
-====How to use BibTemplate in Evergreen trunk (to become 2.0)====
+=====How to use BibTemplate in Evergreen trunk (to become 2.0)=====
@@ Line 65: / Line 65: @@
-===HTML API===
+====HTML API====
 BibTemplate follows the Dojo convention of adding attributes to existing (X)HTML in order to progressively change its behavior.  The 1.6.0 HTML API consists of a set of attributes that are added to existing OPAC markup, and fall into two classes:
   * The **slot marker** -- Elements that denote the location of bibliographic data to insert
-  * The **slot formatter** -- Elements that specify how the named data should be formatted for display
+  * The **slot formatter** and **template values** -- Elements that specify how the named data should be formatted for display
 ==Slot Marker==
@@ Line 129: / Line 129: @@
 </code>
-===JavaScript API===
+====JavaScript API====
 In order for BibTemplate to find the **slot markers** and invoke the **slot formatters** JavaScript renderer must be instantiated and called.  This must be done for each record that is to contribute to a pages display.  The API for this is simple and straight-forward: