1. The token is a placeholder for all the values listed in the library's Material Type table. This table can be accessed through any Millennium module from the drop down menu Admin | Parameters | General | Fixed-length fields | Mattype.

2. An alternate scenario with this token is that for some libraries it could be controlled by a file on the system referred to as matmenu, which is a custom material type limit menu that Innovative has to maintain for the library. This file exists in the data directory on the server. This file is not accessible by the library, and if it needs to be modified, there is a service commitment (CSDirect at Support -» Service Commitments -» WebPAC -» Edit the Limit by Material Type menu)

NOTE: How do you tell if your library is using these special files? If the values seen in the WebPAC in the dropdown lists for these limits does not contain all the valid codes from the Material Type or the Locations table, then the library is using the files. See WebPAC Service Commitments on CSDirect.

The second example is the {toplogo} and {botlogo} tokens. Added to static Web pages, they are placeholders for information that is kept elsewhere on the system. They work in the same way as the {mattype} token. However, with these two tokens, the information is kept in the Web server directory itself in the form of html pages, toplogo.html and botlogo.html.

These tokens work in conjunction with the TOPLOGO and BOTLOGO Web Options to allow the library to provide consistency, in look and feel, throughout the WebPAC. These Web Options cause the above html pages to display on all system-generated screens.

Here's the {toplogo} token in the mainmenu.html page.

When we look in the Web server, we see the toplogo.html file listed there.

Note there is also a toplogo_loggedin.html page.

NOTE: Any file (html, gif or jpg) listed in the web directory can be viewed in a browser by using the "direct link" approach. Here are two examples:

http://LibraryIP/screens/toplogo.html

We can tell that this is the toplogo.html page because the logo is there on the left and the top links are there on the right. Here it displays on its own without the style sheet or other functioning elements of the WebPAC.

However, viewing the mainmenu.html page through a browser with all elements working together, we see this:

A third type of token is that which may only be enabled or disabled. An example of this is the {searchtool} token on a few forms, for example, bib_display.html, patron verification forms, and request_result.html. This token adds a list of drop down indexes and a search input box into the page. For libraries that have scopes, it also adds the scope drop down menu.

Disabling that token by moving it over results in:

If the values of the token are customizable elsewhere in the system (for example, the fixed field table for Material Types), you should change them there. Otherwise your only course of action is to view the source and hardcode that HTML into your page instead of using the token, adjusting it as desired. This means that whenever you upgrade software, you will need to confirm that the token's behavior hasn't changed. And if you update the table, you will need to go back to update the hard coded HTML as well.

Many features require tokens to be added. For instance, if the library wants to allow requests (also referred to as holds) to be placed from the bibliographic record display, a {holds} token must be present in the bib_display.html page.

For additional information, refer to the Innovative Guide and Reference, page # (106941): Customizable WebPAC Forms.

For additional information, refer to the Innovative Guide and Reference, page # (107017): TOPLOGO for Logged-in Patrons Custom Form.

For additional information, refer to the Innovative Guide and Reference, page # (105804): (ASAA) Advanced System Access and Administration.