Release Date: 8th October 2013



Download a PDF document containing these release notes and associated documents: pdfInternational English or pdfUS English.

Please see the latest version of the EMu Help for the most up to date version of this documentation.

New Features

Edit in a Single Language

Edit in a single language functionality allows users with a multi-lingual version of EMu to use the system in either a single language or all languages. Full functionality is provided regardless of the language(s) selected. A number of extensions have been added that provide a more flexible mechanism for displaying and altering data within a single language:

  • When the All Languages option is selected, users may now select the order in which languages are displayed. This allows users who are dominant in a particular language to display this language first with other languages following:

  • Users may now alter data while a single language is displayed. Any data entered into a field will only update the value of the language selected.

  • When displaying data in a single language and where a value does not exist in that language for a given field, the value of the first filled language may be displayed. The text is shown in a user selectable colour (grey by default) to indicate that the value is not associated with the current language. When the field is entered, the text is removed, allowing data to be input:

  • A number of data entry helpers always display values in all languages in the user defined order to assist data entry. For example, if a Lookup List is displayed, all languages are always shown so that users may select the correct entry based on context. This is particularly important where one term in a given language has multiple terms in another language:


A complete description of the support for editing in a single language can be found in the How to edit in a single language documentation.



Support of pop-up calendars

Date fields may now have a pop-up calendar associated with them. The calendar may be used to select a date or view the day on which a particular date falls. Users can step backward and forward a month at a time as well as select a specific month or year:


Please contact KE for information on how to make the pop-up calendar available for use.

Static groups display Summary Data

The grid containing the list of IRNs making up a Static group has been extended to include the Summary Data for each IRN. The grid now provides an easy way to see what records are part of the Static group:


Clear group command

A new command has been added to the Edit pull down menu allowing all the controls in a Group box to be cleared. The command is available while entering search terms and inserting or editing records. A keyboard shortcut (Shift+Ctrl+Del) has also been made available:


Autofill Lookup Lists

The EMu autofill feature that provides a mechanism to add values into a hierarchy where a unique combination is specified has been extended to function on single level Lookup Lists. The change means that when a value is entered into a Lookup List field via the keyboard, the value is replaced with the corresponding Lookup List value if a matching entry exists in the Lookup List module. For example, if a Lookup List contains the value IBM and a user enters ibm, the user's text (ibm) will be replaced with the Lookup List value (IBM). Institutions may use this feature to enforce consistent entry of values.

Scan multi-page documents

EMu now supports the scanning of multi-page documents where the connected scanner supports such functionality. Once the pages are scanned, a multi-page image format should be used to save the document (e.g. TIFF). If the selected image format does not support multi-pages, then only the first page is saved.

Scan from all modules

The ability to scan documents has been added to all EMu modules that allow multimedia to be displayed. The Multimedia pull down menu has two new commands:

  • Setup Scanner
  • Scan Image
Support for PDF images

Support has been added to EMu for the display of PDF images.

Please note that in order to enable this functionality in EMu it is necessary to install the open source tool GhostScript. Details are provided in the EMu 4.2 installation notes.


Issues Resolved

