7.0 SR1 Release notes

Adlib Information SystemsCopyright © 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 ap-pear in this document. The software described in this document is fur-nished 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 im-proved. 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 sup-ply software, or as a definitive product description.

Contents

Introduction..........................................................................1

1 New functionality...............................................................31.1 The Change locations procedure simplified.................................3

2 Improvements..................................................................112.1 Display.......................................................................................112.2 Searching...................................................................................112.3 Editing........................................................................................122.4 Deriving......................................................................................142.5 Pointer files................................................................................142.6 SDI..............................................................................................142.7 Closing Adlib..............................................................................152.8 Printing.......................................................................................152.9 Exporting....................................................................................16

IntroductionThese release notes describe a number of improvements in the Adlib executables, which are implemented in Adlib 7.0.0 SR1. This release is available from the end of December 2012 to all customers with a sup-port contract, and can be downloaded from the Adlib website.

You can simply install this software on top of your existing Adlib sys-tem (for versions 4.4 and higher). So you do not need to uninstall any-thing, 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 in-stalling; 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 (helpdesk@uk.adlibsoft.com) for the necessary password and your license file. Place this file (you can make copies of it) after install-ation 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 warningNew functionality in Adlib 6.6 for SQL Server and Oracle databases makes records that you change with this version or later versions inac-cessible to older versions of Adlib (adlwin.exe as well as wwwo-pac.exe). Please, keep this in mind if you would first like to try Adlib 7.0 before making the definitive upgrade. This limitation does not ap-ply to CBF databases.This means that you have to update wwwopac.exe to 7.0 too. This may have consequences for your web application though because of some changes in the structured XML-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 func-tionality 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.

1 20-2-2013

1 New functionality

1.1 The Change locations procedure simplifiedOn the Location | Future movements screen tab in the object cata-logues of 4.2 model applications and higher, you can register the nor-mal location, the current location and any planned future movements.

Figure 1.1: A screenshot from a 4.2 application: other application versions may show different screens and fields.

The Change locations procedure allows you to simultaneously change the current location of one or more marked records in the Brief dis-play, when you are actually moving objects. You can start this function from within the Edit menu: click the Change locations option.

The Change object locations window opens. The Change object locations windowIn the first section in this window you can enter the new current loca-tion (for alle marked objects), the movement date and time (which doesn’t need to be today), a remark about the suitability of the new lo-cation, the name of the authoriser for the new location and any notes about the new location.In the second section you register any details about the movement, like the movement method, its reference number, a contact person and possibly some notes about the movement.

3 20-2-2013

Only the Location field is mandatory for this procedure, the rest is op-tional.The Progress box displays a summary of the progress of the running procedure. Any errors will be listed here too.

Figure 1.2: The Change object locations window as presented in 4.2 model ap-plications and higher.

The List buttons behind the Location, Authoriser, Method and Contact fields allow you to select an existing term or name. Actually, these are validated fields and you can only enter an existing term or name here, with or without the help of the List function.

4 20-2-2013

Figure 1.3: The Change object locations window as presented in 3.4 model ap-plications and older: you can’t enter movement details here.

As soon as you type a term or name in such a field and leave it, the value will be validated. If the value doesn’t exist, you’ll be notified so and you will still have to choose an already existing term or name. Be-fore, during or after entering a value, you can click the List button be-hind the field to open the Find data for the field… window, in which you can validate the value yourself before Adlib does.In the first entry field underneath Find, you must select a field from the linked record in which you would like to search for a value (one or more fields are available*); if only one field is available, it will be se-lected by default. In the next entry field you must enter a partial or complete value to search on (you cannot leave the entry field empty). Then press Enter or click the Search button to retrieve all values from the relevant index, that start with the search key. Subsequently select one of the found keys and click Select to copy the value to the Change object locations window.

5 20-2-2013

New functionality Adlib 7.0

* Which fields are available in the drop-down list underneath Find, is determined by the link definition of the current linked field. Only the linked field itself and any merged-in fields which have been indexed in the linked database, will appear in the list. Moreover, the list displays the field names as they have been specified in the linked database, and those might be slightly different from the labels presented in the user interface.In fields in the linked database that are represented by a drop-down list, you can only search on the interface language neutral values of the list: in package_location for example (the possibly merged-in field with the linked field location in custom applications, in which you have registered whether the record pertains to a location or a package) you can choose from exactly two values to search on: package and loca-tion. What the procedure doesAs soon as you click the Apply button, the procedure starts processing all marked records one by one. From Adlib 7.0 this involves the follow-ing:1. If the processed record already contains a current location, all its

