Release notes for WebAPI 3.10.1.4057

Bug fixes

• A q-search and an equals search returned different results when searching for a comma-separated list of values: the q-search treated the list as a single value. This was fixed in version 3.10.1.4065.

• Selected facets did not work combined with addToQuery using a narrower search: the result for a selected facet would be the same as without the selected facet. Fixed in version 3.10.1.4060.

• An InvalidOperationException was generated when sorting on a second index (with dummy field) on a linked field. This was fixed in version 3.10.1.4044.

• Under some circumstances, using the Axiell generic media server plugin, the second call to a cached media file generated a Method not implemented error. Fixed in 3.10.1.4006.

• When you didn’t reference a groupConfiguration in the databaseConfiguration section, the adaplEnabled=true property set in the globalConfiguration section was ignored, so the storage adapl was not executed when creating a new record. Fixed in version 3.10.1.3999.

• When a multilingual field was used as facet, the error Object reference not set to an instance of an object occurred if there were records returned in which the field had a value without language attribute. This is a data issue in the first place, because all values in multilingual fields should have language attributes, but the fix in version 3.10.1.3985 makes sure that the error no longer occurs in this situation and that an empty lang attribute is returned in the XML.

New functionality

Header token for oai.ashx enabled

The wwwopac.ashx could already accept an API token via the header, but the oai.ashx still couldn't (where it was only accepted as a query parameter). This was causing problems for customers who use the OAI to support harvesting data for other systems where the end point needs to be protected. This was remedied in version 3.10.1.4043: the oai.ashx can now accept an API token via the header too.