Release notes 6.5.2



6.5.2 release notes

Adlib Information Systems

Copyright © 2010 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 New functionality 3

1.1 Button and menu for editing multilingual field 3

1.2 Alt+Enter to view the field properties 3

1.3 Quickly sorting the brief display 4

1.4 Improved status bar readability 5

1.5 Hide invariant data 5

1.6 Find data for the field… window improved 7

1.7 New option to show all messages again 8

1.8 Alphanumerical sorting 9

1.8.1 Sorting the Brief display 9

1.8.2 Sorting via the Expert search system 10

1.9 SDI storage parameter SDIMAILFORMAT 11

1.10 Access to record buffers extended 11

2 Other improvements 13

2.1 Display 13

2.2 Searching 15

2.3 Editing 17

2.4 Saving 21

2.5 Printing 23

2.6 Adloan 24

2.7 Serials 24

2.8 Importing 24

2.9 WWWOPAC 24

Introduction

These release notes describe a number of improvements in the Adlib executables, which are implemented in Adlib 6.5.2. This release is available from the beginning of April 2010 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 New functionality

1 Button and menu for editing multilingual field

The different translations for a multilingual field can be entered in a separate dialog window which previously could be opened by right-clicking a multilingual field in edit mode, and choosing Edit multilingual texts. From 6.5.2, an Edit multilingual texts button, a menu option with that name in the Edit menu, and the key combination Ctrl+M have been added to open the same dialog. All these options are only active if the cursor is located in a multilingual field.

[pic]

2 Alt+Enter to view the field properties

To view the technical properties of a field, you can right-click the relevant entry field in the detailed display of a record, and choose the Properties option in the pop-up menu which opens.

From 6.5.2, the properties of the field which holds the cursor can be opened as well via the key combination Alt+Enter.

[pic]

3 Quickly sorting the brief display

[pic]

A search result listed in the brief display, can always be sorted very specifically, via the Sort button:

[pic]

In 6.5.2, a faster and simpler method has been implemented as well:

1. Right-click a random spot in the brief display to open a pop-up menu (see the screenshot above).

2. Move the mouse cursor to the Fields option in that pop-up menu, and a second pop-up menu opens, containing all fields which can be used for sorting. It is possible to see all the fields at once, or only one column which can be scrolled using the black arrows at the top and bottom of the list.

3. Click the field on which you wish to sort and the brief display will be sorted alphabetically straight away.

Each time you sort the brief display to a field this way, the selected field will be stored in the first pop-up menu, so that you won’t have to select that field from the complete fields list next time. In the figure below, you can see the first and second pop-up menu next to each other. The first pop-up menu shows that the brief display has already been sorted once on title and on creator. Click such a saved sort field to immediately sort the brief display on this field.

This way, Adlib remembers the last ten chosen fields per database per user. (This information is saved in the Windows registry.)

4 Improved status bar readability

In 6.5.2, the five sections of the status bar at the bottom of the screen in your Adlib application will improve how they resize to accommodate various screen widths. The first two sections from the left now have a fixed length, while the other three sections will scale along with the screen or window width. This minimizes the amount of text truncation in the status bar at reduced width, whilst keeping as much information visible as possible.

5 Hide invariant data

In Adlib SQL Server and Adlib Oracle databases, it is possible that fields have been made multilingual. In such a field you can enter multiple translations of a value. You switch between entry languages via the Data language menu.

The data language which you use first to enter data into a multilingual field in a record, is termed the invariant language for this field in this record. If you’ve entered a value in only one language, in a multilingual field of a record, and you then save the record, then that value will also appear only once in the stored record, in the relevant language. However, as soon as you switch data language, you’ll see that the invariant value of the multilingual field is displayed anyway (although still not stored in the record). The reasoning is that if Adlib cannot find a field value in the current data language, then it should display the value in the invariant language instead: a compromise of course, since it is the right value, but the wrong language.

The new Hide invariant data setting, in the Options menu, allows you, in either display or edit mode, to decide not to show invariant data when you switch to a data language which is not the invariant language. A green check appears in front of the Hide invariant data option, if the function has been switched on. Click the option again to display invariant data in other languages again.

[pic]

1 Example

