2018-09-24: release Axiell Collections 1.3

Today we release the third update of Axiell Collections 1, offering the bug fixes and new functionality described below.

2018-09-24: relevant bug fixes since release 1.2 (2018-07-26)

Short problem description

Saved searches in the Manage saved searches window couldn't be unsorted.

If an invalid date format was searched, Advanced search did not retain the failed search.

Inherited fields weren't displayed on each level.

ISO date fields defined as text fields on screen, didn't accept 3-digit and/or negative years. The fix ensures that in this case all dates in the format (-)(y)(y)(y)y(-mm)(-dd) are accepted.

Upload of documents or linking of images to object records was not possible any more.

The original file name of an uploaded document was not updated in the media record.

Export to Excel didn't work any more.

To an exhibition record you could only add a single object.

The Related records view didn't show some object-event relations.

Object records could remain locked after adding them to an exhibition.

Raw XML sent to a print service didn't contain data from linked fields and merged-in fields.

Printing to an XSLT stylesheet generated an error.

Metadata from the special metadata table wasn't shown.

After deleting a record it was still visible in the Record details view.

Inherited values couldn't be used in screen conditions.

When a search yielded no results, the Search <data source> window would close.

After using search-and-replace, the window couldn't be closed.

Some values were displayed multiple times in the Find data for the field window.

In the Result set, earlier filled write-once fields could still be put in edit mode.

Automatically numbered fields could still be edited in the Result set.

The dialog didn't close after linking an object record to a workflow.

In the record editor, numerical fields were treated as integer fields.

A linked term was not accepted unless you clicked it in the autocomplete drop-down.

The Result set wasn't refreshed after bulk-creating records.

Records with many relations couldn't be displayed.

Printing the Object ID (max. 6 images...) report generated an extension error.

In the Internal object catalogue, an error message Object reference not set... appeared when clicking on the Settings button to select detail screens.

Clicking the Details button in the Find data for the field window caused the browser to ask the user whether he or she wanted to leave the site.

A space in a screen file name could cause the Select button in the Find data for the field window to become non-responsive.

User-dependent screen file Read access rights were not applied.

Clicking on linked fields in the Result set bypassed any restrictive access rights and opened the zoom screen with the possibility to put it in edit mode.

The priref of records could not be exported to a csv file.

The access rights of merged-in fields were not checked when doing indirect advanced searches.

A Last operation: RepCnt on 6872. Language is required error was thrown when trying to save a Loans record.

New names were forced immediately without opening the Find data for the field window.

After moving a location to another location hierarchy, the location context field in object records wasn't updated.

2018-09-20: editing saved search properties

In the Manage saved searches dialog, the Edit saved search button has been removed. Instead, you can edit the editable properties of a saved search directly in the displayed properties (click the small arrow left of the saved search number to show its properties). On the General tab you can only edit the Title, while on the Rights tab you can edit the Owner and Access rights settings for this saved search. Click the Save button next to the properties to save your changes. This mechanism for editing and saving saved search properties can also be found on the Saved searches tab of the Search <data source> dialog.


2018-09-20: managing scheduled saved searches


A Schedule button has been added to the Manage saved searches dialog. It opens a dialog that allows you to set an SDI schedule for automatically rerunning the selected saved search at certain intervals and print or e-mail the result of the search. A requirement for this functionality to work is that your application manager has set up an SDI server.


SDI stands for Selective Dissemination of Information. This means that you can keep your customers or co-workers (library visitors or literature researchers for example) up to date with information that is relevant to them, a list of recent acquisitions maybe. In Collections, an SDI schedule must always be based on a saved search that can actually be rerun (a manually picked selection of records, stored as a saved search cannot be rerun).

An SDI schedule has the following properties, spead over three screen tabs:

