adlib release notes 7.2 - adlib - flexible software for ... · web viewinserting the letter...

Release notes

Axiell ALM Netherlands B.V.Copyright © 2015 Axiell ALM Netherlands B.V.® All rights reserved. Adlib® is a product of Axiell ALM Netherlands B.V.®

The information in this document is subject to change without notice and should not be construed as a commitment by Axiell ALM Nether-lands B.V. Axiell 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 Quick searching anywhere in Adlib..............................................31.2 Continue searching on equal field contents.................................41.3 Selecting another data source from anywhere in Adlib...............51.4 Rearranging sorting fields............................................................61.5 Managing your favorites..............................................................71.6 Renamed and relocated functions...............................................81.7 Import image in Media menu.......................................................91.8 Relational searching optional in Advanced search.....................101.9 Currently active data language with icon..................................111.10 Pinning or unpinning the Pointer files window.........................111.11 Write set to assign the lowest free pointer file number...........121.12 New display of absent multilingual data..................................121.13 New interface languages for Adlib...........................................131.14 Locally viewing your records in The Collection Cloud..............141.15 Images with colour profiles supported in Adlib........................141.16 Designer Help in new format....................................................151.17 Sorting in the Hierarchy browser.............................................171.18 Create .inf documentation in a custom format........................191.19 Uploading data to Europeana...................................................21

1.19.1 Uploading and pushing data, the quick way......................231.19.2 Uploading and pushing data, your own way......................251.19.3 Configuration.....................................................................32

1.20 Forcing identical terms in different domains............................361.21 External translation of application texts..................................371.22 Adapl data preprocessing for label printing.............................431.23 ADAPL function for locking fields.............................................461.24 After-read adapl option for import jobs....................................461.25 New reserved ADAPL variable &6[7]........................................481.26 Adlib startup option for data language....................................48

2 Other improvements.........................................................492.1 Display.......................................................................................492.2 Searching...................................................................................512.3 Editing........................................................................................532.4 Printing.......................................................................................592.5 Pointer files................................................................................602.6 Adloan........................................................................................602.7 Import and export......................................................................612.8 Designer.....................................................................................612.9 ADAPL........................................................................................632.10 SDI.exe.....................................................................................64

2.11 Registry....................................................................................65

IntroductionThese release notes describe a number of improvements in the Adlib executables, which are implemented in Adlib 7.2. This release is avail-able from mid-November 2014 to all customers with a support 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 ([email protected]) for the necessary password and your license file. Place this file (you can make copies of it) after in-stallation 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 newer versions in-accessible 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.2 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.2 too (this re-quirement does not apply to wwwopac.ashx). This may have con-sequences 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 13-1-2015

mailto:[email protected]

Introduction Adlib 7.2

Because of changes in the .inf format due to the addition of new inter-face languages in Adlib 7.2, the following limitations apply when you edit your Adlib database structures using Designer 7.2: Afterwards you’ll no longer be able to adjust your database struc-

tures using an older version of Designer. You’ll have to use De-signer 7.2 from now on.

Afterwards you can no longer use Adlib versions (adlwin.exe and adloan.exe) older than version 7.2.

Afterwards you’ll have to update wwwopac (.exe or .ashx) to ver-sion 7.2. The update of the .ashx version in itself may have con-sequences too:o From wwwopac.ashx 3.7.14028, field names specified in the

briefFields, detailFields, searchFields and authentica-tionConfiguration sections of adlibweb.xml will be validated to the requirements for XML element names on application start. If a field name doesn’t meet the requirements, the API will throw an exception (AdlibWebException) with details about the field name, section and the database. If you encounter the exception after your upgrade to wwwopac.ashx 3.7.14028 or higher, you’ll have to correct the problematic field names in the data dictionary (.inf file) and subsequently in adlibweb.xml.

The XML element name requirements are as follows: names may contain letters, numbers and other characters but they cannot start with a number or punctuation character or with the string ‘xml’. And names are not allowed to contain spaces.

o The Adlib API as used by the current version of wwwopac.ashx implements a strict policy concerning the definition of field tags: all tags used in records that you read or write using the API, must have been defined in the data dictionary. So when you’re about to start using the new version of wwwopac.ashx for your website, you may encounter errors because of this, since it is not uncommon in Adlib applications for tags to have been defined on the screen only or to have ended up in records via an import or adapl procedure. Axiell ALM has sev-eral tools in development (currently called ValidateDatabase and RemoveTagsFromData) which you can use to track down any undefined tags in your records (amongst other functional-ity), after which you can still define them in the relevant .inf to solve the issue. Ask our helpdesk for the status of these tools and the accompanying documentation.

13-1-2015 2

1 New functionality

1.1 Quick searching anywhere in AdlibFrom Adlib 7.2 you’ll be able to quickly start a new search from any-where in Adlib, like from the detailed or list display, by selecting the desired access point from the new Quick search drop-down list in the Adlib Start menu. The function becomes active as soon as you’ve se-lected a data source to work with, in Step 1 of the Search wizard.

The list contains the same access points as Step 2 of the Search wiz-ard, for the currently opened data source.

After your selection, the active display will close and the Search wizard will open directly with the chosen access point in Step 3.

This works a lot faster than having to click the Back button from record display repeatedly to return to Step 2 in the Search wizard to be able to select a new access point.

3 13-1-2015

1.2 Continue searching on equal field contentsAdlib 7.2 introduces an extra way of searching: from within every in-dexed field in detailed display of a record you can search directly for all records with the same field contents, simply via the pop-up menu.In detailed display of a record, suppose you encounter the value ‘can-vas’ in the Material field. If you decide you’d like to see all records with the material ‘canvas’, just right-click the relevant field and in the pop-up menu select the Find records for … option (Find records for ‘mate-rial=canvas’ in this example). The search will be performed untrun-cated and without relations. The search result will be presented in the brief or detailed display, as usual.

When the option is greyed out, the field will have no index so you won’t be able to continue with this search option.

4 13-1-2015

Adlib 7.2 New functionality

1.3 Selecting another data source from anywhere in AdlibFrom 7.2, you can open a different data source from anywhere in Adlib (except while editing a record), using the File > Select database menu. It doesn’t matter if you’re currently searching, viewing a record in de-tailed display of are working with pointer files: simply click File > Se-lect database and select the desired data source in the submenu. Move the mouse pointer over the thin bar with the arrow at the top or bottom of the submenu to have the list scroll up or down and show you more data sources. (The databases and their datasets won’t be displayed in a hierarchical structure here.) Immediately after your choice, Step 2 in the Search wizard will open, for the relevant data source.

5 13-1-2015

New functionality Adlib 7.2

1.4 Rearranging sorting fieldsDe brief display of a search result can be sorted on multiple fields. Click the Sort button in the Start menu to open the Sort window and then double-click the fields on which you’d like to sort.

New in 7.2 is that the order of the selected fields in the list on the right (and consequently the sorting order) can now easily be changed: in the Sort field properties list, select the name of the field that you’d like to move and use the key combination Ctrl+ (the Ctrl-key combined with the arrow-up key) or Ctrl+ to move the sorting field up or down.

13-1-2015 6


1.5 Managing your favoritesIf you often fill in the same texts, but you don’t want to have to type them each time, then you can label such texts as favorites for that field, so that you’ll be able to select that text directly from the right-click pop-up menu for that field next time.In 7.2 you have the added option to manage the favorites you col-lected earlier: it is now possible to delete selected favorites or to change the order of the favorites in the pop-up menu.Right-click the field for which to want to manage the favorites and in the pop-up menu select the Manage favorites option.

In the Manage favorites window you can move a selected text up or down using the blue arrows or remove it with the red cross. Click OK to store the changes.

7 13-1-2015


1.6 Renamed and relocated functions New Publish menuThe Collection Cloud buttons have been moved from the Start menu to the new, persistent Publish menu. In it you’ll also find the new Euro-peana buttons (see chapter 1.19 for more about that).

Expert search renamed to Advanced searchThe Expert search window where you can put together any desired search statement, will be called Advanced search from now on. You can open the window from the Adlib Start menu, for example, after you’ve selected a data source in Step 1 of the Search wizard.Further, the Query by form option has been renamed to Search by form.

13-1-2015 8


Show invariant data has been removed

The Show/Hide invariant data button has been removed. If a multilin-gual field has no value in the current data language while there exists an invariant value in a different data language, then that value will be displayed (greyed out) by default, from now on. (Also see chapter 1.12.) Find image file renamed to Import imageThe Find image file button in the Edit menu and the Explorer window it opens, have been renamed to Import image.

1.7 Import image in Media menuThe Import image function, to link an image file to a record, was al-ready available in the Edit menu but has now also been added to the Media menu in which all Media Viewer functions can be found. It doesn’t matter from which menu you start the function.

9 13-1-2015


1.8 Relational searching optional in Advanced searchPreviously, searching a linked field in a SQL database on a non-pre-ferred term via a search statement in the Advanced search would al-ways replace that term in the background by the preferred term which would then be used in the actual search. So it made no difference if you searched on the preferred term or on (one of) the non-preferred term(s) associated with it. From 7.2 this non-preferred term substitution only takes place if the new Use relations checkbox has been marked (which is the case by default). The setting will be stored for next time.

13-1-2015 10


Searching with relations enables Adlib to actually search on the pre-ferred term when you’ve entered a non-preferred term. Adlib will also retrieve records with narrower terms and terms that are equivalent to the search key. This means that you can find more records than you may have expected. (Note that the search will not include any related terms.) However, hierarchical searching does influence the speed of searching: non-hierarchical searching is just faster because you’ll only be searching on the entered term, nothing else.The new option doesn’t apply to CBF databases.(Ref.no: 6560)

1.9 Currently active data language with iconTo make it more noticeable to users that they’re working in a multilin-gual application and to draw their attention to the currently set data language, a flag icon is now present in front of the code for the current data language in the status bar and this information has more space on either side. If your application is not multilingual, the data language box in the status bar will remain empty.

1.10 Pinning or unpinning the Pointer files window

In 7.2 the possibility has been added to decide for yourself if the Pointer files window must remain open after you’ve opened a pointer file (as was the default case in 7.1) or if it should close automatically (as was the case in even older versions). To this end, a pushpin icon has been added to the lower left corner of the window. Click the push-pin to switch between the two modes: blue means pinned down, grey means unpinned (and this has become the default setting again). Adlib remembers your setting for next time.

11 13-1-2015


A pinned Pointer files window remains opened after you’ve chosen a pointer file and remains opened until you close it manually or until you start editing or outputting marked records in some way. The window closes automatically as well when you return to Step 1 of the Search wizard. Still, in detailed or brief display, amongst others, you can leave the window open, for instance to be able to quickly view several pointer files, one after the other. A pinned window can be closed man-ually via the Cancel button or via the white-red cross in the upper right corner of the window.

1.11 Write set to assign the lowest free pointer file number

The Write set function in Adlib did always assign a number to a new pointer file which was 1 higher than the previously assigned number, even if lower numbers were available (when earlier created pointer files had been removed since then, for example). This has changed in 7.2: now when you let Adlib assign the new pointer file number it’ll be-come the lowest free pointer file number. (Ref.no: 6550, 4622)

