Version 3.4.1.2173 is not an official release version yet. These release notes will be updated when new bug fixes and functionality are added before the final release.
listrecords command was not as good as it could be. The fix in 3.4.1.2173 gives a substantial performance improvement for this request.<xmlType>raw</xmlType> setting didn't output raw xml when using OAI: always grouped XML was generated. Fixed in 3.4.1.2164.scan in a Full Text indexed database used the old index tables people_name or thesau_term instead of the new full text index table. Fixed in version 3.4.1.2124.op="" attribute in a <field> element, as introduced in 3.4.1.2081 was ignored when the field used indirection. Fixed in 3.4.1.2102.domain = '' in the where clause when the domain field was actually stored as NULL. Fixed in 3.4.1.2087.command=getcontent gave a "cannot load file or assembly 'Magick.NET-Q16-AnyCPU, Version=12.2.0.0" error. Fixed in version 3.4.1.2070.contains operator, returned a SQL error: Invalid column name 'strippedterm'. This was fixed in WebAPI version 3.4.1.2024.from date search did not match the modification date in a database with indexed links: records from before the specified date were returned too. Fixed in version 3.4.1.2018.insertrecord call for a record with a link to an existing record, inserted the record all right but tried to create a new linked record instead of making the link to the existing other record. This was fixed in 3.4.1.1974.contains operator on two or more words in a Full Text enabled database, the words were treated as a phrase (words in that particular order) instead of independent words in any random order. This was fixed in version 3.4.1.1948.Previously there was no way to differentiate contains any from contains all: a contains search would always be a contains any search. And a contains all type of search was not available for q searches either.
In WebAPI version 3.4.1.2081 this has been solved. The operators containsall (short version: $), containsany (short version: _) and containsphrase (short version: ~) have been implemented. So with the following sample data:
- record 1 containing ti = buster keaton
- record 2 containing ti = diane keaton
You can do the following searches:
title containsany “keaton buster”
or
title _ “keaton buster“
would return both records as they both have keaton in the title.
title containsall “keaton buster”
or
title $ “keaton buster“
would return record 1 as that has both buster and keaton
title containsphrase “keaton buster”
or
title ~ “keaton buster“
wouldn't return any record because neither contains this phrase.
Moreover, in the <searchfields> section in adlibweb.xml, you can now specify per search field which operator to use if you perform a q search with the WebAPI. You do that by including an op=" attribute in a <field> element. The following operators are supported here:
= (also the default if the op attribute is not used)
>, >=, < and <=
containsall or $
containsany or _
containsphrase or ~
For example:
<searchfields>
<field op=”containsall”>title</field>
<field op="containsall">description</field>
<field op="=">object_number</field>
<field>association.subject
<field op="containsall">term.word</field>
</field>
</searchfields>
The SQL query to harvest each new set of records (after a resumption token) has been optimized, leading to an OAI performance improvement.
Since jpeg 2000 support in browsers is limited to Safari, only download (without display in the browser) of the jp2 file type is now fully supported by the Axiell WebAPI 3.4.1.1957 and up, while for display the file must be converted to a normal jpeg file by adding the &imageformat=jpeg parameter to the WebAPI getcontent call. The size of the downloaded image is determined by either the maxWidth and maxHeight setting in the image server configuration (set them to 0 for retrieving an unscaled file) or (if no explicit settings for width and height were made) by the default maximum dimensions used by the WebAPI.
From WebAPI version 3.4.1.1939, an Axiell.AzureBlobStorage.Plugin.dll plugin for the Axiell WebAPI is available to allow the ingest and retrieval of files in and from Microsoft Azure Blob Storage. Please see the full topic for more information.