Suppose you have an Adlib SQL database in which the object name field has been made multilingual. The languages in which you can enter data are e.g. Dutch, English and German. In a new record you enter the object name “spoon” in the English data language, and after filling in some other fields , you save the record. “Spoon” has now become the invariant value; the field has not received a value in the other two languages. With the record in display mode, you switch to Dutch via the Data language menu. Nothing changes in the displayed record, since the one multilingual field has no Dutch value, and therefore Adlib will show the invariant value: the English word “spoon”, even if that value has not been stored in the Dutch data language. If you don’t want this to happen, you open the Options menu and choose the Hide invariant data option in it. The word “spoon” will no longer be visible in the object name field in this record, as long as you are working in the Dutch or German data language.

The new option is always available, not just in the detailed display of a record.

The current status of the Hide invariant data setting will be stored per user in the Windows registry. This means that you’ll only have to switch the option on once; the next time you start Adlib, the setting will be applied automatically (until you switch it off again in the Options menu of course).

6 Find data for the field… window improved

The Find data for the field… window appears when you leave a linked field, after entering a non-existing term or name. It also appears if you press Shift+F4 when the cursor is active in a linked field.

Due to problems with the scrollbars in older versions of this window, the appearance of the three tabs and their scrollbars has been improved.

[pic]

The vertical scrollbar on the right of the list allows you to scroll within the present part of the complete list. (The present part of the complete list always consists of a limited number of keys.) The little arrow buttons on top and at the bottom of this scrollbar allow you to do the same, but without dragging the scrollbar.

To view any preceding part of the list, click the list-wide button with the double arrow on top of the list. To view any following part of the list, click the list-wide button with the double arrow at the bottom of the list.

Instead of clicking a double-arrow button repeatedly to view other parts of the list, you may also enter one or more letters in the Find box to have the list immediately jump to keys starting with those letters.

7 New option to show all messages again

If you enter a term or name in a linked field, which does not exist in the linked database yet, a message pops up notifying you so. By marking the option at the bottom of this message, you won’t see this message again, and the Find data for the field… window will immediately be accessible in this situation.

Similar messages in Adlib can be hidden in the same way.

[pic]

However, switching the messages back on previously had to be done in the Windows registry. To make this functionality more user-friendly, a new option has been added to the Options menu in Adlib to switch back on again the displaying of all messages: Show all messages.

[pic]

8 Alphanumerical sorting

New in 6.5.2 is the possibility to have the brief display of a search result sorted alphanumerically. Alphanumerical sorting is intended for sorting on fields which contain values consisting of both letters and digits, while you wish to consider subsequent digits to be one number.

Suppose you use object numbers (a text field) built up from letters and numbers. See the fictious numbers below to clarify the difference between sorting on text and alphanumerical sorting. (Note that numerical sorting (not alphanumerical) on a text field yields unpredictable results: only numerical fields can be sorted numerically correctly.)

|Text |Alphanumeric |

|00101A |7A |

|100A |20A |

|20A |100A |

|7A |00101A |

|A20A |A7A |

|A7A |A20A |

|C01 |C01 |

When sorting on text, the field values are compared character by character: 20A then comes before 7A because 2 comes before 7 in the character set. When sorting alphanumerically, (0)1, 7, 20, 100 and (00)101 are seen as numbers, putting 7A before 20A, and since in the character set digits come before letters, 00101A comes before A7A.

1 Sorting the Brief display

In the Brief display, a search result can be sorted as you desire.

[pic]

Click the Sort button or choose the Sort option in the Record menu, and set your sort condition in the Sort window: in the list, double-click the (text) field on which you want to sort, and double-click the Text option (beneath Type) to set the sort type to Alpha numeric, for example. Click the Sort button at the bottom of the window to actually sort the search result according to your settings.

[pic]

2 Sorting via the Expert search system

[pic]

Expert search system users can also specify the sorting in the search statement; the Brief display of the search result will be shown in the desired sort order immediately. The part of the search statement meant for sorting, has the following syntax: sort ‘’ . The new sort type is called alphanumeric. An example of a valid search statement is: object_name = * sort 'object_number' alphanumeric.

9 SDI storage parameter SDIMAILFORMAT