1.12 New display of absent multilingual dataIn Adlib 7.2, the Show/Hide invariant data button has been removed. If a multilingual field has no value in the current data language while there exists an invariant value in a different data language, then that value will be displayed (greyed out) by default, from now on. This makes translation of the relevant data more comfortable.

Such an invariant field value will also be displayed in a different colour: light grey. The distinction clarifies that it concerns invariant data and that the relevant field value(s) haven’t yet been stored in the current data language in the record. However, as soon as you place the cursor in such a field with light grey text, the text colour will return to normal and that means that the value, unaltered or edited, will indeed be stored in the current data language in the relevant field as soon as you save the changes in the record. As long as field values are displayed in light grey, they won’t be stored.

13-1-2015 12


If a multilingual field hasn’t got a value in the current data language while it does in one of the other languages and no invariant value ex-ists for the field in this record, then in display mode light grey suspen-sion points will be displayed in the field (underlined if it concerns a linked field).

In edit mode, the suspension points will be displayed too as long as the cursor is not located in the field: as soon as the cursor is placed in the field, the suspension points will disappear. In no case will the sus-pension points be stored in the record: they’re only meant to indicate that data in another data language has already been entered in the field.

1.13 New interface languages for AdlibThe number of interface languages in which Adlib applications can be displayed, has been extended again. The currently available languages are: English, Dutch, French, German, Arabic, Italian, Greek, Por-tuguese, Russian, Swedish, Hebrew, Danish, Norwegian, Finnish and (from version 7.2.15007.1) Chinese.In Adlib Designer you can set the application language (the language in which field names and labels and such are displayed in Designer) to each of these languages as well.

13 13-1-2015


1.14 Locally viewing your records in The Collection CloudFrom Adlib 7.2 a list of records that you’ve uploaded earlier to The Col-lection Cloud from within the current data source, can be requested in your application.Click the new List records button in the Publish menu of Adlib to show all relevant records in the list display. The button is available from sev-eral locations in Adlib, after selecting the desired data source in Step 1 of the Search wizard.

It is important to realize that Adlib uses the original record numbers of the records you uploaded earlier to be able to show those records in the list display now. This means that applicable records which have since been removed from your database, cannot be shown.Further note that the new button won’t be present in the toolbar of Adlib under Windows XP.

1.15 Images with colour profiles supported in AdlibCertain types of images files, like jpeg and tiff, can have embedded, generic colour profiles which were embedded explicitly when the im-age file was created or edited. The effect of a generic colour profile is that it alters the colours of the relevant image to some more desirable spectrum, although the changes are usually minute. Combined with monitor and/or printer specific colour profiles, a publisher has full con-trol over the resulting colours. Typically, such profiles are used in (desktop) publishing environments or other professional media pro-cessing businesses where colour fastness of images is very important.From 7.2, adlwin.exe supports images with embedded ICC or WCS colour profiles, meaning that the embedded profile will actually be ap-plied whenever images are displayed in Adlib. (Previously, such im-ages were displayed without the colour profile being applied.) (Ref.no: 6543)

13-1-2015 14


1.16 Designer Help in new formatWith Designer 7.2, we introduce a new documentation format called Web Help, which displays in your browser. You can find it online at: http://documentation.axiell.com/alm/en/index.html?ds_designer.html. In the not too distant future it’ll replace the 7.1 version of the HTML Help as currently still offered by Adlib Designer and some other tools. For the time being though, you’ll have to click the link above (which you can save as a favorite in your browser) to open the 7.2 version of the Designer Help. Some of the advantages of Web Help over HTML Help are: You always get to see the most up-to-date version of the docu-

mentation. Every detail page has its own URL, like: http://documentation.axiel-

l.com/alm/en/index.html?ds_adaprogrammingvariables.html or http://documentation.axiell.com/alm/en/index.html?ds_general-topicserrorcodes.html). This means you can store your often used help pages as favorites in your browser. And using a URL is also an easy way for you to refer to a help text in an e-mail to the helpdesk, should you have related questions. The URL can be copied from the URL box or via the Permalink button in the toolbar of the Web Help (depending on the browser you are using).

If the button isn’t immediately visible on the right side of the Web Help toolbar, press F5 or Ctrl+F5 to refresh the page in your browser.

Succinct release notes per program will be included, like: http://documentation.axiell.com/alm/en/index.html?ds_releasenotes7_2.html

The Search tab allows for searching on single or multiple keywords (truncated using *) or searching on a phrase enclosed in double quotes. Click a search result link to open it on the first tab.

You can have multiple detail tabs open at once. If you want to hold on to the help text as it is currently displayed on the first tab while searching for other texts, click the Copy tab button in the toolbar to copy the first tab to a new tab. This leaves the first tab free to display other topics when you click one in the contents window pane or on the Search tab:

15 13-1-2015

http://documentation.axiell.com/alm/en/index.html?ds_releasenotes7_2.html



http://documentation.axiell.com/alm/en/index.html?ds_generaltopicserrorcodes.html

http://documentation.axiell.com/alm/en/index.html?ds_generaltopicserrorcodes.html

http://documentation.axiell.com/alm/en/index.html?ds_adaprogrammingvariables.html

http://documentation.axiell.com/alm/en/index.html?ds_adaprogrammingvariables.html

http://documentation.axiell.com/alm/en/index.html?ds_designer.html


To be honest, there are some minor disadvantages too: An internet connection is required to view the Web Help. However,

if you don’t (always) have one, we can offer a .pdf file of the Web Help instead.

Some help texts may concern a newer version of the software than you are still using, but every new option will be accompanied by the number of the version in which it was introduced. This way you’ll always know when some option doesn’t apply to your ver-sion of the software.

Tip: create a shortcut to the Adlib Web Help

If you’re a regular user of the Designer Help, having the online ver-sion only as a favorite in your browser might still be too cumbersome. Instead, you could make a shortcut to the Web Help for quick access:1. Right-click your favorite browser’s shortcut icon and select Copy

to > Desktop in the pop-up menu.2. Right-click the copied icon and select Properties in the pop-up

menu.3. On the General tab in the Properties dialog, change the name of

the shortcut to Adlib Web Help, for example.4. On the Shortcut tab, enter the following URL (preceded by a

space) behind the existing Target to your browser’s executable: http://documentation.axiell.com/alm/en/index.html?ds_designer.html (This may not work in all browsers but it does in Internet Explorer and Mozilla Firefox.)

5. Click OK in the Properties dialog and you’re done. Your new short-cut should open the Adlib Web Help immediately.

1.17 Sorting in the Hierarchy browserFor any term with narrowers, the Hierarchy browser always presented the narrower terms in the order in which the occurrences of the rele-vant field (e.g. the Parts field in an archive record) were stored in the 13-1-2015 16


record. If the Sort values option for the internal link definition in Designer had been set to Ascending or Descending (instead of the default Unsorted), then the occurrences of the relevant narrower field would be sorted al-phabetically ascending or descending before you stored an edited record. The same order would then also be displayed in the Hierarchy browser. Yet when the values to be sorted on were of the alphanumerical type, you would not be able to sort these occurrences in the record and the values in the Hierarchy browser correctly (namely alphanumerically).From Adlib 7.2, narrower occurrences in the record and the corres-ponding values in the Hierarchy browser are sorted ascending or de-scending according to the Sort values setting for the internal link (or not sorted at all), and the type of sorting will be determined by the Key type of the index on the main term field in the internal link definition. So if you have an internal link definition like the following present in the Collect database in a model 4.2 application: part_of_reference <-> object_number <-> parts_reference, and you would set the Sort values option for it to Ascending and you would reindex the invno (IN) index (for the object_number field) with the Key type now set to Alpha-Nu-meric, then object numbers in the Hierarchy browser will now be sorted alphanumerically ascending. (If the Sort values setting is left to Unsorted, no sorting will be applied.) Note that the sorting of the narrower field occurrences (Parts in this example) in any record will only be changed to the newly set sorting type when you edit and save the record: the sorting order in the Hier-archy browser no longer depends on the stored occurrences sorting or-der though.

17 13-1-2015


Below, on the left, you can see an example of an archive hierarchy sorted alphabetically on object number, while the figure on the right displays the same hierarchy alphanumerically sorted on object num-ber. (Ref.no: 5561)

Limitations of alphanumerical indexes

When an alphanumeric value is indexed, it is reformatted so that ev-ery number in the string becomes a ten-digit number starting with ze-roes. For example, when in a record the string A238HJK08aa2 has been registered, the index value (of which the user can remain un-aware) becomes A0000000238HJK0000000008aa0000000002. So, if the field you wish to create an alphanumerical index for, contains val-ues with many letter-number alterations, the index values can be-come pretty lengthy and therefore you should set the Key size option of this index sufficiently high: for CBF databases this is no problem but the key size for an index in an Adlib SQL database is limited to 100 characters. So if you employ an Adlib SQL database and you esti-mate that any reformatted alpha-numeric strings might exceed 100 bytes, then it's best not to create an alphanumerical index for this field and just accept alphabetical sorting.

13-1-2015 18


1.18 Create .inf documentation in a custom formatIn some Designer tools, like in the Application browser for a selected database or application, or in the Import or Export job editor, or the Record lock manager, it's possible to generate documentation about the currently selected object or the list of objects, by choosing File > Create documentation in the menu.A Documentation window will open with a detailed description of the structure of the selected object. For a database for instance, this infor-mation comprises data on the database, its datasets, fields, indexes and links. And the documentation for an application will contain a de-tailed overview of its properties, menu texts and data sources.The overview is nicely laid out, but if you rather have the bare XML view, you can switch to it through the View menu. In either view you can print the file via the menu or the Print documentation button, or save it as an XML file.

19 13-1-2015


You may also select the text, or part of it, with the mouse cursor, and copy (Ctrl+C) and paste it (Ctrl+V) in any other document.From Designer 7.2 (well, actually from version 7.1.14255.1), the View menu in the Documentation window for a selected database structure also contains the Fieldlist to CSV option.

This option generates a .csv file containing a field list with some field properties. The header line contains the property names.

In some cases you may find this type of documentation a better cross reference than the information produced by the List or XML option. Note that the Documentation window display doesn’t respect the line endings in the generated .csv file, but that the file does contain line breaks, as you can see when you save the file as a .csv file and open it in MS Excel. (Contrary to the screenshot above, all lines are typically displayed consecutively in a single sentence if the window is wide enough.) Also note that, to save this documentation as a .csv file, in the Save documentation as dialog you have to type the .csv extension behind the desired file name and set the Save as type option to All files.

13-1-2015 20


