2019-08-22: release Axiell Collections 1.6

Today we release the sixth update of Axiell Collections 1, offering the new functionality described below.

2019-08-15: "is between" searching on date, ISO date, integer and numeric indexes

The Standard search tab in the Search <data source> window now supports the is between and is not between operators for access points on date, ISO date, integer and numeric indexes. As soon as you select one of these operators, a second entry field is added behind the first, allowing you to search on a number range or date range within a single field. Note that the entered numbers or dates are included in the search, so if you were to search for record numbers between 100 and 200, then records with record numbers 100 and 200 are included in the search result. Similarly, if you were to search for record numbers not between 100 and 200, then records with record numbers 100 and 200 are excluded from the search result too.

ACIsBetweenSearching

2019-08-08: exporting all field occurrences to CSV

Of repeated fields, previously only the first occurrence could be exported to a CSV file. From Collections version 1.6 though, you can choose between exporting only the first occurrence and exporting all occurrences. Since CSV files have as many columns as there are exported fields, the occurrences of a repeated field are concatenated and separated by a field occurrence separator text of your choice, but still contained in the single field column.

All CSV export options can be found in the CSV settings dialog. First click the Export icon for a selection of records in the Result set view.

ACExportIcon

ACExportCSVsettings

Choose the Csv Format, select the fields to export, mark either the All, Marked or Current radio button and click the Settings button to open the CSV settings dialog. In it you'll find the following options:

Field separator - choose either a comma or semi-colon to separate the field columns in the CSV. For your choice you don't need to be concerned about commas or semi-colons in your data because data containing those punctuation characters will automatically be enclosed by double quotes. And Microsoft Excel supports both field separators, but only one of them will cause Excel to open the CSV correctly by default (each field in its own spreadsheet column): you'll have to test this since it differs per Windows installation. Otherwise it's a matter of preference which field separator you choose.
Occurrences - select either First occurrence or Merge occurrences. Merge occurrences concatenates all occurrences of a field and separates them with the Occurrence separator text. The setting applies to all exported fields so that exported data from repeated field groups remains consistent.
Occurrence separator text - enter a text (one or more characters) to separate any field occurrences. Preferably choose a text or character that is very unlikely to appear in the data itself. Any empty occurrences will be exported and separated by this text too.
Separators in field - even if you've set an Occurrence separator text that is very unlikely to appear in the data itself, you may be surprised by the opposite and therefor you also need to think about what should happen if the separator string does appear in the data and set the current option to either:
- Error (recommended setting), in which case the export generates an error message and doesn't produce any output;
- Ignore, in which case the export proceeds normally, but in any resulting concatenated data you can't be sure if a separator text is part of the data or separates field occurrences;
- Strip from field, in which case the export will strip the separator text from the exported data (leaving your records unharmed of course) so that the separator text can be used uniquely as occurrence separator, but the exported data will have been changed.

2019-08-08: deriving records from other data sources

Sometimes you'd like to move or copy records from one data source to another similar one, like from the External object catalogue to the Internal object catalogue or from Archives (accessions) to Archives (catalogue) for example. For this purpose, we now have the derive function. If set up for the current data source, the derive icon appears in the Result set context toolbar. The tooltip which appears when you hover the mouse cursor over the icon, will indicate what the exact function in this data source is: cut or copy one or more records.

ACDeriveIconHint

Click the icon to search for records to derive from the other data source. In the search result, simply mark the records to derive and click OK. Which data source you'll be searching, whether records will be moved or copied and which fields will be included, all depends on the particular setup of this function per data source.

2019-08-05: thumbnail and native barcode/QR code printing to Word templates

Previously, barcode printing to Word templates required a barcode font to be installed on the pc from which you started printing. With Collections 1.6 that is no longer necessary: in the field reference in the Word template itself you can now indicate which type of barcode you'd like to print and in which size. The format of a field reference for a barcode is as follows:

<<field_tag[occurrence].barcode_type|width=width_in_pixels|height=height_in_pixels>>

The following barcode and QR code types are supported:

code39
code93
code128
ean8
ean13
qrcode
upca

Note that EAN-8, EAN-13 and UPC-A contain strict rules. If the barcode doesn’t conform to these then the barcode won't be printed.
For a barcode you'll always need to provide a width and height, while for a QR code a single dimension will suffice. You'll have to experiment with the dimensions to find out if your longest barcode still fits on the label or page and can be read by your barcode scanner alright.

Examples:

<<ba[1].code39|width=270|height=77>>

<<Nn[1].code128|width=300|height=100>>

Thumbnail printing

The size of images printed to Word templates is usually restricted by the dimensions of the table cell which contains the image field reference. If it isn't in a table cell, the image will be printed in its original size. From Collections 1.6 though, you may restrict the printed image size by a width parameter in the field reference as well. (This is actually the only way to customize image size in labels because a label template consists of a large table which cannot contain nested tables.) Any height parameter is ignored so the aspect ratio remains intact (and you cannot just provide a height and no width). The format of a field reference for a size-limited image is as follows:

<<field_tag[occurrence].thumbnail|width=width_in_pixels>>

Example:

<<FN[1].thumbnail|width=270>>

Note that the image is still retrieved in its original size and is only resized during printing, so using the thumbnail parameter won't increase performance.