details will be transferred to the location history. The date entered in the procedure will become the End date (Removel date) of the previous location just created. In 4.2 applications and higher, the history can be found on the separate Location history tab, while in older applications the history is summed up underneath the cur-rent location. Any movement details, as entered in the 4.2 Change object locations window, will also be added to the previous loca-tion just created.

20-2-2013 6

Adlib 7.0 New functionality

2. The details of the new location you entered in the Change object locations window, will be copied to the record fields for the Current location.

Note that any registered, planned Future movements will be ignored by this procedure from now on, so they won’t have any effect on what you’re doing. Any future movement data won’t be used or checked or deleted. This behaviour is now in line with that of the Adlib Movement module, which ignores future movements as well. It is possible that a next version of Adlib will contain a separate method to process any registered future movements or to purge them.The Normal location will be kept intact, of course.The procedure can be aborted during its progress, using the Cancel button. The procedure will finish its work on the currently processed record and will then stop. So the changes in already processed records won’t be made undone: the procedure will only be aborted and the progress report will tell you which records have been processed up un-til then.Further note that the procedure will process the marked records in record number sequence, which is not per se the order in which the marked records are listed in the Brief display.Records which couldn’t be edited by the procedure, for instance be-cause those records were just being edited by colleagues, can be saved in a pointer file afterwards so that you can check what was go-ing on and/or try to execute the procedure on those records again at a later time.

Technical details

The Change locations procedure uses hard coded tags. If you want to customize an application, it might be handy to have an overview of the relevant tags.To start with, Adlib distinguishes between 4.2 model applications and older model applications. This distinction is made on the basis of tag 2A (current_location) in the database collect. If the tag is present, the software assumes that it concerns application version 4.2 or higher. So, this tag in that database should not have a different pur-pose, in whatever application, if you want to be able to use the proce-dure described here.

For application version 4.2 and higher, the following applies:

7 20-2-2013

New functionality Adlib 7.0

Field in Change object loca-tions window

Tags to be filled in database collect

Location 2A (Current location)Date/Time 2C/2G, the start date and time of

the new current location (and SE/Sh, the end date and time of the now previous location, if present)

Suitability 2E

Authoriser 2F

Notes 2D

Method mT (Movement methode)Reference mR

Contact mC

Notes mN

2R (current executor)

When the details of the current location are automatically transferred to a new first field group occurrence of the location history (which of course happens before the procedure enters a new current location), the following tag mapping is used in 4.2. Current location fields Location history fields2A (Current location) ST

2C/2G (Date/Time) SS/SH

2E (Suitability) S3

2F (Authoriser) SP

2D (Notes) LM

2R (current executor) 2V (executor history)

In the 4.2 model application, 2R and 2V have not been defined in the database structure yet and are not visible on the screen (they will be in a future model application), but they will still be stored in the record. In principle that is not problem. If you want, you can define 2R and 2V as text fields with a length of maximally 100 characters in the collect database (2R not repeatable, 2V repeatable) and place them 20-2-2013 8

Adlib 7.0 New functionality

each on their applicable location screen, right above the Authoriser field for example, to make this data visible. for application version 3.4 and older applies:Field in Change object loca-tions window

Tags to be filled in database collect

Location ST Location type LT

Date SS, the start date of the new cur-rent location (and SE(2), the end date of the now previous loca-tion, if present)

Notes LM

Before the procedure enters a new current location, a new, empty first occurrence of the field group for the location details is created. This means that the data from the old first occurrence simply moves down to the second occurrence, which makes the old current location the new previous location. The relevant tags in 3.4 are the following:Current location fields Location history fieldsST(1) (Location) ST(2)

LT(1) (Location type) LT(2)

SS(1) (Start date) SS(2)

LM(1) (Notes) LM(2)

S3(1) (Suitability) S3(2)

9 20-2-2013

2 ImprovementsIn 7.0 SR1 the following functionality has been improved:

2.1 Display1. Clicking a link reference value on screen didn't open a

zoom screen. When you have a screen on which the link refer-ence of a linked field is being displayed (meaning the record num-ber of the linked record), then clicking that underlined link refer-ence wouldn’t open a zoom screen to the linked record (whereas clicking the value in the linked field itself would). (Ref.no: 5534)