Format - Enter the path to an adapl (without the .bin extension) or stylesheet (.xslt) to provide the layout for the output. The path must be relative to the folder which holds sdi.exe (the SDI server). For example: if sdi.exe is located in the Adlib \executables subfolder and a stylesheet is located in the Adlib \museum subfolder, then the path would be something comparable to ..\museum\mystylesheet.xslt. If the adapl or stylesheet is located in the same folder as sdi.exe, then you only need to provide the file name, without path. The Format option is mandatory.
Language - Select the language in which the search statement for the pointer file has been put together. For example: if you used English field names in the search statement, then you should set the language here to English as well, otherwise sdi.exe cannot find the fields later on.
Pruning - The search result of the rerun saved search can be filtered before it is sent out. Choose New records to only show records that have not been reported earlier, or report only new or modified records by selecting New or changed records. The option DM/DI changed does almost the same, but is application-dependant. You can also report the full search result by selecting No pruning. The Undefined option has no meaning, you have to choose one of the options below it.
Limit - Specify the maximum number of records the search result or the rerun saved search may contain. 0 means that there is no limit.
Subject - This field can be used to add a subject line to an e-mail.
Comment - Note possible comments about this SDI profile.
Mode - The search result can be sent to two different output systems. Select Email or Printer. Whether you print or e-mail, all records will be placed underneath each other. The adapl can make use of the normal reserved tags to print headers, footers and record separators.
Printer destination - Fill in nothing to use the default printer. If you want to use another, then provide the full path to it here.
Email format - Choose HTML if you’ve transformed the search result to an HTML page (by means of an XSLT stylesheet for example). The e-mail will then show the browser display of that page instead of the HTML code itself. In all other cases, choose Plain text.
Email addresses - Provide all e-mail addresses to which the result of the rerun saved search has to be sent regularly. Type an e-mail address in the left entry field en move it to the list on the right by clicking the > button. Repeat this for all e-mail addresses. You can remove an address from the list by selecting it and clicking the < button.
Frequency and Schedule - Times and dates when the user wants his or her saved search to be rerun. First choose a frequency, then fill in more specific data on the right in the entry fields of Schedule that become active (which ones become active depends on the set frequency). This way you can set the Hour for Daily, and also the day for Weekly and Monthly, and for Yearly: Hour, Day and Month.
Expiry date - Select a date after which you no longer want to rerun the saved search.
Suspended - As long as this option is marked, the SDI schedule will be inactive.
Last run - The date on which a saved search was rerun last. You cannot add or modify this date yourself.

2018-09-19: uploaded templates can be stored on the server for easy reuse

Axiell Collections 1.3.18262.10 and higher allow custom Word templates uploaded through the Output formats dialog to be stored on the server automatically. The stored template will then become available (initially under its file name) in the Output formats dialog too, so next time this Word template is needed for printing, you can pick it straight from the Output formats dialog and you won’t need to upload it again. This functionality is optional and is only active if it has been configured correctly. Then each time a template is uploaded, it will create an associated record in a new database, containing some metadata about the stored template.
Possibly, an Uploaded templates data source for this new database has been set up by your application administrator as well, to allow you to manage the list of uploaded templates as it appears in the Output formats dialog (change the visible titles, determine which users should have access to which uploaded templates, hide certain uploaded templates permanently). You will never create new records in this data source manually, only edit them.


An uploaded template record contains only seven fields, of which you can edit just three:

Stored template ID – the uploaded template will be saved in the designated storage path under a unique ID.
Original file name – the original file name of the uploaded template will be saved in this field.
Visible template name – initially, the original file name will be stored in this field too but you can change it to anything you like. This will be the visible title of the template in the Output formats dialog. It can only be entered in a single language.
Data source ID – the template can only be visible in the data source from which it was uploaded. The name of that data source will be converted to a unique ID and saved in this field.
User role/Access rights – the user or role who uploaded the template will automatically get Full access rights. This means two things: this user or role will have Full access rights to this record (so don’t change it to Write, Read or None) and the template will be visible to this user in the Output formats dialog of the relevant data source. If the Default access rights for the application have been set to None, then other users won’t have access to this record and won’t see the template in the Output formats dialog. You can add extra occurrences to this field group to specify access rights for other users/roles: Read, Write or Full access rights will show the template in the Output formats dialog, while Read access rights won’t allow other users to edit this record.
Category – this field is for possible future use, currently it has no function.


Once you delete a record, its associated template will no longer be visible in the Output formats dialog, but the template file itself won’t be removed from the designated storage folder.
Each time you upload a template with the same file name as an earlier uploaded template (which will happen when you are still perfecting your template), a new record will be created in the Uploaded templates data source and the template file will be stored under a unique name in the designated storage folder. It won’t overwrite the previously uploaded template with the same original file name.