For storing an SDI pointer file through sdi.exe or wwwopac.exe, a new parameter called SDIMAILFORMAT, is available from 6.5.2. You can use it to specify the e-mail format (other than the Plain text format which was the default previously), and store this in the pointer file. The syntax is SDIMAILFORMAT=. 1 Meaning HTML, 0 meaning Plain text. Partial example: SDICMD=store&…&SDIMAILFORMAT=1&…

10 Access to record buffers extended

If you retrieve data from a currently opened record in a FACS database, using an adapl, then in the background, ADAPL uses a FACS buffer to store that record temporarily. Until now there were two ways of gaining access to that data via ADAPL, namely by including the tags from that record in a FACS declaration or via tag indirection (see the Designer Help for more information about this).

From 6.5.2, there is a third possibility available, which is much more efficient because the tag does not have to be FACS-declared first nor does it need to be stored as a string in a variable (in the case of tag indirection).

To retrieve the contents of a tag in the new way, you use the record buffer name, in this case the FACS name, followed by an exclamation mark and the tag you wish to address, for example:

display Catalogue!ti

or for instance:

If (len(Catalogue!ti) = 0) { …

In adapls executed during the manual editing of a record, for example before storage or after leaving a field, you’ll have all tags from the record at your disposal by default, without having to include them in a FACS declaration. Those tags are stored in the so-called adlib_lite record buffer. Tags which are also reserved words in ADAPL, like the domain tag do, could previously not simply be called in an adapl. Now you can though, using the new notation, for instance:

errorm adlib_lite!do

Another example for the case in which a FACS database People has been declared:

if (enumval$(People!do, People!do, -1) = 'AUTHOR'){ …

3 Other improvements

In 6.5.2 the following functionality has been improved:

1 Display

1. The selection bar on tabs for thumbnails and filmstrip did not follow the last shown record. When you displayed a record in detailed display from within a record selection on the Filmstrip tab, and browsed through some following records with the F5 key and subsequently returned to the Filmstrip tab, then the first displayed record was still selected, instead of the last shown record. The same applied to the Thumbnails tab. (Ref.no: 2789)

2. Thumbnails invisible after changing the interface language. When you switched between interface languages, while showing the detailed display of a record with linked images visible on the Thumbnails tab of the Media Viewer, then the relevant thumbnail images were hidden. Only when you switched back and forth between tabs in the Media Viewer, all thumbnails became visible again. (Ref.no: 4598)

3. After minimizing and maximizing Adlib, sometimes another record was displayed. When you presented a record in detailed display, and you minimized the Adlib application and then maximized it again, then indeed the same record was displayed again, but if you then put it in edit mode, suddenly a different record could be displayed. (Ref.no: 3451)

4. In a multilingual SQL database, the record sorting in the brief display was not adjusted after the current data language was changed. When you selected another data language for the current brief display of a search result, then the sorting order was not changed, even if that was required by the new data language. The sorting was only changed after reloading the brief display (by going back one step first).

Note that any sorting of a search result from searching on an access point must be specified in the sort options for the relevant method in Adlib Designer (e.g. via a sort adapl or field) and possibly by the Locale database setting which may have been set to a specific language region. If the sort options haven’t been set, no alphabetical sorting will take place. Moreover, searching on a specific language in the Search wizard is not possibly yet – searching is done on all language values - and values from all the available languages can therefore be found and displayed in the search result although the value in the current data language has preference. Further, it is due to the Windows locale that in e.g. Latin language regions, terms in Latin languages will always appear before all terms in e.g. Greek, in the brief display. (Ref.no: 4250)

5. Images with diacritical characters in the name were not displayed on the thumbnails tab of the Brief display. Although images with diacritical characters in the name (like ü) were correctly displayed on all three tabs in the Image Viewer, they were not displayed at all on the Thumbnails tab of the Brief display of a search result. (Ref.no: 4388)

6. Clicking a related object reference caused the display of the screen tab and Media Viewer to interfere. When a Related object was specified for an object (on the Numbers | Relationships tab in a Museum record), and you had pinned down the Media Viewer so that it showed on this particular tab while you clicked the underlined related object reference, then the detailed display of the related object on this tab interfered with the display of the Media Viewer, partially distorting it by overlapping yellow bars. (Ref.no: 4565)

7. Text boxes were wider than Search wizard window (XP). When using Adlib on Windows XP, text boxes and their frames in the Search wizard appeared too wide for the Search wizard window, being cut off on the right side. Any buttons present on the right side, could also be cut off and become only partially visible. (Ref.no: 4609)

8. Repeated occurrences of a free text field were displayed partly overlapping the field below. In a repeated field group in which the last field was a free text field, the repeated free text field was displayed partly overlapping the field below. (Ref.no: 4619)

9. Flickering scrollbars in Find data for the field… window. In some very specific circumstances, opening the Find data for the field… window (Shift+F4) from an empty linked field (in an SQL database), could cause flickering scrollbars in this window, along with missing buttons and texts, making it unworkable. (Ref.no: 4621)

10. Resizing the Adlib window distorted the menu bar. When you resized the Adlib window by expanding it to the right, the menu bar displayed only grey stripes in the expanded part. (Ref.no: 4613)

2 Searching

1. Searching on record number was not possible in non-classical mode. When you had started your application in non-classical mode (you then select the database to work with in the so-called dashboard, an HTML page, instead of in the Search wizard) and in the Search wizard you chose the Record number access point to search with, then Adlib found no records.

[pic]

When you switched back to classical mode (via the Options menu; then restart Adlib), and you searched on record number, then Adlib did find records. (Ref.no: 4548)

2. In detailed display, the wrong initial screen was opened. When you searched for records using an access point to which a so-called initial screen was linked, then the detailed display of a found record was not opened on that initial tab, but on the screen which appeared in the list in the definition of the current data source after the relevant initial screen. (Ref.no: 4230)

3. Searching via an access point on a merged-in field, did not work. When you had associated an access point with an index on a merged-in field, then searching via that access point did not yield any results.

By the way, note that indexes on merged-in fields are advised against because they don’t always contain up-to-date information due to their nature, and produce an empty index on manual reindexing. See the Designer Help (6.5.38.3 or higher) at the Tags to index index option, for more information. (Ref.no: 4580)

4. The Pointer files window could not be opened from within the Expert search system, after the brief display. When you opened the Expert search system from within the Brief display of a search result, then you couldn’t open the Pointer files window from there using the Pointer files button. (Ref.no: 3244)

5. Maker and Role could no longer be repeated in the Query by form Collection. When you opened the Query by form Collection in a Museum application running on a CBF database, then it was no longer possible to insert a second occurrence of the Maker and Role fields to be able to search on two maker names at the same time. (Ref.no: 4222)

6. Narrower terms were not found in internally linked fields on link reference. When you used the Search wizard to search an internally linked field (linked on reference) in an Adlib SQL database on a term which had narrower terms, then none of the narrower terms were found. (Ref.no: 4495)

7. After cancelling the search result for deriving, the QBF also closed. When you had put together a search command in a Query by Form for deriving a record, then the search result appeared in the Available data window, but if the record you were looking for wasn’t in that result, and you clicked the Cancel button to adjust the search criteria, then not only the Available data window closed but the search form as well, and you had to reopen that search form and re-enter the search command. (Ref.no: 4036)

8. Searching an index on a linked term with square brackets in it, did not yield any records. When you had filled in a term with square brackets in a linked field in an Adlib SQL database, for instance Boîte: D [Dessinateurs], and you wanted to find this record via an access point (index) on this field later on, then you could only find the record if you searched on a partial term up to the first square bracket, Boîte or Boîte: D for example. However, in the linked database itself you could find the term record with the square brackets normally. By the way, the same problem could occur for terms with other special characters in them, like an underscore (_). (Ref.no: 4482)

9. An expert search using the WHEN operator resulted in SQL error 189. When you executed an expert search statement using the WHEN operator in an Adlib SQL database, this resulted in an SQL error 189. (Ref.no: 4681)

3 Editing

1. The Change locations procedure could be opened for all databases. When you right-clicked a result set in the Expert search system, you could always choose the Change locations option in the pop-up menu, regardless of the current database or application version.

[pic]

The fix is that from now on, the relevant pop-up menu will only be available for the COLLECT database (in which the objects are registered) in 4.2 applications and higher. This way, you can perform the Change locations procedure on all records in the selected result set. (Ref.no: 4519)

2. For the Change locations procedure, the entered new location was not validated. When you had marked some records in a 3.4 Museum application, started the Change locations procedure and entered a new location which did not occur in the location domain in the Thesaurus, then that location was forced into the Thesaurus without warning.

In 6.5.2, the entered location is indeed validated, and you can only enter existing locations. If you want to use a location which doesn’t exist yet, you’ll have to register that term first in the location (LOCAT) domain in the Thesaurus. (Ref.no: 4402)

3. The Change locations procedure could not be opened from detailed display. The Change locations procedure could only be opened from the brief display, for marked records. With this fix, the procedure can be started as well for the currently opened record in detailed display, regardless of whether it is marked or not. Any other marked records won’t be processed from detailed display. (Ref.no: 4497)

4. The Change locations procedure filled in an incorrect value instead of a date. When you entered a location in the Change locations window, for the currently opened record, and then started the procedure, then a completely incorrect value was entered for the date in the record (no date, but for instance the number 0009 or 0030). (Ref.no: 4556)

5. Upon linking an image, you were asked if you wanted to replace the existing image. When you linked an image to a Visual documentation record, via the Finding image file button or by dragging the image to the record from within Windows Explorer, then Adlib asked you incorrectly if you wanted to replace the existing image. If you clicked Yes, a window opened to save the image, but when you clicked Save subsequently, an error message 80 (copy of file failed) appeared. The path was entered in the image field though. (Ref.no: 4525)

6. An interface language change didn’t work correctly for Adlib SQL. When you switched from one interface language to another via the Language switch menu, opened a record and saved it, and closed and restarted the application, then Adlib started normally with the newly set interface language. However, that language was not set correctly everywhere under the hood, causing values from enumerative fields to still be processed in the previous language when you opened and saved a record. (Ref.no: 4587)

7. After copying a record, a change in the image path was not displayed immediately. Suppose you copied a museum record to which an image was linked, and from the Reproductions tab in the copied record you opened the linked image record in a zoom screen. When you subsequently filled the Identifier URL field in that zoom screen, with a path to a different image, saved that image record and also the object record, then still the originally copied image was shown instead of the newly linked image. The new image only became visible when you returned to the Search wizard or the Brief display and opened the object record again from there. (Ref.no: 3377)

8. A copied linked field could not be pasted. When you copied the value from a linked field to the Adlib Clipboard using Ctrl+D, opened a new record and tried to paste the copied field using Ctrl+K, you found that didn’t work. (Ref.no: 4162)

9. The use of the double arrow in the linked record search screen, could make Adlib hang. When you used the button with the double arrow pointing upward (below the vertical scrollbar) in the Find data for the field… (linked record search screen) window in an application running on a multilingual SQL database, then Adlib would hang or respond very slowly. (Ref.no: 4190)

10. The list of keys in the linked record search screen was not adjusted when changing the search key. When you entered a term in a linked field in an SQL database, e.g. starting with an ‘a’, and to validate it you opened the linked record search screen (Find data for the field…), then the part of the list of found keys that started with an ’a’ was displayed correctly. However, if you then entered a different term in the Find entry field, for example starting with a ‘w’, then the list below it was not adjusted to the new search key: the displayed part of the list did not scroll to words starting with the ‘w’. (Ref.no: 4188)

11. A term selected from the linked record search screen, for a multilingual field linked to a unilingual external database, returned an error 7 when the record was saved and the linked term was clicked. When a multilingual field was linked to a unilingual, external database (e.g. a thesaurus), and from the linked record search screen (Find data for the field…) a term was selected and the record saved, it appeared at first as if for the term a record in the local thesaurus had been created. But when clicking the underlined term, an error 7 was produced by Adlib, reporting a record number. This record number should’ve been of the newly created linked record in the local linked authority database, but it actually wasn’t: no linked record had been created for the term derived from the external database. (Ref.no: 4193)

12. The validation of certain linked fields only worked twice. When you edited a linked field like Maker by entering a non-existing name, left the field and then left the Find data for the field… window using the Esc key, and repeated leaving the field and closing the validation window, then after two times the window no longer appeared, and you could save the record including the new name, although no new record for it had been created in the linked database. (Ref.no: 4271)

13. Enumerative fields could not be used when Adlib was started in rtl mode. When Adlib was started with the -rtl option (for text entry from right to left), and when editing a record you clicked the arrow next to an enumerative field, the list would directly fold in again, with no possibility to choose anything from the list. (Ref.no: 4305)

14. The spelling checker did not report faulty spelling if there was no suggestion for a better word. When you did the spelling check, no spelling error was reported if the dictionary had no suggestions for a right word. Instead, a message appeared telling you that the spelling check was complete. (Ref.no: 4306)

15. A double scrollbar could appear in the Find data for the field… window. When you validated the content of a linked field in the Find data for the field… window, and you dragged the horizontal scrollbar in there (if present), then a second vertical scrollbar appeared next to the first one. (Ref.no: 4414)

16. It was not possibly to link an image from a path that was specified as Storage path. If a Storage path had been set in Adlib Designer for an image field and you tried to link an image from that location in a Visual documentation record then Adlib produced several error messages, like “File already exists. Overwrite?” and when clicking Yes: “Error CopyFile failed for file…” (Ref.no: 4426)

17. Search-and-replace could leave empty occurrences. If you searched-and-replaced the content of an occurrence of a (non-grouped) field by nothing, while the occurrence was not the last occurrence, then the resulting empty occurrence wouldn’t be deleted like it should be.

Note that empty occurrences of a field in a field group, will only be deleted if the same occurrence of every field in the group is empty. (Ref.no: 4500)

18. Emptying an RTF field did not remove the RTF codes. When you edited a rich-text field by deleting the text in it, then the (invisible) RTF codes remained behind. You could observe this after saving the record by pressing Ctrl+R to display the record contents in a different way. (Ref.no: 4570)

19. Diacritical characters were incorrectly displayed in feedback link deletion warning messages. When you deleted a thesaurus record of a term with diacritical characters in it, while at least one catalogue record linked to this term and there existed a feedback link in the thesaurus to this catalogue, then in the second message warning you about the deletion of a term in use in the catalogue, the diacritical characters in the term were displayed incorrectly. (Ref.no: 4614)

20. Forcing a linked term and trying to jump to the next record, did not open the next record. When you entered a non-existing term in a linked field, and without leaving the field you clicked on the Next record arrow button, Adlib asked if you wanted to save the linked record, and then also saved the current record, but did not jump to the next record. (Ref.no: 4576)

21. Under very specific circumstances, occurrences in the Documentation field group got mixed up. When you edited an object record, put the cursor in the Title field on the Documentation tab, typed a non-existing title and pressed Tab, a link to the new documentation record was created. When you put back the cursor in the Title field, clicked the Add occurrece above button, put the cursor in the empty Title field occurrence, entered a new title and pressed Tab again, then the lead word, author and shelfmark fields were moved from the second occurrence to the first occurrence. (If you then stored the record, the lead word that belonged to the second occurrence was written in the title of the first occurence.) (Ref.no: 4626)

22. The validation list was empty for a unilingual, linked field in a multilingual database. When you put the cursor in a non-multilingual, linked field in a multilingual database and opened the Find data for the field… window (Shift+F4), then in it no list of possible terms was displayed. The data language in which you were working didn’t matter. (Ref.no: 4652)

4 Saving

1. A user name with diacritical characters was saved and displayed incorrectly. When a user with a name with diacritical characters edited and saved a record in an Adlib SQL database, then that name was stored in other, strange characters, as could be seen in the relevant fields on the Management details tab. (Ref.no: 4540)

2. On saving from within the Media Viewer, the file name had to be entered manually. In the Media Viewer in the detailed display of a record, when you clicked the Save as button (to also save the image elsewhere), you had to enter the file name manually in the Save image as window, while that file name was already known. This fix ensures that the file name has already been entered for you. (Ref.no: 4420)

[pic]

3. Existing hard returns in tag BE changed into little squares. When, in an existing record in an Adlib Oracle or Adlib SQL database, you edited and saved an existing record repeatedly, while in the Description field (BE) a text with hard returns was present, then after saving a couple of times, those hard returns turned into little visible squares. With every repeated storage, new squares were added. (Ref.no: 4504)

4. An invalid value could be stored in an ISO date field. When you did not enter a date in ISO format into an ISO date field, yet entered some word instead, and subsequently clicked another field with the mouse pointer, clicked Postpone in the message about the invalid date and subsequently saved the record, then the record was indeed stored with the invalid value. (Ref.no: 3258)

5. Saving a derived object record was not possible without changing the object number first. When you derived an object record from the External object catalogue (in an Adlib SQL database) into the Internal object catalogue, and tried to save it, you got an error 189 (“Cannot write to file… Cannot insert duplicate key row…”). You could save the derived record only after changing the object number. (Ref.no: 4353, 4438)

6. Title of part was not stored in linked copies record. When you filled in the Title of part field in the copies field group in a book record and saved the record, then the title of part was not written back to the relevant copies record. (Ref.no: 4663)

7. More than one preferred term found window displayed when storing a record, while the link was already resolved. When a linked field contained a value wich appeared multiple times in the linked database, and the record was put into edit mode, then copied, after which the original record was saved, then Adlib displayed the More than one preferred term found window. This was not correct because nothing changed in that record - the linked field was already resolved - so this window should not have appeared. (Ref.no: 4664)

5 Printing

1. In Word templates, field names with a dot in them were processed incorrectly. When you printed records to a Word template which contained field names with a dot in them, for example creator.role, then Adlib only looked at the part in front of the dot. In the example of creator.role, the content of the creator field was printed, instead of the content of the creator.role field. (Ref.no: 4454)

2. On choosing a Word template, .dotx templates were not visible. When you had marked records for printing, clicked the Print button and chose the Create a report with Microsoft Word templates option in the Print wizard, then templates with the .dotx extension were not visible in the Explorer window in which you had to select the desired template: only templates with the .dot extension were visible. You could enter the name of a .dotx template manually though. (Ref.no: 4515)

3. Adlib froze after choosing a certain predefined output format for printing labels. When choosing the Labels with shelfmark output format to print some book records, Adlib froze after you indicated on which label the printing had to start. The error was in the ADAPL Print command handling of strings containing only spaces. (Ref.no: 4352)

4. Specificly indicated field occurrences on Word templates were not filled. When you printed marked records to a Word template which had field references to specific occurrences ( for example), then no data was retrieved for these references. (Ref.no: 4552)

5. Printing to file using a stylesheet produced UTF-16 output file. When you printed to file using a stylesheet created for this purpose, the resulting output file was encoded in UTF-16 whilst it should be UTF-8. (Ref.no: 4661)

6 Adloan

1. The borrower name was not displayed in messages about reservations. When a borrowed material was returned and now there was a reservation on it, then a message about it did appear, but it showed only the borrower number, not the borrower name. This was also the case when you opened the record of a borrower who had reserved materials to be collected; the relevant message didn’t have the name of the borrower either, only the number. (Ref.no: 4594)

7 Serials

1. When checking in a new issue, the last occurrence of the received issues list was apparently removed. When you added an occurence for checking in a new issue by clicking the Add occurrence for a new serial? checkbox in a Serials record, a new occurrence was indeed created on top of the listed received issues, but the last occurrence had suddenly disappeared. Switching to another screen tab and back would display all occurrences correctly again. (Ref.no: 4551)

8 Importing

1. Importing via adlwin.exe ignored record locks. When you had opened a record in edit mode in your Adlib application, and on a different computer someone else imported records via the same application in the same database, then the record in edit mode could be overwritten despite the present record lock. (Ref.no: 4599)

9 WWWOPAC

1. Crash on retrieval of a record with an ampersand in the title. When you wanted to retrieve a title with an ampersand (&) in it, using a simple query (like searching on the name of an author), then wwwopac crashed with a message saying that the ampersand character wasn’t escaped. (Ref.no: 4608)

2. WWWOPAC.exe could not retrieve values from a multilingual field, other than the invariant value. Queries to retrieve values stored in a multilingual field (in an Adlib SQL database), either by specifying a data-language in the query or not, did not retrieve any values. Searching with “invariant=true” and no data-language did retrieve the invariant value. Similar queries executed with wwwopac.ashx (instead of with the .exe version) all worked as expected. (Ref.no: 4550)

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

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

Google Online Preview   Download