|
The functions used to convert between imperial and metric units are, in many cases, built into specific clients. Each function is essentially the same with minor differences. The minor differences cause some conversions to compute an incorrect precision for the calculated value.
|
All conversion functions have been merged and checked to ensure the correct precision is implied for the calculated value.
|
|
When a conversion is applied between different units (e.g. feet to metres), the value entered by the user is flagged as the "Original" value. The flagging of the original value requires a number being placed in an Orig column indicating which field had the data entered. In some instances the Orig column may be shown as a text field when used in reports, rather than as an integer field.
|
All Orig fields have been updated to be integer based.
|
|
The Narrower Terms and Used For fields in the Thesaurus module do not have attachment buttons displayed, even though they are attachment fields. The buttons are missing from Query and Detail modes.
|
The attachment buttons have been enabled for Narrower Terms and Used For, in both Detail and Query modes.
|
|
If you enter a term into a Thesaurus controlled field that has the Thesaurus Validation Registry entry set to none, and the term entered appears in the Thesaurus, but not by itself (e.g. the term sports was entered, but only Sports Car exists in the Thesaurus), the term entered is cleared if you do not select a term. The current functionality makes it impossible to save a record with the original term as it is always cleared.
|
The term entered is no longer cleared if a term is not selected from the Thesaurus where the Validation Registry entry is set to none.
|
|
If a multi-term query is performed on an attachment field, where the field searched in the attached module has Also Search Registry entries associated with it, the query generated may not be the most efficient one possible.
|
The query generated for multi-term attachment queries where the attached column has Also Search Registry entries is now efficient.
|
|
For systems running in UTF-8 mode, the Audit Trail mechanism will drop audit records containing invalid UTF-8 characters. As the audit records are not posted to the Audit Trail table a "gap" may appear in the audit trail. The issue only occurs where invalid data is stored in a record (normally as a result of bad data when importing into EMu).
|
The Audit Trail mechanism now replaces invalid UTF-8 characters with the invalid UTF-8 character (0xFFFD). The substitution allows the audit record to be processed without error.
|
|
The View>Attachments command, used to show all records attached to the current record, displays modules the user does not have permission to use. While it is useful to see whether any records in the module attach to the current record, the module cannot be invoked without displaying a permission denied error.
|
The View>Attachments command has been modified to show only those modules the user has permission to access. A check box has been added to Show all modules, allowing the old behaviour to be selected.
|
|
If a Taxonomy record is re-parented to a name with a higher rank, the intervening ranks are not discarded from the Hierarchy tab.
|
Re-parenting now causes the intervening ranks to be removed from the Hierarchy tab.
|
|
An Access Violation message may be displayed when visiting the Hierarchy tab in the Narratives module. The message is displayed only if a hierarchy of narratives exists.
|
The message no longer appears when displaying the Hierarchy tab where a hierarchy of narratives exists.
|
|
When importing records into a Catalogue that uses the location SPLIT facility (used in parent records to indicate the child records are not all at the same location), spurious Internal Movements records may be created, even though none of the child records has been relocated. The spurious Internal Movements records note the location as unchanged.
|
Spurious Internal Movements records are no longer created when importing records into a Catalogue that uses the SPLIT location facility.
|
|
A Data validation failed on LatCentroidLongitude0 message may be displayed when calculating centroid values from decimal numbers. If converting the decimal value to degrees/minutes/seconds causes the seconds value to be close to 60, a rounding error may cause a value of 60 to be used. As this is not a legal value the error message is displayed.
|
When converting decimal values to degrees/minutes/seconds where the second value may result in 60, the minute value is incremented and the seconds reset to zero.
|
|
The mode displayed in the Module Title bar may be repeated when switching between display languages (e.g. English to Arabic).
|
The mode is no longer repeated when the display language is switched.
|
|
The emulutsupdate server-side script does not update Lookup List files in local/luts/default if it exists. Files in the luts/default directory are always updated. The issue means that localised versions of Lookup Lists may not be updated correctly by EMu upgrade scripts.
|
Local versions of Lookup List file are now updated by the emulutsupdate server-side command.
|
|
A number of the background loads used to synchronise data require the fifo load to be running when they are started. The emuload command does not check to ensure the fifo load is running before starting other background loads.
|
emuload checks the fifo load is running before starting any other background load. If the fifo load is not running, it is started, then any other loads listed are invoked.
|
|
If the Thesaurus module is opened in Browse mode, a term is selected in the tree, and then Details mode is chosen, the term record displayed may be read-only, even if the user has edit privileges.
|
The term record is now displayed with the correct permissions, rather than being read-only.
|
|
If the Thesaurus module is maximised or enlarged in Browse mode and the window splitter is moved to the right to increase the size of the terms tree, after which the module is returned to normal size, the fields on the Browse tab may disappear off the right hand edge of the page.
|
The fields on the Browse tab are displayed in the correct position when the Thesaurus module is re-sized.
|
|
If a second alternate term is added to a Thesaurus record, where the record was saved after the first alternate term was entered, an error message may display indicating non unique terms are present.
|
The Thesaurus record now saves without error when a second alternate term is entered.
|
|
If the Refresh tree option is selected in the Thesaurus module and the current record has Use and Use For terms, then the Use and Use For terms are repeated at the top of the Browse tree. The terms are repeated each time the Refresh option is invoked.
|
The Use and Use For terms are no longer repeated when the Refresh option is invoked.
|
|
An Access Violation message may be displayed when switching the display language in the Thesaurus module where the Browse tree is empty.
|
The message no longer appears when switching languages in the Thesaurus module with an empty Browse tree.
|
|
If a Narratives record may appear in two branches of a narratives hierarchy, the child narratives may not be shown for both branches of the hierarchy.
|
The child Narratives records are now displayed regardless of how may branches the parent narrative appears in.
|
|
The field prompts on the Permits query tab in the Rights module may not display correctly. The prompts are set to display using a right-to-left orientation, rather than the standard left-to-right setting.
|
The prompts have been changed to use a left-to-right orientation by default.
|
|
Data in reference fields, that is fields displaying data from another module, may not contain the correct values after certain operations are performed. The affected operations are:
- Discard Record
- Replace (Global Edit)
- Export Records
- Merge Record
- Sort
- Delete Record
|
Data in reference fields now displays the correct values after the listed operations are performed.
|
|
The value in a read-only combo-box may be cleared using the backspace key the first time data is viewed. The backspace key will not clear the value when viewing subsequent records.
|
The backspace key is disabled when a combo-box is read-only, regardless of when the data is viewed.
|
|
Duplicate attached records may be created when using the Import facility to create attached Collection Events or Sites records where the data contains lat/long values. The issue is caused by the failure of the lat/long conversion code when importing records.
|
The correct lat/long conversion now occurs, removing the creation of duplicate Collection Events or Sites records with the same data.
|
|
Random Access Violation messages may display indicating an error has occurred in mshtml.dll. The error message may even appear when a user is not at their machine.
|
The random error message is no longer displayed.
|
|
When performing a spell check on a RichEdit control that has multiple lines of text, the highlighting of the words spelt incorrectly may be out by a few characters.
|
Words spelt incorrectly are now highlighted correctly.
|
|
The View Attachments button next to a read-only grid may not be enabled when a single row is displayed in the gird. The button is only disabled for grids displaying data from another module (a reverse reference column).
|
The View Attachment button is now enabled when a single value is in a read-only grid.
|
|
The default value for the Gender field in the Parties module is set to Female. Ideally the default values should be Unknown.
|
The default value for the Gender field is now Unknown.
|
|
When changing the colours for various attributes (e.g. mandatory fields, etc.) via the Options dialogue box, the new colours selected will not take effect in modules already open. New instances will display the correct colours.
|
Existing modules now update their colours correctly when the Options dialogue box is closed.
|
|
When switching to the Details view of a record on a tab that contains an HTML control, the input focus is set to the HTML control, rather than the first control on tab.
|
The input focus is set to the first control on a tab when switching from Details view, even if the tab contains an HTML control.
|
|
A List of Values failure: fail to get values message may be displayed when generating a Crystal Report that contains dynamic parameters.
|
The error message is no longer displayed for Crystal Reports containing dynamic parameters.
|
|
The Audit Trail facility does not flush logging information when the processing of a record has been completed. The lack of flushing means the log file contents may lag behind the processing of records.
|
The Audit Trail facility now flushes logging information after each records processed.
|
|
If a taxonomic name appears in the Names History tab of other records it is difficult, if not impossible, to delete the name. Since the original name points to the preferred name, and the preferred name contains a history of previous names, a loop is formed. When a record is deleted it is not allowed to be referenced by any other record. A loop makes it impossible to delete either record, as it is referenced by the other record.
|
When deleting a taxonomic name, the Names History tab is now checked to ensure the original record is not referenced. This allows the record to be deleted.
|
|
The Taxonomy module has NULL indexing enabled on many of its fields. Unfortunately, this imposes a very large indexing overhead and as the indexing is enabled in the base module it cannot be disabled via the Registry.
|
All NULL indexing has been disabled in the Taxonomy module. System Administrators may enable it on selected fields via the EMu Registry. The indexing overhead for the Taxonomy module has been reduced dramatically.
|
|
The Taxonomy module does not generate the correct scientific name for autonyms.
|
The author is now inserted at the appropriate place in the sequence in the scientific name for autonyms.
|
|
The auto filling of values for the upper levels of hierarchies may be slow where the controls that form the hierarchy appear on a number of tabs.
|
The speed of auto filling of values in hierarchies has been improved dramatically.
|
IMu Web Framework: The IMu web framework provides a series of tools for distributing data held within EMu via the Intranet/Internet. IMu includes:
