Adlib API home page > Documentation > Release notes for wwwopac.ashx 3.7.14202

Release notes for wwwopac.ashx 3.7.14202

All field tags must have been defined in the data dictionary

The Adlib API as used by the current version of wwwopac.ashx implements a strict policy concerning the definition of field tags: all tags used in records that you read or write using the API, must have been defined in the data dictionary (the Adlib .inf files): if you're not reading or writing entire records (any and all tags from the record), but limit the reading or writing to specific tags from records, then only those tags really need to have been defined. So when you’re about to start using the new version of wwwopac.ashx for your website, you may encounter errors because of this, since it is not uncommon in Adlib applications for tags to have been defined on the screen only or to have ended up in records via an import or adapl procedure. Axiell ALM has several tools in development (currently called ValidateDatabase and RemoveTagsFromData) which you can use to track down any undefined tags in your records (amongst other functionality), after which you can still define them in the relevant .inf to solve the issue. Ask our helpdesk for the status of these tools and the accompanying documentation.

Fix for implicit truncated q= searching

Prior to wwwopac.ashx version 3.7.14202.1, q= searches were always implicitly truncated. From version 3.7.14202.1, wwwopac.ashx offers an optional truncation="true|false" attribute for the searchfields node in the adlibweb.xml file, allowing you to switch truncation on explicitly for all q= searches, whilst by default truncation is off (false). For example:

<searchfields truncation="true">

Fix for error when filtering on dataset

When you executed a query filtering the search result on dataset (like ...&search=TI=jaws* and dataset=intern), an "Object reference not set to an instance of an object" error was thrown. This bug has been fixed in version 3.7.14080.