Release notes 6.5.2 SP3



6.5.2 SP3 release notes

Adlib Information Systems

Copyright © 2011 Adlib Information Systems B.V. ® All rights reserved. Adlib® is a product of Adlib Information Systems B.V. ®

The information in this document is subject to change without notice and should not be construed as a commitment by Adlib Information Systems. Adlib assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a licence and may be used or copied only in accordance with the terms of such a licence. While making every effort to ensure the accuracy of this document, products are continually being improved.

As a result of continuous improvements, later versions of the products may vary from those described here. Under no circumstances may this document be regarded as a part of any contractual obligation to supply software, or as a definitive product description.

Contents

Introduction 1

1 Improvements 3

1.1 Searching 3

1.2 Editing 3

1.3 ADAPL 6

Introduction

These release notes describe a number of improvements in the Adlib executables, which are implemented in Adlib 6.5.2 service pack 3 (build 6.5.2.562). This release is available from mid-March 2011 to all customers with a support contract, and can be downloaded from the Adlib web site.

You can simply install this software on top of your existing Adlib system (for versions 4.4 and higher). So you do not need to uninstall anything, but please make a backup of your databases and applications first.

From Adlib 5.0 a new licence file is used: adlib.lic. If you are already using 5.0 or higher, you can use this upgrade immediately after installing; your licence file has already been renewed, is in the right place and will not be overwritten by the upgrade. When you install this upgrade over an Adlib version that is older than 5.0, then the following applies: if you receive this release on CD, then on it you’ll find the proper licence file; if you downloaded this release, then e-mail our helpdesk (helpdesk@uk.) for the necessary password and your licence file. Place this file (you can make copies of it) after installation of the upgrade in your Adlib \bin and \tools or \executables folders (if present). The point is that the licence file should be located in the same folders as your Adlib .exe files. How these folders are named is not important.

The release notes of previous major releases and service releases can be found on the Adlib web site.

1 Security warning

A requirement for using Adlib software on a Microsoft operating system older than Windows XP (Windows 2000), is that the Microsoft component gdiplus.dll is present in your folder containing the Adlib executables. For Windows XP or higher, this file can be removed.

In this gdiplus.dll software component, Microsoft has found a security leak that may introduce a virus to your system by means of specially prepared JPG images. To prevent that, all gdiplus.dll files on your system need to be replaced by its latest version.

On the Windows side you can do this by activating Windows Update, and installing the latest Microsoft service packs and hot fixes. If you also use MS Office, you’ll also have to update that through Microsoft’s Office Update.

On the Adlib side you can fix the potential problem by installing release 6.0.0 or higher; gdiplus.dll will then be replaced automatically.

Instead, you may also replace all occurrences of gdiplus.dll (versions 5.1.3097.0 and 5.1.3101.0) manually, by a newer version.

This dll can normally be found in your Adlib \bin folder(s) and the folder in which wwwopac resides (if you use Adlib Internet Server), and in certain Windows folders. Through the Windows Explorer you can search your system for all places where this file occurs.

You can look up the version of an occurring gdiplus file through the properties of the file: right-click the file and choose Properties in the pop-up menu. The version can be found on the Version tab.

Note that Microsoft’s Update function may install a GDI+ detection tool, which tells you whether you need to update this file. But the test that this tool performs is not complete and doesn’t check your whole system. It is possible for you to get a message that your system still needs an update, when you have already installed it. So check which versions are present on your system yourself, and execute any required updates and/or replacements manually.

2 Improvements

In 6.5.2 SP3 the following functionality has been improved:

1 Searching

1. Right truncated searching did not work in combination with left truncated searching. When left truncation had been made possible for an Adlib Oracle database, and you searched right plus left truncated via the expert search language (by using an asterisk on both ends of the search key), then the right truncation was ignored during the search: only left truncation appeared to work. (Ref.no: 4195)

2. Searching via an ISO date access point didn’t find any records. When you searched an ISO date access point, like Production date (early) in a 4.2 application, no records were found, while an equivalent search in the Expert search system did yield results. (Ref.no: 4289)

3. When a search on an ISODate found multiple dates, the All keys button only returned the records for the first date. When you used the Search wizard to search an ISODate index on a date range, and this search yielded multiple keys (dates), then pressing the All keys button only returned records for the first date. (Ref.no: 4949)