Issue Resolution
The splitting of date ranges may result in the current century being prepended to the closing value rather than the century of the opening value. For example, 1886-93 would result in 1886 and 2093 as the opening and closing values respectively. In most instances a closing value of 1893 is required.   The closing value of a date range now reflects the century of the opening value, rather than the current century.
The Multimedia and Supplementary_tab fields may not appear in the list of fields available for selection when creating a report. In order to add the fields it is necessary to add Reportable Registry entries for each of the fields.   The Registry entries are no longer required as the Multimedia and Supplementary_tab fields are now shown in the field list (permissions permitting).
The auditserver may not complete processing the current record when it is terminated. When it is restarted it may then process the same record again, possibly resulting in two entries in the Audit Trails module.   The auditserver now finishes processing the current record before shutting itself down.
Admin Tasks that have specified input types of either number, date or time do not have values entered validated. Hence it is possible to enter a badly formatted number, date or time value that is not detected until the server-side script checks its arguments.   Numeric, date and time values entered as input values in Admin Tasks are now checked when the field containing the value is exited. If the value is not valid, a suitable message is displayed and the value must be amended.
The emulutsrebuild server-side command does not load system based Lookup Lists when they are named on the command line. For example, emulutsrebuild -t 'System Yes' does not add the Lookup List entry for the System Yes Lookup List.   System based Lookup List entries are now loaded correctly when named on the command line.
When selecting a file to import into EMu the file selection dialogue box restricts the file extensions that may be chosen. The list of possible files is restricted to those matching *.csv, *.tab, *.txt and *.xml. In some cases an Import file may not match one of the listed extensions, forcing users to rename files.   The file selection dialogue box has been extended to allow All Files (*.*) to be selected. The change allows any file to be chosen. EMu parses the first part of the file to determine whether it contains XML or CSV based data.
When copying a large number of rows from a list of matching records onto the Windows clipboard, the operation may take a long time. In particular, if the data contains values from other modules the time taken may be substantial.   The time taken to copy records onto the Windows clipboard has been reduced dramatically where a large number of records is involved.
The Summary Data generated for the Accession Lots module contains only the name of the first person listed as the source of the object(s). In the case where multiple sources have been involved the Summary Data does not reflect this involvement. In this case the value displayed may be misleading.   The Summary Data for the Accession Lots module now lists all parties listed as a source of the object(s).
The file permissions set on the EMu server allow access to server-side files for users registered in the UNIX group emuadmin. In general, user emu is the only account that is part of the emuadmin group. If a system administrator chooses to add another user to the group, the user may be able to view information that is sensitive.   The EMu server-side permissions have been tightened so that only user emu may view files containing information that may be sensitive.
If a Catalogue object is attached to an Event where the object is already part of the event and the Exhibition Objects module is used by the Institution, then EMu will display a message indicating that the object is already part of the event. Once the message is acknowledged the same message may be displayed again and again. The only way to exit the messages is to close EMu.   The message indicating that the object is already part of the event is now displayed once only.
The header displayed at the top of each column in List mode may not display the text correctly if the text contains extended characters (that is characters with diacritics).   The header text is now displayed correctly for extended characters.
The data shown in the Shortcut grid for a given record may not display correctly. The issue only arises for users with Unicode based data where the data contains extended (or non-ASCII) characters.   Unicode data is now displayed correctly in the Shortcut grid.
The message box displayed asking for confirmation for a new entry to be added to a Lookup List may not display the new value correctly for Unicode based systems where the value contains extended (or non-ASCII) characters.   The correct text for the new value is now displayed for extended Unicode characters.
When a series of rows in List mode is copied to the Windows clipboard the data copied may not display correctly if pasted into Microsoft Excel. The issue only arises for Arabic characters.   Arabic characters now paste correctly into Microsoft Excel.
When a series of rows in List mode is copied to the Windows clipboard and then pasted into Microsoft Word any diacritic characters will not be displayed correctly. The issue only occurs for non-Unicode based clients. The issue does not occur if the Paste Special... command is used in Microsoft Word.   All diacritic text pasted into Microsoft Word now displays correctly.
The error message Cannot allocate memory may be displayed when copying a large number of rows from List mode onto the Windows clipboard. The issue only occurs where the number of rows is in the tens of thousands.   The error message no longer appears when copying a large number of rows onto the Windows clipboard.
An incorrect hint string is displayed when hovering over the Discard Record speed button. When a series of records is selected the Discard Current hint is displayed, rather than the Discard Selected Records hint.   The correct hint is now displayed when hovering over the Discard Record speed button.
If an object is removed from an event record by simply clearing the Summary Data of the object from the Objects gird, then the associated Exhibition Objects record is not deleted. If the object is deleted by right clicking on the object's Summary Data and selecting Delete..., then the Exhibition Objects record is deleted correctly.   The Exhibition Objects record is now deleted when the Summary Data of the associated record is cleared.
Multimedia records attached to the Exhibition Objects module are not displayed as thumbnails by default. The full version of the image is shown. The Multimedia tool bar can be used to switch to Thumbnail mode.   The Exhibition Objects module now displays multimedia thumbnails by default.
The command to insert the current date (Edit>Date>Current Date) may insert the date for the previous day. The incorrect date, while consistent, will only occur spasmodically.   The correct date is now inserted.
The lutserver server-side load may fail with a Not enough space error message even though there is plenty of space available. The error occurs when the load has a large number of updates to process.   The lutserver load no longer fails with an Not enough space error message when processing a large numbers of updates.
The Column Access Modifier Registry entry may not be triggered until a record is saved. The issue only arises if the column being monitored for changes is not one of the columns used for tab switching.   The Column Access Modifier Registry entry is always triggered when the column being monitored is exited after being modified.
The error message You cannot Edit no matching records in Column column with value 'value' may be displayed when using the Import tool to import data. The issue only arises for CSV based data where data is inserted into the same module twice. A typical scenario is importing a Bibliography record which in turn accesses another Bibliography record.   The error message is no longer displayed when importing data that accesses the same module twice.
The Bulk update tools provided on the Tools menu do not honour the Column Attach Registry entry. The affected tools are for Relocations, Condition Checks, Re-identification and Revaluation. If a Registry entry has been specified, invoking an attachment to the appropriate module results in the Registry entry being ignored.   The Column Attach Registry entry is now triggered when using attachments in any of the Bulk update tools.
The error message List Index out of bounds(0) may be displayed when importing data into a multi-lingual EMu system. The error only occurs when importing values into a hierarchy where one or more of the levels of the hierarchy is empty.   The error message is no longer displayed when importing data where one or more levels in a hierarchy is empty in a multi-lingual system.
If text is entered into a grid control in Query mode and the Insert Record speed button is selected before exiting the grid, an Access Violation error message may be displayed.   The error message no longer displays when clicking the Insert Record speed button.
If an Admin Task is defined in a multi-lingual system where strings are provided for all languages as part of the Registry entry, then the strings displayed show all languages rather than the current language selected.   The Admin Task now displays strings in the current language selected, rather than displaying all strings.
If a user has defined a different font colour for data when editing or creating a record and a value in a computed field is modified, the record will stay in Edit mode after the save command has been invoked. The issue only arises where a special handler has been installed to handle a computed value (e.g. Currency conversion).   The record no longer remains in Edit mode for computed fields when saved.
The ICS files generated by EMu may not contain the correct format. The ICS files contain a list of notification dates suitable for uploading into calendar applications like Microsoft Outlook, etc.   The ICS files generated now contain the correct format.
The lutserver server-side load may create a new Lookup List entry for Unicode based entries that already exist where the entry contains extended (or non-ASCII) characters. The entry created may not contain the correct data.   A new entry is no longer created when the Unicode based Lookup List entry exists, even if it contains extended characters.
The data displayed below the thumbnail image in Contact Sheet mode may appear incorrectly for Unicode based data where extended (or non-ASCII) characters are part of the data.   The correct data is now displayed for Unicode extended characters.
The lutserver server-side load may generate an error when checking whether a Lookup List value still exists. The Server error: Can't find "/home/emu/client/data/column" directory. Unable to resolve "column" error message only occurs where the hierarchy contains a virtual column. In this case the Lookup List entry should not check the column.   A Lookup List hierarchy containing a virtual column is no longer checked by the lutserver when determining whether an entry is still valid.
An Access Violation error message may be shown when clicking on the After Export tab in the Export Properties dialogue box. The issue only occurs if no After Export scripts have been installed.   The error message no longer appears when clicking on the After Export tab in the Export Properties dialogue box.
If a Lookup List field contains a value consisting of punctuation characters only, then when the record is saved the user will be asked to confirm the insertion of a new Lookup List even if the value is already in the Lookup List.   The confirmation message for Lookup List values which consist of punctuation only is displayed once, rather than each time the value is encountered.
An Access Violation error message may be shown when copying rows from List mode to the Windows clipboard. The message is only displayed if one of the columns copied is a client-side column (DataLocal column).   The error message is no longer displayed when copying rows to the Windows clipboard where one or more of the columns is a client-side column.
If a new value is entered into a Combo Box and the record saved, the value is added to the Lookup List module but it may not be added to the Combo Box drop down list. The next time the list is dropped down, the value may be missing.   New values are now added to the drop down list when the record is saved.
The emulutsrebuild server-side program may change the Hidden flag on a Lookup List entry from Y (Yes) to N (No) when rebuilding a Lookup List. The issue occurs only where the default Lookup List permissions for the column do not contain ReadIgnore, WriteIgnore or AutoWriteIgnore.   Lookup List entries with the Hidden flag set to Y (Yes) are no longer changed by the emulutsrebuild server-side program.
If a report contains a reverse reference field, under certain circumstances the data associated with the field may not be included in the report. The issue only arises if the data for the field is a single value. Multiple values are reported correctly.   The data for single value reverse reference fields is now reported correctly.
Error messages generated by the EMu server are not displayed correctly if the text contains extended (or non-ASCII) characters. In particular, French and Arabic errors may display incorrectly.   EMu server error message now display the correct text for all languages including text with extended characters.
The Overdue Loans notification reports, generated on a per user basis, may contain an incorrect list of the object on loan and the count of the object on loan. The issue only arises if the Extended Data for an object in the loan contains a closing bracket character.   The correct list of objects and count of objects is now reported in the Overdue Loans notification reports.
The Movements tab in the Locations module is designed to show all objects that have been moved through the current location. Under some circumstances the list of objects displayed may not be complete. The information regarding the movement is complete, however the Summary Data for the object may be missing.   The list of objects is now complete. An upgrade script is provided that forces empty Summary Data values to be populated correctly.
Under certain circumstances the last character in the Extended Data text may not be displayed as bold. The issue only occurs if the data contains more than one line of text.   All of the Extended Data text is now displayed in bold.
When copying data from List mode to the Windows clipboard and pasting it into Microsoft Excel using the Paste Special: CSV command, the pasted values may not appear in Excel.   Data pasted into Microsoft Excel via the Paste Special: CSV command now appears correctly. Due to limitations in Excel, Unicode based data may contain some question mark characters where Excel cannot map the character to its internal character set.
If a field has a Lookup List associated with it and also is an attachment field (e.g. it attaches to the Thesaurus module) and a value is entered into the field, then under certain circumstances the value entered may be cleared rather than force an attachment lookup. The issue only occurs if the value entered is not in the associated Lookup List.   The value is no longer cleared and the attachment lookup is now triggered correctly.
A System Error. Code: 1400. Invalid Window Handle error message may be displayed after a record is saved. The error only occurs if a default value is set on a Combo Box control that is only visible in Display mode (a very rare combination).   The error message is no longer displayed when saving a record.
If a drag and drop operation is used to add records to a grid control where the record has been changed by another user, then the record is refreshed and the drop operation removes the changes made by the previous user. The issue only occurs if the grid on which the drop operation is performed was modified by another user after the record was retrieved.   If a drop operation occurs on a grid that has been modified by another user, a message is displayed and the drop operation is aborted. The change ensures no data is lost.
Some currency based calculations may result in rounding errors. The issue only arises where the currency value is greater than seven digits of precision.   The rounding error no longer occurs where a currency value consists of more than seven digits of precision.
If data is copied from List mode and then pasted into Microsoft Word while keeping the source format, the data is no longer displayed in a table but rather as unformatted text.   If the Keep Source Format option is selected in Microsoft Word, the pasting data will now appear as a table rather than unformatted text.
The luts server-side audit handler generates an error when a name is not associated with a hierarchy. The error causes other audit handlers for the current audit record to be skipped. The issue only arises if a hierarchy has not been configured correctly.   An error is no longer generated if a hierarchy is not configured correctly. The hierarchy is skipped and all audit handlers are executed correctly.
An Admin Task may be executed inadvertently by displaying the list of available Admin Tasks and then double clicking anywhere in the Admin Task dialogue box. The issue only arises if a task is selected when the double click is executed.   An Admin Task is only executed if the double click occurs on the task selected, otherwise no action is taken.
If the emulutsrebuild server-side command is executed with a Lookup List name supplied as a command line argument and the lookup name matches an existing Lookup List name but the character case is different, then the Lookup List entries for the existing name are deleted.   The Lookup List entries are no longer deleted if the Lookup List name supplied does not match exactly the character case of an existing Lookup List.
When performing an attachment query the Searching dialogue box may display a status of Optimising Search that may never change. The only way to exit the dialogue box is to terminate EMu. The issue only occurs if an open module is displaying a grid that has custom functionality added to it. Normal grids do not exhibit this issue.   The attachment query no longer hangs when a grid containing custom functionality is displayed.
The Mandatory Modifier Registry entry may not be triggered when a dependent value changes in a nested column. The issue only occurs when the value to check is part of a nested column (a column name ending in _nesttab).   The Mandatory Modifier Registry entry is now triggered correctly for nested columns.
Under certain circumstances the value displayed in a query grid for an attachment query (e.g. <# 4 #>) may result is a search for the number of records (in this case 4) rather than the attached records. The issue only occurs if the cursor is placed in the query field after the attachment process is completed.   The attached records are always used as part of the query rather than the number of attached records.
Under certain circumstances the resolution height and width set on the Multimedia tab in the Report Properties dialogue box may not be honoured when the report is generated. The issue only arises if the Multimedia field is the last field listed in a report group.   The resolution height and width settings are honoured when the Multimedia field is the last field listed in a report group.
The Column Access Modifier and Mandatory Modifier Registry entries are not triggered when creating records using the EMu Record Template facility.   The Column Access Modifier and Mandatory Modifier Registry entries are now triggered correctly.
If a multi-page TIFF image is ingested by the Multimedia Repository, then the last page of the document is used to generate the thumbnail image rather than the first page. Since the last page may be a lower resolution image of the first page a blurry thumbnail may be produced.   The first page of a multi-page TIFF document is used to generate the thumbnail and resolution images.
The image types PDF and DNG are not recognised as image formats when producing a report with the Use first image only option enabled. As such, an image is not displayed in the report.   Both PDF and DNG are now recognised as image formats when generating reports.
The error message Can't find "/data/emu/client/data/AssParentObjectRef" directory. Unable to resolve "AssParentObjectRef". may occur when relocating objects using the Internal tab in the Movements module. The error displays when the New Location and Date Moved fields are updated and the movement is saved.   The error message no longer appears when the Movement record is saved.
The Summary tab in the Audit module may not display extended (or non-ASCII) Unicode characters correctly. Data stored as ISO-8859-1 (latin1) will be displayed correctly.   Unicode data is now displayed correctly on the Summary tab in the Audit module.
If a double click occurs on a row in List mode or on a cell in Contact Sheet mode and the mouse cursor is moved away from the row or cell clicked, under certain circumstances the record displayed in Details mode may not be the same as the record on which the click occurred.   The correct record is now displayed in Details mode based on the row or cell on which the double click occurred.

Upgrade Notes

See Upgrade 4.1 to 4.2 for details.