Creating your own database documentationBut that’s not all. The View menu in the Documentation window does not only show the List, XML and Fieldlist to CSV options, but also any other custom XSLT stylesheets in the new \DatabaseInfo subfolder of your Designer \Xsl folder. In there, you can already find the FieldList-ToCsv.xsl stylesheet. You can copy this stylesheet and adjust it to your liking or build an entirely new one based on the XML version of the documentation (there’s no .xsd available currently), to create your own type of database cross reference.You can do the same for your application structures, by the way, by creating a new stylesheet and putting it in an \ApplicationInfo sub-folder next to the \DatabaseInfo subfolder. This subfolder isn’t present yet by default, because there’s no applicable XSLT stylesheet yet ei-ther.Important to note is that the location of these XSLT stylesheets de-pends on how you installed Adlib Designer. The zipped version which you can download from MyAdlib can be placed anywhere on your sys-tem or network, so you will know where to find it. When you install a new version of Designer, probably in a different folder, you just have to copy your custom stylesheets from \Xsl\DatabaseInfo in your old De-signer folder to the same subfolder in your new Designer installation and you’re done. However, if you are working with the click-once version of Adlib De-signer, which automatically updates whenever you start Designer (and an update is available), the installation folder can be a little hard to find. When you run an updated click-once Designer version for the first time, the status bar will show you the destination of the installation. Typically, the path has the following syntax: C:\Users\<your_name>.<your_domain>\AppData\Local\Apps\2.0\8W4ACD087.LTL\RAUT130.AO0\adli...exe_c0bd10001_none_14dc8ee48. The alphanumerical parts probably differ completely. Of the subfolders at the lowest level, choose the one that has been installed most recently to find your cur-rent click-once Designer installation. You can edit or add stylesheets for database structures there, in the \Xsl\DatabaseInfo subfolder, but do also create backups of those files because with the next automatic update you may lose them as the update will be installed in a new sub-folder. You will then have to copy your backup XSLT files to \Xsl\DatabaseInfo in the newly installed version to have access to them again.

1.19 Uploading data to EuropeanaAdlib 7.2 offers integrated access to the Europeana Connection Kit (ECK) enabling you to upload selected records to a so-called aggrega-tor for Europeana, the European cultural and scientific heritage collab-

21 13-1-2015

http://www.europeana.eu/portal/