4. Incorrect warning for circle definition with two identical, hierarchically linked terms from different domains. When a term appears twice in a Thesaurus, but in different domains, then in priciple one term can be the broader or narrower term of the other term. This way you can define a hierarchical relation between for example a city with the same name as the province. However, when you searched hierarchically on such a term via an access point to an Adlib Oracle database, then in the list of found terms a warning symbol appeared in front of the term, as if to indicate a circle definition. But this warning was incorrect. (Ref.no: 4505)

2 Editing

5. The linked terms list was sorted incorrectly and the focus was not on the validated term. When you typed an existing term in a validated field in an Adlib SQL database and pressed Shift+F4 to open the Find data for the field… dialog, then the retrieved terms list in that window was not sorted alphabetically and the term you were looking for was not selected. (Ref.no: 4749)

6. Redundant new source title occurrences were created when adding a source title. In the Articles dataset, when you added an existing source title to a record, a new field group occurrence of the source title fields was created automatically after the merged-in Material type field content was retrieved from the linked record. (Ref.no: 4788)

7. On the Documentation tab, the contents of author fields sometimes moved up. When multiple field group occurrences were present on the Documentation tab in an object record, of which the first occurrence did have a title but no author, and from the first title occurrence you clicked the Make/edit linked record button only to close the zoom screen directly without saving, then all authors had moved one occurrence up and were now located next to the wrong titles. On closing of the record, with or without saving, the authors did land in the proper occurrences again. The same problem could occur with article information, pertaining to the Volume, Year and Pages fields. (Ref.no: 3567)

8. Linking more than one new image didn’t create all reproduction records. When you added multiple images as new reproductions to an object record, only of the first added image a reproduction record was created in the linked PHOTO database. Dead links for the remaining, but non-existing reproduction records, were still added to the object record. (Ref.no: 4941)

9. Deleting an image from a copied record also deleted the object number. When you copied an object record, changed the object number by adding characters behind the already existing value, and subsequently used the Delete occurrence button in the Media Viewer to delete the reference to an image, then this would also delete the new object number. (Ref.no: 4429)

10. The creation date of a copied record in the Record information window showed the date of the original record. When you copied a record, changed some data in it, saved it and checked the stored contents in the Record information window (Ctrl+R), then the Creation date in the header box of this window still displayed the creation date of the original record, instead of the creation date of this new record. (Ref.no: 4784)

11. The layout of the Find data for the field… window was corrupted if the Used thesaurus list was present. When for a linked field an external thesaurus had been set up, and you opened the Find data for the field… window for this linked field (Shift+F4) to validate a term, the presence of the Used thesaurus drop-down list interfered with the display of the Show data for all domains option. (Ref.no: 4854)

12. The creation time in the Record information window increased with one hour. Every time you edited and saved a record in an Adlib SQL Server or Adlib Oracle database, the original creation time as displayed in the Record information window (Ctrl+R) increased with one hour, while in the record itself the original input time remained the same. (Ref.no: 4779)

13. Error 7 when forcing new term in linked field. When leaving a linked field containing a value which did not exist in the linked database yet, a message stating This term does not exist opened, as usual. After closing the message however, a new message opened, reporting an error 7 for creating a field. After closing this message, forcing the new term itself worked fine. (Ref.no: 4896)

14. Searching with a WHEN operator in the Expert search system produced an error 189. When you performed a search in the Expert search system involving the WHEN operator and an ISO date field, an error message appeared stating that the multipart identifier for the relevant field could not be bound. (Ref.no: 4978)

15. The repsort function did not include all fields from the field group in the sorting. When you added a new occurrence to a field group, below other existing occurrences, while an adapl program would sort these occurrences using the repsort function, then not all fields were actually sorted. (Ref.no: 4992)

16. Sometimes it was possible to remove a read-only field occurrence. If a field had been set to read-only in its screen field properties while the field was part of a data dictionary field group (and the other screen fields of that group hadn’t been set to read-only), then a user could remove occurrences of that read-only field anyway by placing the cursor in one of the other fields in the group and remove the field group occurrence there. (Ref.no: 4880)

17. After using the double down arrow button in the link screen, it wasn’t possible to scroll back up. When you entered a new record in a multilingual Adlib SQL database, and you typed something random in a validated field, left the field and in the Find data for the field… window you clicked the long double down arrow button beneath the list of terms once or twice, then you couldn’t scroll back up again because the double up arrow button was now inactive. (Ref.no: 5003)

3 ADAPL

18. Clearing a linked field via a storage adapl left the link reference intact, and therefore did not really empty the field. When you entered a value in a linked field and saved the record while a storage adapl empied the relevant linked field, then the link reference of that linked field was not emptied, so that after storage the linked field was still filled. (Ref.no: 4943)

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download