7.0.0 SP2 Release notes

Adlib Information Systems

Copyright © 2013 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.

9-9-2013

Contents

Introduction

1 Improvements

1.1 Display

1.2 Searching

1.3 Editing

1.4 Printing

1.5 Deriving

1.6 Importing and exporting

9-9-2013

Adlib 7.0.0 SP2Improvements

Introduction

These release notes describe a number of improvements in the Adlib executables, which are implemented in Adlib 7.0.0 service pack 2 (build 554). This release is available fromSeptember2013 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 Adlibsystem (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 license file is used: adlib.lic. If you are already using 5.0 or higher, you can use this upgrade immediately after installing; your license 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 license file; if you downloaded this release, then e-mail our helpdesk () for the necessary password and your license 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 license 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 website.

Backwards compatibility warning

New functionality in Adlib 6.6 for SQL Server and Oracle databases makes records that you change with this version or later versions inaccessible to older versions of Adlib (adlwin.exe as well as wwwopac.exe). Please, keep this in mind if you would first like to try Adlib 7.0.0 SP2 before making the definitive upgrade. This limitation does not apply to CBF databases.

This means that you have to update wwwopac.exe to 7.0.0 SP2too. This may have consequences for your web application though because of some changes in the structuredXML-format: previously, empty fields from field groups did not appear in the record XML, while from 6.6 they do.

You also need the latest version of Adlib Designer to implement functionality described in these release notes. However, when you modify your application in the new version of Designer, you won’t be able to edit that application anymore, of parts thereof, in older versions of Adlib Designer.

19-9-2013

Adlib 7.0.0 SP2Improvements

1Improvements

In 7.0.0 SP2 the following functionality has been improved:

1.1Display

  1. The Hierarchy browser remained empty if there was a broader term occurrence without a broader term reference. When for a displayed record the Hierarchy browser opened, it started with identifying the top broader record for the current record. However, when the current record (or a broader) contained a broader term occurrence, yet with an empty linkreference, Adlib still concluded there was a broader record, but since it couldn’t find that broader record, the display of the record hierarchy would freeze. (Ref.no: 5867)
  2. Temporary image files were not removed. When URLs are being used to refer to images, for each image that is displayed a temporary file is created in the %temp% folder of the Adlib user. However, these files were not automatically deleted when closing Adlib, which could cause the %temp% folder to grow larger with every retrieved image. (Ref.no: 4849)

1.2Searching

  1. Step 4 in the Search wizard didn’t support multiple identical records. When there exist multiple records for one and the same term in an authority database like the Thesaurus, the Search wizard result window (step 4) would only display the properties (hierarchy etc.) for the first record it found for the relevant term. So if in the first record the term doesn't have a hierarchy, while in the second record the term does have a hierarchy, no hierarchy was displayed for the term. (Ref.no: 5826)
  2. In front of found terms in step 4 of the Search wizard sometimes warning signs were displayed without proper reason. When searching on term in the Thesaurus, and various terms appeared in the list of found terms in step 4 of the Search wizard, then sometimes they had warning signs in front of them although all of these records were accessible and didn’t contain circular references. (Ref.no: 5832)
  3. A search on a free text index which resulted in "no records found" would take very long and prevented other users from saving records. When you used the Search wizard to search on long-text fields like Title, the search would take very long (several minutes) if no records could be found. When during this search another user tried to save a new record, the saving process would not complete until the search process from the other user had finished. (Ref.no: 6014)
  4. Searching with an empty QBF made Adlib crash. When you create a new object record and on the Documentation tab you double-click the Title field, a Query by form opens. If you left the QBF empty and still clicked the Search button in the menu, a message appeared asking you to enter criteria for the search (as expected), but then Adlib crashed. (Ref.no: 6023)

1.3Editing

  1. A single-character non-preferred term wasn’t always replaced. When you entered a non-preferred term consisting of a single letter in a linked field, then it wasn’t replaced by the preferred term if you left the field using Ctrl+Enter. (Ref.no: 5811)
  2. The More than one preferred term found … window displayed incorrect data. When you entered a non-unique term in a validated field and left the field, the More than one preferred term found … window opened to let you choose the correct term from a list, but the window displayed data from the parent record (if present) instead of the record itself. (Ref.no: 5775)
  3. It was impossible to add multiple occurrences of a field when the occurrence sort order had been set. When you tried to add an object to an outgoing loans record to which at least one object had already been linked, for example, while the sorting order of the tag IN had been set to Ascending, the new occurrence was not inserted properly. When a new occurrence was added, the contents of the field group was not moved entirely, resulting in an error 351: Link reference tag not filled. (Ref.no: 5738)
  4. Tooltips in the More than one preferred term found window sometimes showed the wrong hierarchy. If in the More than one preferred term found window identical terms are presented, as can be the case for location names for example, you typically hover the mouse pointer over the term to display a tooltip containing the higher level term hierarchy of the term which you need to decide which preferred term to pick. However, the tooltip for the last preferred term in the list didn’t show the correct higher level hierarchy. (Ref.no: 5866)

  1. When selecting a location in the Change location procedure, the full hierarchy could not be viewed. When you had opened the Change location procedure and via the list button you searched for a location that wasn’t unique, then you found that although the broader location was shown in the Is part of column, you could not view the entire hierarchy. This meant that if the combination of the searched location and its broader location happened to be non-unique as well, you couldn’t select the proper location.
    The fix consists of a new Context column in the list screen, showing the entire upwards hierarchy of a location. (Ref.no: 5958)
  1. Linking images through drag-and-drop didn’t always work well. When dragging more than two images individually or together from Windows Explorer into the Adlib Media Viewer, only two Visual documentation records were created and linked to the object record. (Ref.no: 5910, 5911)
  2. Adlib crashed after adding an occurrence linked to a collect record without an image. When you added an occurrence to a linked object number field (linking to the collect database) and you entered an existing object number of an object record without an image, after which you left the field via Tab and subsequently clicked the Save button, then Adlib became non-responsive and after some time produced a serious error message. (Ref.no: 6000)

1.4Printing

  1. Printing to e-mail gave error 332. When you printed a selection of records using a predefined output format, and chose to e-mail the result (from within the Print window) instead of printing to the printer, an error 332 occurred. (Ref.no: 5823)

1.5Deriving

  1. No records could be found when trying to derive from the German National Bibliography, LOC or National Library of the Netherlands. With any query, the result of trying to derive a book record from the German National Bibliography, the Library of Congress or the National Library of the Netherlands was always: No matching record available. (Ref.no: 5957)
  2. After previewing a record to derive, the record details were not copied to the target record. When you had opened a new record, subsequently searched for a record to derive from the Gemeinsamer Verbundscatalog and clicked the Details button for one of the found records to preview it in a zoom screen, then after closing the zoom screen and selecting the same title to copy its details to the target record, the local record would remain empty. (Ref.no: 6004)

1.6Importing and exporting

  1. A runtime error occurred when choosing the Import function while the interface language was Arabic. When you had set the Adlib interface language to Arabic, selected a database to work in and then chose FileImport, Adlib would generate a common runtime error: an invalid parameter was passed to a common runtime function. (Ref.no: 6110)

19-9-2013