|
As seen in previous sections of this tutorial many forms in the web server directory require a command link in order to function properly. Additional forms spoken of here that require command links are acquire_web.html and suggest_web.html.
There are also a few pages that will need just "direct links." A direct link would look like http://libraryIP/screens/help_index.html.
NOTE: Remember all pages, forms and images are under the same /screens directory.
All direct pages are informational and are not required by the web server: help_index.html, libinfo.html, feeds_examples.html, resources_index.html, etc.
An example of an informational page that only requires a direct link is help_index.html. The tabs lead to other informational direct link pages.
And what we see below are a combination of command link forms and direct link pages. The "Suggest a Title for Purchase" form requires the /acquire command link.
The feeds_example.html file is a sample page to show how the library may use incoming feeds. Incoming feeds, of course, can be added to any static page, and if the library has purchased the product Feed Builder, they can create outgoing feeds to add anywhere they wish as well.
There are other products that include html pages or forms in the set up. See the Innovative Guide & Reference and Innovative Product links below for more information.
Links to these forms or pages may be placed anywhere the library wishes. Remember to check the Innovative Guide & Reference for possible tokens that may be used on the forms. You will not find, however, information on the direct link pages spoken of here. They are simple html pages and only the {toplogo} and {botlogo} tokens may be used on them.
NOTE: What's important to remember here is that although these pages can be scoped and internationalized, the {toplogo} and {botlogo} tokens do not work in these direct link pages for WebPACs of other languages. The full coding of the toplogo.html and botlogo.html must be inserted into the pages. Please see the Alternate languages section of this tutorial.
For additional information, refer to the Innovative Guide & Reference, Page #106941: Customizable WebPAC Forms.
For additional information, refer to the Innovative Guide & Reference, Page #107081: Using AirPac.
For additional information, refer to the Innovative Guide & Reference, Page #107007: Using Kids Online.
For additional information, refer to the Innovative Guide & Reference, Page #107086: Using Ecommerce.
For additional information, refer to the Innovative Guide & Reference, Page #106995: Using Patron Self Registration.
For additional information, refer to the Innovative Guide & Reference, Page #107138: Using Program Registration in the OPAC.
For additional information, refer to the Innovative Guide & Reference, Page #106843: Using Community Reviews.
For additional information, refer to the Innovative Guide & Reference, Page #106987: Using Feed Builder.
| 