oration offering an internet portal to millions of digitized books, paint-ings, films, museum objects and archival records. The ECK was developed in the Europeana Inside project, a cooperative project funded by the EU, in which Axiell ALM participated as a techni-cal partner. The goal of the ECK is to facilitate the contribution of data to the Europeana portal.Records will not be uploaded to Europeana directly: first you’ll upload records to the ECK, an intermediate third-party web service, allowing you to prepare your data online for the aggregator (like for example: http://euinside.k-int.com/dpp/home) and ultimately for Europeana, giv-ing you full control over the final data which will be collected by Euro-peana at some later time. As a content provider you’ll solely have to deal with the aggregator as you’ll have no influence over the planning and procedures involved in Europeana’s harvesting of the data from your selected aggregator.Before you can start using this functionality in Adlib, we recommend you contact the Collections Trust: http://www.collectionstrust.org.uk/ to obtain more information about how to participate.Thus far, the preparation and submission of collection data to Euro-peana was quite labour-intensive and for Adlib users it usually meant having to install an OAI server/repository which had to be harvested by an aggregator, a process over which you have no control.As more and more institutions open up their collections by sharing their data on the internet (as already possible on Axiell ALM’s The Col-lection Cloud for example), the ECK and its direct accessibility from within the Adlib user interface is therefore again a leap forward as it allows you to easily “push” your object data to an aggregator for Euro-peana without requiring an OAI server (instead of having to rely on the “pull” of aggregator harvesting), also giving you much more control over exactly which data will be submitted.After the initial setup (see chapter 1.19.3 ), you’ll find two active but-tons in the new Publish menu in Adlib, allowing (authorized) users to upload a selection of records to the relevant ECK web service and sub-sequently to push the validated and converted data (LIDO or EDM) to the aggregator.

13-1-2015 22

http://www.thecollectioncloud.com/

http://www.thecollectioncloud.com/

http://www.collectionstrust.org.uk/

http://euinside.k-int.com/dpp/home


1.19.1 Uploading and pushing data, the quick waySince the upload and ECK functionality offer many advanced options, which you won’t always need, let’s first discuss the quick route through the forest:1. In your object catalogue, find some records you wish to upload and

mark them in the brief display.2. Click the Upload record(s) button. Adlib will generate a temporary

Adlib XML file of the records to upload and will then open the Euro-peana upload wizard. Typically, you can just click Next here, un-less you want to create some reference of your upload, which you can do by marking the Create pointer file from selection option and/or the Retain the output files (xml, lido, zip) option.

3. The next page in the upload wizard shows you the procedural steps in the automatic upload process as they take place. You’ll notice the Adlib XML is transformed and validated to LIDO and fi-nally transferred to the record set manager at the ECK web ser-vice. Click Next.

23 13-1-2015


4. The final step of the wizard displays a log of the processed actions. If you want, you can copy the log to the clipboard or save it to a file, for future reference. Click Finish to close the wizard.

5. We’re almost done now. Next, click the Manage record(s) button in the Publish menu to open the Europeana set manager. This looks quite complicated but if all the records you’ve uploaded are repor-ted here as being Valid and Ready, then all you need to do now is click the Data push option in the right window pane to push your data to the aggregator (where it will wait for Europeana to harvest it). Before you do so, you may select one of the records in the list and click Preview to see how it will look on Europeana. If you’re not happy with the result, just don’t click Data push but instead Delete the problematic (selected) records from the list and Close the Europeana set manager.

6. Wait for the transfer of your data to the aggregator to finish and click Close in the final message.

13-1-2015 24

Object number

Validation statusReady status


1.19.2 Uploading and pushing data, your own wayIf you’d like to have more control over the different procedural steps or if errors occur while uploading and/or pushing your data, you’ll have to know a little bit about the advanced options available. Upload options Input file and Destination set – There are really two ways to

create a record selection to upload. The first is to mark records in the brief display of Adlib. This will cause the Input file and Destination set options to be read-only. The Input file box will show the path to the temporary XML file which will be created by Adlib and Destination set displays the cur-rent dataset name (being both source and destination) and next to it the real database name it represents.

The second way is to not mark any records before you start the Europeana upload wizard and select an earlier made XML file (for-matted as “grouped” XML) containing the data to be uploaded. Click the Browse button to select the desired XML file on your sys-tem. The XML file can be the result of an earlier export to grouped XML from within Adlib or the saved result of an earlier upload to the ECK (see the Retain the output files (xml, lido, zip) option). Why you would want to do it like this is up to you: maybe you’d just like to check the bare source data before uploading it.

25 13-1-2015


The Destination set drop-down list then allows you to select the “set” into which these records should be uploaded. You’ll find this list effectively contains the names of all the data sources in your Adlib application. For the time being, the rule of thumb here is to simply select the source dataset of the record XML. The option is here really for internal or future use, as its purpose is actually to set the folder name (namely the relevant Adlib database name as indicated behind the list , e.g. collect) in the record set manager of the ECK, into which the uploaded records will be stored, while Eu-ropeana has no subdivision in such datasets nor is there in the record set manager currently a filter to allow you to show up-loaded records per dataset or something like that. Also, the cur-rently available stylesheet that will transform your Adlib XML to LIDO, will only do that for (unilingual) object records. So the rec-ommendation is to select the name of the original data source of the uploaded records here.

Retain the output files (xml, lido, zip) – Particularly for a hand-picked record selection you may want to check the different stages the record XML is put through before it is uploaded to the ECK. Mark this checkbox to automatically save these stages in four different XML files in your Windows Documents\Adlib\<database name_date>\ folder, namely: input.xml (containing the source grouped XML), parsed.xml (the XML after it has been parsed, maybe only showing different indentation), lido.xml (the XML after initial conversion to the LIDO format) and lido_pid.xml (in which the image references and LIDO record IDs have been re-solved to proper URLs using your configuration settings). The lido_pid.xml file is also present in the output.zip file, renamed to adlib_lido.xml.

Delete existing records from the set – Set this option if you’d like to remove all present records from the ECK record set man-ager before the currently uploaded records are inserted. You may want to do this if previous uploads were not satisfactory. Even though record contents will be deleted, a reference to the old record will remain, flagged as deleted, and you can still list those deleted records in the record set manager. To make things even more complicated, records will only be deleted if you do not also mark the Don’t make the records ready (update only) option below: if you do mark that option too, the only records that will be removed now will be records that were

13-1-2015 26


never made Ready before (more about this in the section: The record set on the ECK web service).Also realize that data which has already been pushed to the aggre-gator cannot be deleted from the aggregator anymore: deletion of uploaded data is currently only really possible before it has been pushed. It is possible though that a future version of the ECK will allow deletion from the aggregator, but that hasn’t been imple-mented so far.

Don’t make the records ready (update only) – Select this op-tion only if you want to upload records and have them validated but not yet commited. This advanced option is for experienced users only since it may cause two versions of each record to exist temporarily in the ECK record set (if those records were uploaded before). This allows you to upload records just to see if they vali-date and maybe because you’d like to preview them, without over-writing any earlier uploaded data in the record set which already has the Ready status.If you mark this option, you’ll have to do a manual Commit in the Europeana set manager later on to make the newly uploaded records Ready for data pushing, if desired. If you don’t, you can still push the “old” version of those records though, before dele-ting the newly uploaded ones.For more details about the workings of the ECK record set, see the section: The record set on the ECK web service.

Create pointer file from selection – If you’d like Adlib to auto-matically create a pointer file for the records that you marked in the brief display, then select this option. You can use the pointer file for later reference, to check which records have already been uploaded, for instance. The pointer file name will be formatted like this: Records uploaded to set: <database name>. The Create pointer file from selection option will be inactive if you haven’t marked any records because you are planning to use an input file instead.

Europeana set manager optionsThe upper list box in the Europeana set manager will display uploaded records (even deleted ones), their latest update date and time (from the server) here and their validation Status and Ready status. It may take several seconds before your uploaded records become vis-ible or before any updates have been processed, so please be patient. The actions which are still awaiting to be processed on the server are listed in the Queue box. As long as the Next update in 15 seconds op-tion at the bottom of the window is marked, the set manager will check with the server and update the list and the information on the other tabs every 15 seconds automatically, but it may take even longer than that for an update to be processed. Instead of waiting for the next 15 seconds you may also choose to click the update now op-

27 13-1-2015

Actions


tion next to it to see if the results are in yet. The Queue will become empty after all queued actions have been processed.

Status valuesPossible Status values are: Valid – Validation of the uploaded LIDO XML has passed. Invalid – Validation of the uploaded LIDO XML has not passed. In-

formation about the error leading to the failure can be found on the Errors tab. If the error states: Failed to communicate with web service, the error lies with the third-party web service but is proba-bly temporary. Then click the Validate option on the right, repeat-edly if necessary, to try again until succesful.

Not checked – The ECK web service hasn’t come around to vali-dating your upload yet. Please just wait until it does.

Ready valuesPossible Ready values are: Yes – The relevant records have been validated and are ready to

be pushed to the aggregator, using the Data push option in the right window pane.

Yes (old) – The relevant records have been validated and are ready to be pushed to the aggregator, using the Data push option in the right window pane. However, there’s also a newer version of these records present in the record set (unless their Status is Deleted), which you can view by clicking the Preview option. If you like the newer version better than the old one (which can’t be previewed anymore), you’ll have to (Validate and) Commit to

13-1-2015 28


overwrite the old version with the new one. Yes (old) will change to Yes.

– If the Ready status is empty it means No. You’ll have to (Vali-date these records, if not Valid already and) Commit them to make them Ready Yes.

Available actionsPossible actions to perform on the listed records can be started by clicking one of the options in the right window pane. Some only work on a single selected record, others on all records or on one or more se-lected records (Ctrl+click to select multiple records): Preview – Shows an HTML display of the selected record in your

default browser. This is how the record data will be presented on Europeana. A record needs to be Valid to be previewed.If two versions of a record are present in the set, the newer ver-sion will be shown.

Validate – Tries to validate the uploaded LIDO XML of selected records or all records, regardless of their status. If two versions of a record are present in the set, the newer ver-sion will be validated.

Delete – Deletes the selected records or all records, regardless of their status and readyness. Although record content will be deleted, a reference to the record will remain present, with a Deleted flag attached to it. Record data which has already been pushed to the aggregator won’t be deleted from the aggregator.If two versions of a record are present in the set, both versions will be deleted.

Commit – Commits all Valid records which are not ready yet, to make them Ready Yes. If certain records weren’t validated yet, Commit tries to validate those first. And if the aggregator requires the pushed data to be formatted as EDM, Commit will also trans-form the LIDO XML to EDM XML (as set up in your ECK configura-tion).The Commit option will be temporarily disabled if the Queue al-ready contains a commit action.Any Ready Yes (old) records will be overwritten by Valid new ver-sions of those records.

Data push – Pushes the data from all records with the Ready sta-tusses Yes and Yes (old) to the aggregator. You cannot undo this data push. Data push does not work with the queue: it has to wait for a reply from the server and you’ll be notified so. The progress of the push procedure will be displayed in a message.

Screen tabs

29 13-1-2015


The tabs available in the Europeana set manager are: Records – Shows the records uploaded from your institution. The

“subtabs” Show all, Pending (records not processed yet), Valid, In-valid, Ready and Deleted are filters. A blue filter is an active filter. Click the filter label to switch it between active and inactive. For example: to only show all valid records, activate the Valid filter and deactivate the others. Or, to only show all valid and invalid records, activate the Valid and Invalid filters and deactivate the others. Adlib will retain your filter choice.

Errors – Displays any validation errors from the web service if records didn’t pass validation. They may give a clue about what’s wrong, allowing you to fix it and upload the relevant records again.

History – Shows a part of the log of all actions processed on the server. Click the Get more option in the upper right corner if you’d like to see more log entries.

Messages – Shows sort of a log of errors, warnings and other in-formation. Errors and warnings will cause a yellow warning icon to appear in the tab label:Before you report any errors to our helpdesk, it’s good to know that not all possible errors are caused by Adlib or your configu-ration. After you click the Data Push option, for example, basically all non-Exception type errors will be caused by the ECK web ser-vice and you’ll have to contact your aggregator to report those er-rors.

The record set on the ECK web service

All records that you or your colleagues upload to the ECK will end up in a record set that divides the records into two groups: the ones that are Ready to be pushed to the aggregator because they have been “commited”, which means they have been validated and possibly converted to the EDM format (if that, instead of LIDO, would be the XML format required by the relevant aggregator) and the ones that are not ready because they haven’t been validated and/or commited yet. This division provides the condition for a unique, albeit confusing, characteristic allowing any record to be present in this record set twice, once with the Ready status and once without it: however, a du-plicate record will only be visibly listed in the record set once! The Status column will display the validation status of the newly uploaded version of a record if an older version of the record is present as well, while the Status column will display the validation status of the only available version of a record if no newer version is present. The Ready column on the other hand, will display the status Yes for a ready record that has no competition from a newer upload, while it will dis-play Yes (old) if there’s and “old” record version ready to be pushed 13-1-2015 30


to the aggregator while there’s also a newer, different or deleted ver-sion of the record in the set, which hasn’t been commited yet.If you never upload a record more than once, this situation will surely never occur; neither will it if you never mark the Don’t make the records ready (update only) option in the wizard when uploading data. Normally, you’ll upload a record only once and even if you acci-dentally upload the same record twice, it will overwrite the existing version of the record in the record set on the ECK web service (if vali-dation succeeds and the record is automatically commited, that is). The exception to the rule, causing two versions of a record to be present in the set, is when you upload a record more than once while having marked the Don’t make the records ready (update only) checkbox in the wizard, or when you upload a record more than once and find it doesn’t pass automatic validation the second time.

Having two versions of a record in the record set is no problem but you need to be aware of the consequences if it does occur. As men-tioned above, the way to tell if a record is present in the record set twice, even though it’s only listed once, is if the Ready status of that record reads Yes (old): When you push data, only data which has the Ready status Yes or

Yes (old) will be pushed. If you want a newly uploaded copy (or maybe an altered version) of an earlier uploaded Ready: Yes (old) record to overwrite it, you simply have to (Validate and then) Commit the selected record via these options in the Europeana set manager. The new version of the record will overwrite the old one and only one version of the record will remain in the record set.

If you delete one or more records from within the Europeana set manager, using the Delete option in the right window pane, both versions of double records will be deleted from the record set. On the other hand, if during upload of a second version of a record you had marked both the Delete existing records from the set and the Don’t make the records ready (update only) option, then you can tell from the Status: Deleted and Ready-ness Yes (old) of all pre-existing records which you haven’t uploaded again just now, that even though these records have now been flagged as deleted, the deletion hasn’t been commited because of the up-date only option. So here too, Yes (old) indicates that there still is an old version present in the record set, ready to be pushed or commited. If you Commit, all Ready: Yes (old) records flagged as Deleted will indeed be deleted this time.

Of the selected record, the Preview option in the right window pane of the Europeana set manager, displays the latest uploaded version, even if an older Ready version is present as well.

31 13-1-2015


If there’s only a single version of the record present in the record set, then of course this version will be used in the preview.

1.19.3 ConfigurationThe two Europeana upload buttons in the Adlib interface can only be-come active if a correctly configured europeana.xml file is present in either the Adlib executables folder which contains adlwin.exe or the folder in which the .pbk file of the currently active application resides. Further, if certain users need to be shielded from using the upload functionality, you can do so by adding the Upload records to Euro-peana method to all relevant data sources in your Adlib application structure, after which you set the appropriate access rights for it.

You can edit the europeana.xml file manually via a text editor or man-age these settings in Adlib Designer.

13-1-2015 32


The following ECK configuration settings are available:<eckUrl>ECK location (URL)

The URL of the Europeana Connection Kit (ECK) web service. This is currently hosted by Knowledge Integration Ltd (k-int.com) but anyone is free to download and install the ECK on their own server. Example: http://euinside.k-int.com/ECKCore2

<lidoXslt>LIDO stylesheet path

This is the path to the AdlibXML-to-LIDO tran-formation XSLT stylesheet. Example: F:\adlib\xslt\adlibXML2LIDO.xslt

<providerId>Provider

This is the provider ID. It's used by the ECK to tell the various providers apart from each other. From a technical perspective this value is used to construct the correct ECK URL.The setting is also used during the Persistent Identifier (PID) generation for LIDO record IDs. Every LIDO record needs a PID.Example: DSOM

<provider--Description>

This is the provider description. It's currently not being used.

<resourceMaster>Full image URL

<resourceThumbnail>Thumbnail image URL

These settings are used to resolve the image URLs in the final LIDO XML. The magic marker %data% will automatically be replaced by the image file name. There's a setting for the full image and one for the thumbnail. Examples using a wwwopac.ashx image server:<resourceMaster> <![CDATA[http://service.thecollectioncloud.com/wwwopacx/wwwopac.ashx ?command=getcontent&server=images& imageformat=jpg&value=DSOM%data%]]></resourceMaster>

<resourceThumbnail> <![CDATA[http://service.thecollectioncloud.com/wwwopacx/wwwopac.ashx ?command=getcontent&server=images& imageformat=jpg&width=100&height= 100&value=DSOM%data%]]></resourceThumbnail>

33 13-1-2015


<pushProviderId>Provider Identifier

<pushCollectionId>Collection Identifier

<pushUsername>Username

<pushPassword>Password

Push settings. See http://euinside.k-int.com/ECKCore2/SetManager/Help/edit for more in-formation. You would receive these settings from your aggregator. Because the ECK is not necessarily hosted by the aggregator, the pushProviderId can be different from the providerId. Example:

<pushProviderId>DSOM</pushProviderId><pushCollectionId>DSOM </pushCollectionId><pushUsername>fredrik</pushUsername><pushPassword>A789dIUU</pushPassword>

<pushSwordURL>SWORD server URL

The URL of the receiving SWORD server. SWORD is a protocol used by the ECK to transfer data to the aggregator. Example: http://natag-centos6.dev.seecr.nl/sword

<pushFormat>Data format

This can be either EDM or LIDO. Some aggre-gators prefer one format over the other. The ECK can send both formats to the receiving server.

13-1-2015 34

http://euinside.k-int.com/ECKCore2/SetManager/Help/edit

http://euinside.k-int.com/ECKCore2/SetManager/Help/edit


In Designer you can edit an existing europeana.xml file or create a new one. A new file can be made as follows:1. Open your Adlib system in the Application browser of Adlib De-

signer.2. Right-click the folder of the application from which you’d like to

have access to the ECK (xplus for example) and select New > Eu-ropeana Configuration File in the pop-up menu.

3. The new configuration file will be created and it will appear under-neath the Adlib .pbk file (or below the list of data sources if the ap-plication structure has been folded out).

4. Now you can enter all settings without having to work with the XML file. For more information about these settings, see the de-scription of the ECK configuration settings in the table above.

35 13-1-2015


5. Click Apply to store the changes. If you leave this settings tab without clicking Apply, Designer will still ask if you’d like to save your changes.

An earlier created europeana.xml file present in the application folder can be opened here as well, to edit the existing settings.Do copy the new or edited europeana.xml file to the folders of the de-sired other applications or move it to your Adlib \executables folder (if you’d rather manage the one copy) so that Adlib can make use of it. When Adlib looks for a europeana.xml file, it will do so in the folder of the active application first and only when it can’t find the file in there it will search the \executables folder.

1.20 Forcing identical terms in different domains

Previously, when you used Adlib Designer to import an existing term into a linked field with a fixed domain other than any domain already associated with the term registered in its authority database, the new domain would automatically be added to the existing term record. This is not always what you want though. Sometimes you would like to have the option to force a new linked term record for the identical 13-1-2015 36


term* and have the new domain associated with the new term record only. For instance, suppose you have an existing authority record for the term “bank” with the associated domain “furniture”. Now, if you were to import or enter the term “bank” in a linked field with the fixed domain “financial institution”, you would surely want to create a new linked “bank” record with the “financial institution” domain, instead of linking to the existing “bank” record associated with two different do-mains.This option has now become available in Adlib Designer.In Adlib Designer you’ll find the new Always create new domain records option on the Options tab in the Import job editor. Mark this checkbox to make sure that whenever an existing term is imported into a linked field with a domain different from the domain(s) for the already present term record, a new linked record will be created for that term, with the new associated domain. For an existing term with-out domain, the imported term will also be stored in a new record.Note that the ability to create new records also depends on the Forc-ing always allowed and Process links options on the same tab.* Duplicate terms in authority databases like the Thesaurus or Persons and institutions are only allowed if the indexes on the relevant fields can index non-unique keys as well. Typically this is the case when the internal links in these databases in your application are linked on ref-erence (record number), not on value (although indexes on reference-linked internal links may still have been set to unique). By default, in-ternal links on reference have only been implemented in our model ap-plications 4.2 and higher. Further, the new option to have duplicate term records created, is offered regardless of whether indexes are in-deed non-unique: if they are unique, regular error messages will in-form you that the entered or imported term has to be unique. (Ref.no: 6051)

1.21 External translation of application textsThe Translations manager of Adlib Designer allows you to view, edit and/or translate all interface texts of your Adlib system in one over-view (except for the Help files). The data in your database cannot be accessed this way. The files that can be opened in this tool are appli-cation structure files (.pbk), database structures (.inf), screen files (.fmt) and system text files (.txt). From these files, the texts you can edit and/or translate are message texts, button and screen field/box labels, enumeration texts, method (access point) texts, data source list texts, screen titles, application titles, and field names. All these texts can be edited or translated into as many languages as you wish to make available to users. (See the Managing translations topic in the Designer Web Help for more information about this tool.)

37 13-1-2015

http://documentation.axiell.com/alm/en/index.html?ds_tmintroduction.html


In Adlib Designer 7.1.13323.1, new functionality has been added to this tool. The new functionality is accessible from the File menu in the Translations manager: Import from file and Export to file.

This functionality allows you to: export the currently loaded application texts in selected interface

languages to an XML file; import an earlier exported and edited XML file into the currently

loaded files and overwrite or insert one or more (newly) selected languages in the process.

The advantage here is that a single XML file containing all application texts to be edited or translated to a new interface language, can easily and safely be exchanged between your company and an external translator, because the translator no longer needs to have access to the application structure files. The translator can do his or her work by simply editing the XML file itself in a text editor. The resulting file can be sent back, after which you can import it into the actual application to update the relevant texts.Let’s use an example to clarify things: 1. In Designer, select the main Adlib folder of your test environment

to work in, using File > Change working folder.2. Open the Translations manager, from the menu or the toolbar. If

the window opens empty, load your application texts into it using File > Add application folder. If later on you want to export as many texts as possible to be translated, then mark all checkboxes in the Open folder with Adlib texts dialog.

13-1-2015 38


3. When texts have been loaded into the Translations manager, click File > Export to file to open the Export translations window. Select the languages of the application translations you wish to export (for the translator to translate) and include the language(s) into which a new translation must now be made. Let’s use Hebrew for example. (English will always be exported, whether you mark the checkbox or not, and is used to match new translations to the cor-rect Adlib objects when importing the edited XML file later on.) Ex-porting means that the application texts in the selected languages will be copied to a special XML file: as of yet, nothing will be changed in the original Adlib files from which the texts are ex-ported.Then click the … button behind the Export to file entry field, to se-lect a folder and enter a file name for the XML file to be generated.Click OK to start the export.

39 13-1-2015


4. Look up the XML file on your system and double-click it to open it. It will be structured like the example below. Note that because we’ve included the language still to be translated, empty XML tags for this language (Hebrew in this example) are present in the XML file, making it easy for the translator to insert the new texts.

<?xml version="1.0" encoding="utf-8"?><AdlibTranslations> … <text> <English>Access</English> <Dutch>Toegankelijkheid</Dutch> <Hebrew></Hebrew> <French>Restrictions d'accès</French> </text> <text> <English>Access conditions</English> <Dutch>Raadpleging</Dutch> <Hebrew></Hebrew> <French>Conditions d'accès</French> </text> <text> <English>access_category.notes</English> <Dutch>toegangscategorie.opmerkingen</Dutch>

13-1-2015 40


<Hebrew></Hebrew> <French>conditions_d_accès.notes</French> </text> <text> <English>Accession</English> <Dutch>Inschrijving</Dutch> <Hebrew></Hebrew> <French>Inscription</French> </text> <text> <English>Accession analysis</English> <Dutch>Inschrijvingsanalyse</Dutch> <Hebrew></Hebrew> <French>Analyse d'inscription</French> </text> …</AdlibTranslations>

5. After editing/translating the file in an appropriate text editor, the translator should return the file. (Note that the English texts must not be edited in any way.) For example:<?xml version="1.0" encoding="utf-8"?><AdlibTranslations> … <text> <English>Access</English> <Dutch>Toegankelijkheid</Dutch> <Hebrew>גישה</Hebrew> <French>Restrictions d'accès</French> </text> <text> <English>Access conditions</English> <Dutch>Raadpleging</Dutch> <Hebrew>תנאי גישה</Hebrew> <French>Conditions d'accès</French> </text> <text> <English>access_category.notes</English> <Dutch>toegangscategorie.opmerkingen</Dutch> <Hebrew> הערות.סיווג_גישה </Hebrew> <French>conditions_d_accès.notes</French> </text> <text> <English>Accession</English> <Dutch>Inschrijving</Dutch> <Hebrew>הצטרפות</Hebrew> <French>Inscription</French> </text> <text>

41 13-1-2015


<English>Accession analysis</English> <Dutch>Inschrijvingsanalyse</Dutch> <Hebrew>ניתוח הצטרפות</Hebrew> <French>Analyse d'inscription</French> </text> …</AdlibTranslations>

6. Open your application folder in Designer again and in the Transla-tions manager load all the application texts that you originally loaded for export. Only the actually loaded texts will be updated, by means of the match between the English translation in the loaded texts and the English translation in the imported file.

7. Click File > Import from file to open the Import translations win-dow.

Mark only the language(s) of the translation(s) with which you want to update your application files. The texts in the selected lan-guages will be overwritten by the relevant texts from the XML file; the other present translations in the application files will remain unchanged.Click OK to import the new translations.

8. In the Translations manager you can now check that the new translations have been added correctly.

13-1-2015 42


9. Remember to save all affected application files when you close De-signer.

1.22 Adapl data preprocessing for label printing When you print labels using the File > Print label option in Adlib, you print to printer-specific labels (using printer-specific templates, not Word templates) which may contain fixed texts, barcodes and field data from your Adlib records. From Adlib 7.2 it is possible as well to have a custom adapl preprocess any record data before a label is printed, similar to how you can use an adapl to preprocess data before printing to a Word template (although you never explicitly call the la-bel template nor set the label template as an output format). You could use this functionality to have more control over how names of persons or institutions will be printed on your labels, for instance by dynamically limiting the length of data to be printed or to rearrange the order of printed details depending on what data is actually present in the record. All functionality of ADAPL is at your disposal. Adding an adapl reference to the label templateSuppose you have the following Zebra printer label template to print an address:CT~~CD,~CC^~CT~^FX%title:Address label 12pt%^FS^XA~TA-5274310~JSN^LT10^MN^MTD^PON^PMN^LH0,0^JMA^PR268447781,268447781~SD12^JUS^LRN^CI0^XZ^XA^MMC^PW812^LL0529

43 13-1-2015


^LS0^FT63,413Â0N,34,28^FH\^FD%field:postal_addr_street%.^FS^FT63,374Â0N,34,33^FH\^FDt.a.v. %field:salutation% %field:initials% %field:last_name%^FS^FT63,334Â0N,34,31^FH\^FD%field:name%^FS^FT63,453Â0N,34,33^FH\^FD%field:postal_addr_postcode% %field:postal_addr_place%^FS^FT63,492Â0N,34,33^FH\^FD%field:postal_addr_country%^FS^PQ1,1,1,Y^XZ

Now if you’d like to have some adapl you wrote executed before each label is printed, you’ll have to include a reference to it in the template. You can do that in two ways: You can add a line like the following anywhere in the template (al-

though inserted as the third line would be nice here): ^FX%adapl:..\\adapls\\myadapl.bin%^FS

Or insert the part between ^FX and ^FS in the already present comments section, like so: ^FX%title:Address label 12pt%%adapl:..\\adapls\\myadapl.bin%^FS

Do of course change the name of the adapl to the name of your own adapl and note that the path must be relative to the Adlib application folder containing the adlib.pbk file. Also observe that every backslash in the path must be escaped by doubling it.Save your edited label template and restart Adlib when you are ready to test your work.Note that if for printing the adapl cannot be found, an error message will be displayed and no labels will be printed. Writing a preprocessing adapl for label printingLet’s look at an example adapl to get you started. Assume the name field included in the template above contains person names in the for-mat ‘surname, first name’, and you would like to reverse this to ‘first name surname’ using an adapl. You could write the following very sim-ple adapl to handle this:* this adapl reverses 'surname, first name'* to 'first name surname'.

%1 = name$(%1)

end

Please note the following: In this particular example the name field has field tag %1. Your own

application could have different field names and tags. The ADAPL name$ function reverses a name if a comma appears in

it. In this case it takes the value from tag %1, reverses it and tem-porarily stores it back in the tag. The reversed value is not stored

13-1-2015 44


in the database record, it is just present in memory for the mo-ment.

This adapl will be executed for every marked record in your selec-tion, so when the adapls runs it has direct access to all field tags in the currently processed record (without the need to use FACS).

Even though the adapl changes the contents of a field tag while the label template contains field names, Adlib will match the tag to the proper field name before printing, so when the name field is printed, the altered contents of tag %1 will actually be printed.

In the label template you can use field tags instead of the English field names if you find that to be more clear, but you can’t use tags starting with a percent character. So in this example you would not be able to replace %field:name% by %field:%1%, for ex-ample, but you could replace %field:postal_addr_postcode% by %field:pc%, for example, if pc were the tag of the postal_addr_postcode field.

You can use temporary tags in your adapl and template. Suppose tag xx does not appear in your database, then in your adapl you could fill this temporary tag with any value you like, include the tag in the template like you would with a normal field name or tag and the value will be printed. For example, to fill tag xx with to-day’s date, add the following line to your adapl: xx = date$(8)Don’t forget to recompile your adapl and to actually include the tag in your label template too to get it printed.This temporary tag won’t be stored in your records.Further note that it is good practice to define temporary tags in the data dictionary of the relevant database, even though you won’t be storing anything in those tags permanently. The reason is that when you decide at a later time to add some new fields to your database, you won’t accidentally introduce tags that are al-ready in use as temporary tags in adapls.

To learn more about creating printer-specific label templates, see chapter 15.11 in the Adlib User Guide. ADAPL programming, on the other hand, is explained in detail in the Designer web Help.

45 13-1-2015

http://documentation.axiell.com/alm/en/index.html?ds_adaprogrammingintro.html


1.23 ADAPL function for locking fields

Matching the Adlib Lock field for editing function (see chapter 12.10 in the Adlib User Guide), 7.2 offers the lockfield (tag, occ, lan-guage) function in the ADAPL programming language, in which tag must be the data dictionary field tag of the field to be locked, occ the occurrence number of the field occurrence (1 or higher) to be locked, and language should be provided in the form of an IETF language code like 'nl-NL' for Dutch or 'en-GB' for British English (also see the “Us-ing Language Identifiers (RFC 3066)” document which can be found on the internet).Result = LOCKFIELD(tag, occ, language)

Argumentsresult, occ: integertag, language: text All lockfield() arguments are mandatory. If the relevant field is not multilingual or if it is a multilingual linked field or you want to lock all languages of a non-linked multilingual field at once, then use the string '0' (a zero between single quotes) instead of a language code.The function returns an integer error code: 0 if successful or a different value if an error has occurred.An example of an application is when you’d like to import data from a previous and/or frozen system, data which should be protected from editing after the import: the new function allows you to lock the rele-vant field occurrences during the import.The functionality to lock fields is only available for Adlib SQL and Oracle databases. (Ref.no: 6443)

1.24 After-read adapl option for import jobsBesides the regular import adapl setting on the Options tab of an im-port job in Designer 7.2.14286.3 and higher, you can also set an adapl which will be executed a little before that, namely before any update process will be started, but still after reading the record from the ex-change file and the mapping of the source fields to the target fields. To this end, the old Adapl procedure option has been renamed to Storage adapl (which will only be executed just before storage of the target record) while the new After read adapl option has been added. Both settings are optional and in both cases it concerns custom adapls which have been written especially for your import job.13-1-2015 46


So the after-read adapl will be executed before any update process. This means that if you have set an Update tag for the import job, this adapl will be executed before the import procedure uses the update tag to search for an existing target record to update. You can use this fact particularly to preprocess the value which will end up in that up-date tag, an object number for instance. This may be necessary if the relevant data (object numbers in this example) in the exchange file has a different form than that data in the target records. Sometimes the source data may contain field data from which object numbers have to be extracted first, because there’s other data in the field too, or it is necessary to put object numbers together from data from multi-ple fields in the exchange file before they match object numbers in the existing target records. You can use the after-read adapl to actually do that processing. This adapl can in principle be programmed in the same way as the Storage adapl for an import job.The after-read adapl will be executed with execution code 27, that is to say: &1=27. You can request such an execution code in the adapl it-self if you wish to use the adapl for multiple goals and you want to have one piece of code executed just after reading the exchange

47 13-1-2015


record and another piece of code before storage. That way you’ll only have to write a single adapl which can be set in both options.

1.25 New reserved ADAPL variable &6[7]The new ADAPL reserved variable &6[7] will contain the English name of the data source the user is currently working in. The name and its exact spelling will be obtained from the application definition file (.pbk) of the currently run application. That means &6[7] cannot be used in stand-alone adapls or in Step 1 of the Search wizard: in the first case there will be no current .pbk while in the second case the user will not have selected a data source yet.Note that all databases and datasets listed in Step 1 of the Search wiz-ard are called data sources. Data source names have been set in the .pbk while database and dataset names have been set in their own database definition files (.inf). (Ref.no: 6509)

1.26 Adlib startup option for data languageTo have your multilingual Adlib application always start up in a preset data language, 7.2 allows you to use the –d <data language> com-mand-line option. For example, insert –d en-GB behind the path to adl-win.exe in the Target of your Adlib shortcut to have the application al-ways start up in the English data language. For example:

F:\Adlib\executables\adlwin.exe –d en-GB

13-1-2015 48

2 Other improvementsIn 7.2 the following functionality has been improved:

2.1 Display1. Read-only access rights on the \data folder caused Adlib to

ignore application access rights. When read-only access rights were set in Windows Explorer on the Adlib \data folder, then Adlib ignored any access rights specified in the application and automat-ically applied read-only rights to all fields in the databases. This was wrong, because application-defined access rights can be more restrictive than read-only. (Ref.no: 3314)

2. Only the first 79 characters of a screen field label were dis-played on screen. When you created a screen field label that was longer than 79 characters only the first 79 characters were displayed on screen, even though the Screen editor in Designer doesn’t limit the length of the label. (Ref.no: 6119)

3. Scrolling through a large number of records (over 70000) was not possible. Scrolling on the brief display through a large number of records was not possible. The scroll bar would jump back to the beginning. (Ref.no: 6273)

4. The Derive button didn’t show the drop-down menu when it had been added to the Quick access toolbar. When the De-rive button was added to the Quick access toolbar, the drop-down menu containing the derive options didn’t appear when the button was clicked. It was impossible to derive a record using this button. (Ref.no: 6278)

5. After closing a zoom screen, sometimes not the original record was shown but the one that was linked as 'part of'. After opening a Parts record B from record A (by clicking the Parts field on the Number | Relations tab in an object record) and subse-quently opening a zoom screen by clicking the Collection field on the Identification tab and then closing it, you didn’t return to record B (from which you opened the zoom screen) but to record A (the part-of record of record B). (Ref.no: 6288)

6. Several buttons in the ribbon were displayed as if they were active but didn't actually work when the Pointer files window had been opened. Several buttons in the Adlib menus weren’t greyed out after you had opened the Pointer files window, and other buttons were active but didn’t do anything anymore. In the File menu, the Import, Export and Images buttons weren’t greyed out; in the Start menu, the Restart, New, Advanced search,

49 13-1-2015

QBF and Derive buttons no longer worked although they were dis-played as being active; and also in the Start menu the Pointer files button should have been greyed out. (Ref.no: 5920)

7. The Hierarchy browser showed the wrong data when using a zoom screen. When you had opened a record and displayed the Hierarchy browser, clicking an underlined term to open its record in a zoom screen and then clicking its broader term in the zoom screen made the Hierarchy browser change its content to that of the linked database, instead of persisting in displaying the hierarchical contents of the primary database. (Ref.no: 4891)

8. The status bar sometimes stated: 1 record flagged, al-though no record was marked. In some circumstances, the sta-tus bar displayed the message: 1 record flagged, although no record had been marked. You could even use the Write set func-tion, which resulted in a pointer file with zero hits though. If you actually marked individual records, the status message wouldn't be updated. (Ref.no: 6085)

9. Opening a zoom screen for a term linked on value while the term record didn’t exist, yielded two error messages. When a linked field was linked on value (not on link reference) and this field contained a value for which no linked record was available, then when you clicked this term in the record in display mode to open a zoom screen, two error messages were generated instead of just one. (Ref.no: 6088)

10. The $role constant for screen conditions only contained the first role assigned to a user. A user can have more than one role, but the $role constant for screen conditions only contained the first assigned role, so that a screen condition would not be evaluated correctly if it had been made for any user role but the first. (Ref.no: 6448)

11. A second zoom screen hid behind the first. When in display mode you opened a zoom screen to a linked record and in that zoom screen you clicked another linked term to open a second zoom screen, then the second zoom screen was opened behind the first. (Ref.no: 5698)

12. In RTL mode the record navigation buttons were swapped while their functionality remained the same. In right-to-left entry mode the arrow buttons to navigate to the first, previous, next or last record in the search result were swapped but the func-tionality behind each button remained the same. However, RTL mode users associatie “forward” with an arrow pointing left and “backward” with an arrow pointing to the right, so this fix restores the normal arrangement of these buttons in RTL mode but swaps their functionality. (Ref.no: 6399)

50 13-1-2015


13. Hebrew field name wasn’t correctly displayed in Edit data for multilingual field… window caption. If you started a 2.0.6 (or comparable) Adlib application in RTL mode with the interface language set to Hebrew and in a multilingual Title field you opened the Edit data for mulilingual field… window, then the Hebrew translation of the title field name in the caption of this window was displayed incorrectly. (Ref.no: 6340)

14. A language switch sometimes caused interface texts to be shortened. If you switched interface languages in the advanced search system or in a Query by form and went back to the Search wizard, you would find that names of databases and access points were displayed shortened (cut off after a few letters). (Ref.no: 4480)

15. No text underneath last row of images in Thumbnails brief display. When you scrolled to the bottom of a large search result on the Thumbnails tab of a brief display, the bottom row displayed thumbnails but no accompanying text underneath it. Without a thumbnail for a record it seemed the record wasn’t even there. (Ref.no: 4835)

16. Opening a zoom screen from another zoom screen opened it behind the first zoom screen. When you had opened a first zoom screen and clicked an underlined value in that zoom screen, then the second zoom screen opened unnoticeably behind the first one. You had to move the first zoom screen to see the second one. (Ref.no: 6477)

17. A field suppress condition like C1 = 2A didn't work because one of the tags started with a digit. In field suppress condi-tions, tags starting with a number were not recognized as tags but instead were interpreted as text. (Ref.no: 6621)

18. Thumbnails with diacritics retrieved via wwwopac.ashx weren’t always displayed. Thumbnail images with diacritical characters in their file names were not displayed on the Thumb-nails and Filmstrip tabs of a search result in Adlib, if those thumb-nails were retrieved via wwwopac.ashx. (Ref.no: 6176)

2.2 Searching19. Using a QBF in a SQL database and searching on a non-pre-

ferred term resulted in no records found. Using a Query by form in a SQL database and searching on a non-preferred term re-sulted in no records found because no preferred-term substitution was applied. (Ref.no: 5348)

20. Searching a CBF database on priref returned Record has just been deleted for every record. Searching a CBF database

51 13-1-2015


on record number displayed an (incorrect) Record has just been deleted messsage for every record in the search result that you double-clicked. (Ref.no: 5901)

21. Searching with a QBF used the broader term of the entered value and returned all narrower terms of that term. Search-ing with a Query by form used the broader term of the entered value and returned all narrower terms of that term. With the fix, you now search on the entered term, but on any nar-rower terms of the entered term as well. (Ref.no: 6225)

22. Date range search results weren’t always correct. Records with various dates that should have been returned in the search result, weren’t, and vice versa. (Ref.no: 6258)

23. The Use relations checkbox wasn’t present for alpha-nu-meric access points. When the index for an access point was of the alpha-numeric type, the Use relations checkbox in Step 3 of the Search wizard (applies only to SQL databases) wasn’t available when you searched on this access point. (Ref.no: 6224)

24. Searching an article on source title returned an error 121 on parent-child relation when the parent record's title started with the same word as the source title of the arti-cle. When an article was linked to a serial using the source title link and also linked to a book in a parent-child relation, while the title of both the book and the serial started with the same word, then when you searched the Articles dataset on that particular word in the source title, Adlib would return an error 121 on the parent-child relation. (Ref.no: 6316)

25. Displaying the term list in the Find data for the field win-dow for the first time, took a while. When you pressed Shift+F4 in the a linked field for the first time after starting Adlib, it took a while before the Find data for the field window was filled with the term list. (Ref.no: 6289)

26. Truncated searching with a QBF did not retrieve all rele-vant records. Truncated searching with a Query by form on a partial word did not retrieve all relevant records. The behaviour was unpredictable. (Ref.no: 6507)

27. No non-preferred term substitution in SQL. When you searched on a non-preferred term in a SQL database, using the ad-vanced search language in Adlib, then no records would be found because the non-preferred term would not have been substituted by the preferred term. (Ref.no: 6360)

28. An advanced search with the “<” operator returned no re-sults. When you executed the advanced search statement %0 <

13-1-2015 52


100 for example, while records with record numbers smaller than 100 were present, no records would be found. (Ref.no: 6516)

29. Searching without relations sometimes generated a SQL error. In the Search wizard, when you turned off the Use relations option after doing the same search with relations, you would get a SQL error. (Ref.no: 6517)

30. A field value starting with a space character couldn’t be found using a term index, although it was properly in-dexed. When a field value started with a space, e.g. " 1" and the field had a term index, then that term was correctly indexed, in-cluding the space, but when you searched on this term (with or without space) via the Search wizard or Advanced search, then Adlib would return “No records found”. The bug only appeared in Adlib SQL databases. (Ref.no: 6539)

31. A truncated search combined with another search through WHEN in the advanced search, returned a SQL query error. When you executed an advanced search statement like for exam-ple: location.history = "room 1A*" when location.histo-ry.date.end = "2014-07-01", in which one value was truncated and the Boolean WHEN operator was being used, then Adlib would return a SQL query error. (Ref.no: 6579)

32. Truncated narrower and generic searches returned no re-sults. If an advanced truncated search e.g. object_name = *term* returned results, then searching on object_name nar-rower *term* or object_name generic *term* could give no re-sults at all. (Ref.no: 6424)

33. An empty search while using relations could result in a SQL query time-out. When you have marked the Use relations check-box in the Search wizard and you search on an empty value, it may take a while for the search to finish. In previous versions, this could result in a SQL query time-out. (Ref.no: 6601)

2.3 Editing34. The favorites list could not be used in a zoom screen. The

right-click list of favorite values for a field could only be used in the primary database, not in a zoom screen to a linked database. (Re-f.no: 4972)

35. The Hierarchy browser displayed its content twice when navigating through the hierarchy while the record was in edit mode. When you had opened a record in edit mode, opened the Hierarchy browser and opened another record by clicking it in the hierarchy, then the hierarchy was suddenly displayed twice. (Ref.no: 5316)

53 13-1-2015


36. Adding a second occurrence of an HTML field, generated an error 1011. When you added a second occurrence of an HTML field (if present in your application), an error 1011 was generated. (Ref.no: 6168)

37. After creating a new linked term, the term was not se-lected in the Find data for the field window. After you had opened the Find data for the field window for a linked field and created a linked record for some new term from within that win-dow and then closed the zoom screen for the new term, then the new term was not automatically selected in the Find data for the field window. (Ref.no: 6175)

38. Replace in records using Match substrings also replaced text that should not have been changed. When, for example, you wanted to replace the prefix of a number of locations using the search-and-replace with the Match substrings option selected, then the part of the field contents that should not have been changed was still changed in an unpredictable way. (Ref.no: 6240)

39. In an HTML field there was no pop-up menu for copying, cutting or pasting text. When you copied some text from a website or text file and right-clicked an HTML field in your applica-tion (if present), no pop-up menu appeared to offer you the possi-bility to paste the copied text. Instead you could use the keyboard shortcut Ctrl+V though. (Ref.no: 6222)

40. A field on a zoom screen was not editable when its tag was also used as a context field in the primary database. A field on a zoom screen was not editable for certain users without the admin role, when its tag was also used as a context field (for dis-playing an internal link hierarchy) in the primary database. (Re-f.no: 6265)

41. Error 1011 when using Add occurrence below option in an empty linked field. When the cursor was located in an empty linked field and you clicked the Add occurrence below option, an error 1011 was generated. (Ref.no: 6328)

42. For some linked fields you had to press Enter twice in the Find data for the field window to force a new term. When no link screen had been specified for a linked field, you had to press Enter twice whenever the Find data for the field window opened to allow you to force the new term, while for linked fields that do have a link screen you only need to press Enter once. (Ref.no: 6357)

43. Missing error message when a non-unique key was used while the concerning index had been set to unique. When in a Library application not only the copyno (e0) but also the shelf-mar (ey) index had been set to Unique keys only then no error

13-1-2015 54


message appeared when a non-unique key was used in the Shelf mark field. The copy record and the copy occurrence in the Docu-ment database were (correctly) not saved, but no message was presented to inform the user. (Ref.no: 6373)

44. Deleted data in the Notes field that is part of a linked field group, was shown again when a new occurrence was added. When you deleted data from the Notes field on the Copies and shelf marks tab (document database, tag en, part of the Copies field group), that data was shown again when you added a new occurrence of that field group. (Ref.no: 4850)

45. Content of some fields was missing after deriving a record from one dataset to another dataset. The contents of at least two fields (di and UR in collect.inf) were missing after deriving a record from one dataset to another dataset of the collect data-base. (Ref.no: 6306)

46. Inserting the letter “á” using Ctrl+Alt+a deleted all text al-ready entered in the field. When you entered text in a field and at some point you pressed Ctrl+Alt+a to enter the letter á, the letter would indeed be entered but the other text would be deleted from the field. (Ref.no: 5514)

47. Pasting multiple field group items from the Adlib clipboard rearranged the sorting order of the field groups. When you copied the contents of individual fields (Ctrl+D) from repeated field groups and pasted those in a new record all at once (Ctrl+J) then the sorting order of the pasted field groups was rearranged. (Ref.no: 5147)

48. Read-only conditions for screen fields using $role didn’t work. When access to a screen field was limited to read-only us-ing the $role constant, the field would still be editable. (Ref.no: 6504)

49. When updating an existing record through deriving, the status bar reported New record. When updating an existing record through deriving, the status bar displayed the notification New record instead of the existing record number. After saving the updated record, the correct record number was displayed again. (Ref.no: 4795)

50. Copying all fields and pasting them in a new record re-sulted in duplication of fields. When you used the Copy all fields function in one record and subsequently opened a new record and used Paste all fields, then some fields were pasted twice so that duplicate occurrences were created. (Ref.no: 6349)

51. It was not possible to use Alt Gr in richt-text fields. It was not possible to use the right Alt key (Alt Gr on some keyboards)

55 13-1-2015


to enter characters like € in richt-text fields. (Alt Gr+5 normally enters the euro sign.) (Ref.no: 5343)

52. IPTC image metadata sometimes not imported. If you cre-ated a new Visual documentation record for an image file contain-ing IPTC metadata that had been edited in Windows Explorer, then the IPTC metadata was not imported when you created the link to the image file. (Ref.no: 6514)

53. Leaving a tab with an HTML field for the second time, caused Adlib to freeze. When you had opened a record in edit mode, put the cursor in an HTML field (e.g. on the Accompanying texts tab of an object record), subsequently opened another tab, went back to the tab with the HTML field and again opened an-other tab, then Adlib would freeze. (Ref.no: 6555)

54. A new linked term needed to be forced twice. When you had entered a non-existing term in a linked field and forced the new linked record through the Find data for the field window, then on saving the main record while the cursor was still in the linked field, the Find data for the field window opened again, requiring you to force the new linked record once more. (Ref.no: 6556)

55. The Copy all fields function copied non-exchangeable fields as well. When you used the Copy all fields button, all fields of the record were copied to the clipboard, including fields for which the Exchangeable option in Designer had been deselected. (Ref.no: 6559)

56. The default link screen was shown if multiple preferred terms were found during a search-and-replace. When you performed a search-and-replace in a linked field and the new value appeared in the linked database more than once as a preferred term, then the More than one preferred term found… window opened as expected, but the displayed field columns were those of the (implicit) default link screen, not those of the link screen speci-fied for the linked field. (Ref.no: 6569)

57. On deriving, searched title words ended up in the new record instead of the real title. When you derived a record, the words you had entered in the title field in the search form were copied to the new record, instead of the actual title from the origi-nal record. (Ref.no: 6575)

58. Pasting field group occurrences could change their sorting order. The order in which copied fields from a repeated field group were pasted into the target field group was not related to their original order: the new field group occurrences were pasted underneath any existing ones correctly (coherently) but usually not in their original order. (Ref.no: 6589)

13-1-2015 56


59. Modifications in Copy details field occurrence sometimes lost. After modifying one of the existing field occurrences of the Copy details field group of a library material, e.g. the Notes field, and then adding a new occurrence of that field group, the modifi-cations to the existing occurrence were overwritten by data from the relevant linked copy record. (Ref.no: 6223)

60. Unintended deletion of thesaurus terms from object records. If you deleted an empty occurrence from the term.type field of a thesaurus term, the term itself would (after your confir-mation) be removed from any object records. (Ref.no: 6229)

61. Drop-down lists for linked fields also showed non-preferred terms. The drop-down lists for linked fields (that were set up to display the available terms in a drop-down list instead of in the Find data for the field window), also contained non-preferred terms. There also was no way to distinguish the preferred from the non-preferred terms, even though after selecting a non-preferred term it was substituted automatically by its preferred term. Due to the fix, non-preferred terms will no longer show up in these drop-down lists. (Ref.no: 6256)

62. Message asking for confirmation to add term to empty do-main. Under Windows 7, when you clicked a drop-down list repre-senting the domain for the field next it, without actually selecting a domain, and then double-clicked the field next to it and selected a term from the Find data for the field window, Adlib would ask: Do you want to add term <term> to domain <>?, leaving the domain unspecified. (Ref.no: 6326)

63. After opening the Find data for the field window for a mul-tilingual linked field, sometimes the wrong key was se-lected. After opening the Find data for the field window for a mul-tilingual linked field, the search key was sometimes the first and sometimes the second term in the list, and still some other key was highlighted. (Ref.no: 6537)

64. The screen wasn't refreshed after an after-field adapl deleted an occurrence. If an after-field adapl was responsible for deleting certain occurrences of the relevant field, the screen wasn’t refreshed afterwards, causing the data to still be visible and valid. (Ref.no: 6630)

65. The focus on the edited record was lost after an error mes-sage. When you were editing a field, e.g. the ISBN field, and en-tered an incorrect value after which you clicked in another field, an appropriate error message appeared, but after clicking OK you could not continue typing in the field with the cursor: you first had to click the initial field to allow you to correct the mistake. (Ref.no: 4841)

57 13-1-2015


66. The Location entry field in the Change locations procedure was greyed out after a new selection of records was made. When you performed the Change object locations procedure re-peatedly, the Location entry field would become greyed out and inactive. It would become impossible to type or paste data into this field. The Browse button, next to the field, was still available though. (Ref.no: 5744)

67. When using the AAT as an external source it wasn’t possi-ble to page down to retrieve the next set of terms. When us-ing the AAT as an external thesaurus for a linked field it was not possible to page down to retrieve the next set of terms. By default only 10 terms are retrieved, even when more terms meet the search criterium. However, the Page up and Page down double-ar-row buttons weren’t active. (Ref.no: 6121)

68. The Find data for the field window didn’t always display the search key at the same place in the list. After opening the Find data for the field window on a multilingual linked field, the search key sometimes was the first and sometimes the second term in the list, depending on the current data language. (Ref.no: 6355)

69. Saving a record in a linked dataset with a (partially) upper-case name, while the field linked to the current database using "=", returned an error 32. If a dataset name contained capitals and the definition of the field linking to that dataset used “=” to link to the current database, then an error 32 was gener-ated on saving a record in the relevant database, showing the dataset name in lowercase letters. (Ref.no: 6485)

70. With Word 2007, the Adlib spell checker would only pro-vide alternatives for misspelt words if Word was active. When you ran the spell checker in Adlib, while Word 2007 was in-stalled on your system, the spell checker would recognize misspelt words but would only suggest alternatives if Word was actually up and running. (Ref.no: 6655)

71. It wasn’t possible to use the Save as Media Viewer function for file types other than images. When using the Save as func-tion for media files displayed in the Media Viewer, you could only save to image file formats. (Ref.no: 6084, 6634)

2.4 Printing72. When Boolean operations were used to generate a list of

search results, then only one record was printed when try-ing to print the entire list. If you performed a search which yielded multiple records and then printed this result from the brief display, all records in the result set would be printed as expected,

13-1-2015 58


but if you subsequently used a Boolean operator to expand or nar-row the search result, then only one record would be printed when trying to print the entire record list. (Ref.no: 6282)

73. In the Print wizard, a field’s screen text wasn’t used as the default label. When you used the Print wizard to print data from marked records, then on the Print wizard page where you select the fields to print, the Label column for selected fields was always empty, so you had to enter a readable field name there yourself.The fix makes sure that the appropriate label text from any Screen texts set for the relevant data dictionary field in Adlib Designer are entered in the Label column by default. You can still change the suggested label or enter a new label if no screen text was avail-able. (Ref.no: 6407)

74. Label printing didn’t use the sorting order of the brief dis-play. When you had marked several records in the brief display of a search result that you had sorted on a particular field and printed them to labels via a label printer, then the records were not printed in the order of the selected records in the brief display. (Ref.no: 6553)

75. Number of printed copies always 1. When you printed a se-lected record to a predefined output format and in the Print win-dow you had set the number of copies to print to 2, still only one copy would be printed. (Ref.no: 4807)

2.5 Pointer files76. The pointer files list Hits column wasn’t always updated.

After adding records from a pointer file to another existing pointer file, the number of hits for the destination pointer file was not up-dated in the pointer files list. With the fix, a message will now be shown, reporting the number of records added to/removed from a pointerfile. The dialog for adding/removing will not close automatically since one might want to add to/remove from other pointerfiles. (Ref.no:5677)

77. Creating a pointer file using a large query returned an er-ror 189. When you tried to write a set to a pointer file after exe-cuting a search statement of more than 4000 characters in the Ad-vanced search, an error 189 was generated.The fix consists of any search statement now being truncated at 4000 bytes. If the statement is bigger than 4000 bytes it is marked with /* to make the pointer file non-profilable (as other hand-picked sets can’t be updated either). (Ref.no: 6279)

78. Sorting in a pointer file was not applied when the pointer file was opened through the advanced search language. When a pointer file for an Adlib SQL database included the sort op-

59 13-1-2015


tion and you opened this pointer file by first opening the advanced search language and from there the Pointer files window, after which the selected pointer file had to be double-clicked as a set in the Advanced search window to open the resulting record set, then the sorting was not applied. (Ref.no: 4605)

2.6 Adloan79. Adloan didn’t store the list column width settings. By de-

fault, the columns on the three Adloan tabs are too narrow, but you can widen them by dragging the separator lines between the column headers. However, Adlib didn’t store the new column widths for the next time you opened Adloan, causing the columns to be too narrow again. (Ref.no: 6392)

80. When you made the copies list columns wider, vertical lines were created on the screen. When columns in the copies lists (issued copies for a borrower) were made wider, vertical lines (distortion) appeared on the screen. This happened when there was at least one issued copy in the list. (Ref.no: 6394)

81. The due date of an issued copy could not be changed prop-erly if the date was truncated in the Due date column. When having issued a book to a borrower you couldn’t properly change the Due date in the column itself if the column was set too narrow. (Ref.no: 4677)

2.7 Import and export82. Storage adapls were not executed when importing from

within Adlib. When you imported an XML file from within your Adlib application, the storage adapl associated with the current database was not executed. (Ref.no: 3360)

83. Image export in application with storage path didn’t work when the reproduction reference contained a subfolder. When you had marked some records with reproduction references containing a sub folder, while for the reproduction field a storage path had been set, then no image files were copied to the destina-tion folder when you exported images through File > Images. (Re-f.no: 6184, 6310)

84. An import into Collect forced redundant location records. An import of object records containing locations that weren’t yet present in the locations database were forced in there as many times as they were present in the exchange file, so this caused a lot of redundant location records. The bug was present in Adlib De-signer and import.exe. (Ref.no: 6253)

13-1-2015 60


85. Reindexing a priref index with the -fix option resulted in none of two duplicate records in the database being in-dexed. When you tried to fix a database (using the import.exe –fix option) in which a duplicate priref caused data corruption, then instead of indexing only the most recent record of the two du-plicate ones, neither one was indexed. (Ref.no: 3897)

86. On error 58, import jobs were aborted instead of skipping over the problematic records. When an import job encountered a record with a different owner than the person running the import procedure, an error 58 (no write access) would abort the entire im-port procedure instead of logging the error and just skipping the relevant record. (Ref.no: 6379)

87. Different import results from Designer and import.exe. Dur-ing import, Adlib Designer didn’t correctly insert edit information into records, while import.exe did. (Ref.no: 6639)

2.8 Designer88. The Data type field property incorrectly listed "European

date (dd-mm-yyyy)". The Data type field property in Designer in-correctly listed European date (dd-mm-yyyy) while the proper text to be displayed should have been European date (dd/mm/yyyy). Note that although the property label displayed the wrong text, the actual date field stored dates in the correct dd/mm/yyyy nota-tion already. (Ref.no: 3675, 4427)

89. It was not possible to add a new index from the context menu for another index. A new index could only be added from the right-click pop-up menu for the index list node, not from the pop-up menu for an individual, existing index. (Ref.no: 5854)

90. The click-once Adlib Designer showed only the default set-tings of the adcirc.pbk. When you opened an Adloan application definition file in Adlib Designer, it only showed the default settings and you could not change them. (Ref.no: 6246)

91. The Reindex all word indexes option did not create a new wordlist table in a SQL database. The Reindex all word indexes option did not create a new wordlist table in a SQL database. Since it is recommended that you delete the SQL wordlist table manually before reindexing all word indexes in a SQL database, a new wordlist table should be created automatically during this reindex-ing operation. (Ref.no: 6255)

92. Certain changes in an existing import job could not be saved immediately. After changing the Mapping in an existing import job, the Save button didn’t become active. Only after

61 13-1-2015


changing another setting could the import job still be saved. (Re-f.no: 6263)

93. The SQL database connection Test button did not check for the existence of the relevant table. The SQL database connec-tion Test button (at the bottom of the Database properties tab for a selected database definition) did not check for the existence of the relevant table: it only checked the connection to the SQL data-base. (Ref.no: 5641)

94. Changing the access rights for a field did not activate the Save button. When you selected any data dictionary field in a database structure and added a role and access rights on the Ac-cess rights properties tab, the Save button (to allow you to store the changes) would not be activated. (Ref.no: 6227)

95. Syntax error when compiling an adapl that contains an in-teger variable. When in Designer you wrote an adapl containing an integer variable declaration, compiling the adapl from within Designer failed due to a syntax error (Unknown token ‘integer’). (Ref.no: 6341)

96. Designer reported "Adlib Designer has stopped working" twice in a row after closing the program on Windows Ser-ver 2012. Designer reported "Adlib Designer has stopped work-ing" twice in a row after closing the program on Windows Server 2012. It didn't matter whether it was a local copy of Designer or if Designer was run from a network share. (Ref.no: 6483)

97. A field suppress condition like C1 = 2A didn't work because one of the tags started with a digit. In field suppress condi-tions, tags starting with a number were not recognized as tags but instead were interpreted as text. (Ref.no: 6621)

98. Different import results from Designer and import.exe. Dur-ing import, Adlib Designer didn’t correctly insert edit information into records, while import.exe did. (Ref.no: 6639)

2.9 ADAPL99. On compiling, the datdif function generated a syntax error.

Compiling an adapl containing the datdif function generated a syntax error. (Ref.no: 6001)

100. When adeval.exe was terminated by clicking on the close window button, the adeval process remained active. When you were running a stand-alone adapl, using adeval.exe, and you terminated adeval.exe by clicking on the close window button, then the adeval process remained active (as could be ob-served in the Windows Task Manager). (Ref.no: 6107)

13-1-2015 62


101. Syntax error when compiling an adapl that contained an integer variable. When in Designer you wrote an adapl contain-ing an integer variable declaration, compiling the adapl from within Designer failed due to a syntax error (Unknown token ‘inte-ger’). (Ref.no: 6341)

102. The adapl debugger only displayed two occurrences of &H, even though an unlimited number of occurrences was and is supported by adeval. When an adapl was run from the command line, using adeval with more than two arguments, then from the information displayed in the adapl debugger it seemed that only the first two arguments were placed in the &H variable. In actuality, all arguments were placed in the &H variable, but only the first two were shown in the adapl debugger. The fix ensures that now the first ten arguments will be displayed in the adapl de-bugger (even though an unlimited number of arguments was and is supported by adeval). (Ref.no: 6496)

103. The READ <FACS name> POINTER command made ade-val crash. When you ran an adapl containing a READ <FACS name> POINTER command, using adeval, adeval crashed on the READ command. (Ref.no: 6497)

104. The link in a non-multilingual field wasn’t resolved cor-rectly by an after-field adapl as soon as a data language was specified in the .pbk. When you specified a data language in the application structure and in the running application an after-field adapl was executed for a non-multilingual linked field, then the link in it could not be resolved correctly by the adapl anymore. (Ref.no: 6540)

105. A screen adapl was automatically executed on saving of the record, even when the screen had not been accessed. Even when a screen with which a screen adapl had been associ-ated, had never been opened while accessing the record, it was still executed when you saved the record. (Ref.no: 6545)

106. The INT function combined with VAL sometimes gave an incorrect outcome. The result of int(val(number1) / val(num-ber2)) was different from val(number1) / val(number2) if num-ber1 (a text variable) was 299.20 while number2 (also a text vari-abel) was 59.84, for example. (Ref.no: 6561)

107. The wordcreatedocument function always returned 0. The wordcreatedocument function always returned 0 (meaning: succesful), even when the template could not be found.With the fix, the function now returns a CONFIGURATION_ERROR when creation of the Word document fails. The details of the error also contain the name of the problematic template. Those details

63 13-1-2015


can be retrieved via error$(val(result)) if result contains the function result code. (Ref.no: 6618)

2.10 SDI.exe108. Sdi.exe updated pointer files with an incorrect database

name, causing errors in Internet Server. Search profiles cre-ated with Adlib Internet Server 3.1.2 (running on wwwopac.exe) were no longer accessible after sdi.exe had run, because sdi.exe updated pointer files with an incorrect database name. (Ref.no: 6009)

2.11 Registry109. The initial default data language setting could not be

made per machine. It is possible to set the default data lan-guage with which Adlib starts the first time a user opens the appli-cation. This can be done in the Windows registry per work station. Previously, this setting could only be made per CURRENT_USER in the registry, which was inconvenient if the default language had to be set for many users of that machine. To fix this, the default data language can now also be set underneath the LOCAL_MACHINE key. The latter will be checked first and only if no default data lan-guage has been set there, the CURRENT_USER will be checked. (If no default data language has been set in the registry, the first data language in the relevant drop-down list in the Adlib GUI will be the default data language the first time a user opens Adlib, while if both registry keys contain a default data language, the one for the current user will override the one for the local machine.) Please contact the Adlib Helpdesk for more information, if you con-sider applying this option. (Ref.no: 6403)

13-1-2015 64