2. Changing the data language while in the Expert search window, was not reflected in the status bar. After changing the data language while the Expert search window was being dis-played, the data language noted in the status bar hadn’t changed, so you didn't know what your current data language really was. (Ref.no: 5503)

2.2 Searching3. Field names with a hyphen in them were not always han-

dled correctly by the expert search language. Since hyphens appearing anywhere in a search statement are now treated as “AND NOT”, you must enclose typed field names containing a hy-phen (a minus sign), by double quotes. However when you picked such a field name from the list in the Expert search window, Adlib did not put double quotes around it automatically, as it should have, to prevent an erroneous syntax. With this fix, whenever you pick a field name containing a hyphen from the list in the Expert search window, Adlib puts double quotes around it automatically. (Ref.no: 5510)

4. Searching with the WHEN or WHEN NOT operator didn't yield correct results. When you searched on <field>=* com-bined with either WHEN or WHEN NOT, the result could also contain records in which the relevant field was empty. It was also possible that records complying to the search conditions were missing from the search result. (Ref.no: 4345, 5610)

5. A QBF containing the tag TO generated a syntax error. When you had added the tag TO to a Query by form, then on open-ing this QBF in Adlib a syntax error was generated. (Ref.no: 5661)

11 20-2-2013

2.3 Editing6. .5 wasn’t recognized as a decimal value anymore. When you

typed .5 (without a zero in front of it) in a numerical field, it wasn’t recognized and the dot was removed, so just 5 remained. (Ref.no: 5512)

7. A user with write access rights could not edit a record opened by skipping the Brief display. When you were as-signed a role which had write access rights to the current data-base, and when searching in Adlib you picked a single found key from the last step in the Search wizard to open a record in detailed display directly (and thus skipping the Brief display), you couldn’t edit the record. You could only edit the record if you had opened it from within the Brief display. (Ref.no: 5518)

8. The Records featuring keyword function wasn’t working correctly in SQL. When you used the Records featuring keyword function (in the Find data for the field window) for a name that ap-peared twice in the linked database, records featuring either one of both identical names were returned instead of only the records linking to the selected name record. (Ref.no: 5668)

9. Preferred name substitution didn’t work if a non-preferred name was entered while its preferred name was not in the domain associated with the field. When you entered an exist-ing, non-preferred author name (already associated with the au-thor domain) in the Author field in a record, while its preferred name was associated with a different domain, and you moved the cursor to another field, then firstly the inappropriate message “Do you want to add <non-preferred name> to domain author?” ap-peared, and secondly, when you clicked Yes, the record was saved but no preferred name substitution had taken place and the non-preferred name was saved in the record. (Ref.no: 5685)

10. When moving occurrences with Ctrl+, occurrences some-times moved up only partially. When you moved a field group occurrence two lines up using Ctrl+, not all occurrences were al-ways moved: the last field in a row could stay behind in the previ-ous occurrence, especially if that field contained long text. (Ref.no: 5656)

11. In the People and Thesaurus databases, used-for names and terms were sometimes irreversibly converted to lower case. When you edited a Persons and institutions or Thesaurus record with an already registered used-for name with upper case letters in it, and you put the cursor in that field and then in an-other, the name instantly changed to all lower case. Once you saved the record that way, it couldn’t be changed back, even though the linked record still had the correct capitalisation. This

12 20-2-2013

Adlib 7.0 New functionality

problem occurred in older applications in which the internal links were linked on value, not on link reference. (Ref.no: 5543)

12. Unwanted term substitution when adding a parent term (Taxonomy) in a zoom screen. When adding a parent term to a new record created in a zoom screen, the new term was replaced by the parent term of the parent term being entered. (Bug.no: 5496)

13. A forced term was not added to a new occurrence of a re-peatable linked field with occurrence sorting enabled. When you added an occurrence to a repeatable linked field for which oc-currence sorting had been enabled, entered a new term and forced it into the linked database, then after saving the main record, the occurrence with the newly forced term was not there anymore. The term had not been forced into the linked database. (Ref.no: 5592)

14. When opening a zoom screen to the Thesaurus from within a People zoomscreen, the zoom screen opened in the Peo-ple database instead of the Thesaurus. When you opened an object record in edit mode, entered a new creator name and in the Find data for the field window you chose the Create a new people record option, a zoom screen to enter more details for the new creator opened correctly. If you then entered a new place in that zoom screen and pressed Tab to validate the input, then in the Find data for the field window still the People database was se-lected instead of the Thesaurus (in which place names are stored). This could result in the place being saved in the wrong domain while the creator was not saved. A crash could also occur. (Ref.no: 5648)

15. The cursor disappeared after selecting a favourite from a field's context menu, when you opened it with the menu key present on some keyboards. When the cursor was in a field in edit mode and you pressed the menu key to the left of the right Ctrl key on some keyboards to open the pop-up menu for the relevant field, and you selected a term from the favourites list (again by using the keyboard), the favourite term was added to the field but the cursor was gone. This meant that you first had to use the mouse and click in a field to get the cursor back before you could continue working with the keyboard. (Ref.no: 5689)

13 20-2-2013

New functionality Adlib 7.0

16. Records in a SQL database couldn’t be locked when the user name contained an apostrophe. When you logged on to Adlib (SQL) with a user name containing an apostrophe, then you were able to find records but you couldn’t edit them. The apostro-phe in the name made it impossible for Adlib to lock the record: a syntax error would be generated. (Ref.no: 5132)

2.4 Deriving17. It wasn’t possible to cut a record if you didn’t have delete

rights on the source record. When deriving a record from one dataset to another in the same database while the source record must automatically be deleted when you save the derived record, you needed full access rights to the source dataset. If you only had write or less access rights, Adlib could report an error when you tried to save the derived record, about a duplicate object number (or other unique field), because the source record couldn’t be re-moved. The fix makes sure the source record is removed automat-ically after saving the derived record. (Ref.no: 5599)

2.5 Pointer files18. Modifying SDI profile properties would profile the pointer

file. When you changed the properties of an SDI profile, like when adding an e-mail address, and you saved the changes, then the SDI pointer file would be updated automatically. This could mean that e-mails would be sent as if a scheduled SDI profile had been executed. (Ref.no: 5694)

2.6 SDI19. SDI crashed with a C++ exception error 357. Even though

most of multiple scheduled SDI profiles would be executed, SDI could crash at some point with a C++ exception error 357, a mem-ory-usage problem. (Ref.no: 5663)

20. The SDI subject couldn’t handle diacritics. When you had used diacritical characters in the text in the Subject field of the properties of an SDI profile, these characters were displayed incor-rectly in sent e-mails. (Ref.no: 5509)

20-2-2013 14

Adlib 7.0 New functionality

2.7 Closing Adlib21. Users who weren’t allowed to close Adlib, could still close

the Search wizard. When in Designer the Allow the user to shut Adlib option had been switched off, you would still be able to close the Search wizard by means of the cross in the upper right corner of the Search wizard window. This would leave an empty Adlib main window in which you couldn’t continue working. (Ref.no: 5098)

22. Sometimes an Adlib application couldn’t be closed because the confimation message was hidden behind the Search wizard. If you opened an Adlib application and almost immedi-ately clicked the white-red cross in the upper right corner, before the Search wizard was displayed, then the message asking you to confirm the closing of the application was hidden behind the Search wizard, making it seemingly impossible to really close the application. (Ref.no: 5386)

2.8 Printing23. Word printing sometimes closed unexpectedly without cre-

ating a Word document. When you printed to a Word template as a predefined output format, the Word window would open, the Adlib Word interface progress bar would start running, but could suddenly stop and the Word windows would be closed immedi-ately. (Ref.no: 5691)

24. The Print wizard generated an error after finishing when there was an apostrophe in the header text. When you inter-actively put together a report with the Print wizard and in the header text you entered an apostrophe with at least one other character behind it, then on finishing the wizard (when in the back-ground a print adapl is being generated) it notified you of an error at line 117/118 during compilation. (Ref.no: 5193)

25. Adlib froze when cancelling the file name assignment when saving print output to file. When you printed a record by means of an predefined output format and in the Print window you marked the Print to file checkbox and clicked OK, then when you clicked Cancel in the Select an output file window, Adlib froze. (Re-f.no: 5513)

2.9 Exporting26. Protected fields could still be exported. The contents of a

field to which a user had None access rights, could still be ex-15 20-2-2013

New functionality Adlib 7.0

ported. This was a problem when such access rights had been set to hide a field and its contents completely from certain users (be-cause of confidential data for example). By exporting the field or the entire record, those users could still view the data in the re-sulting exchange file. (Ref.no: 5325)

20-2-2013 16