Quick Help & FAQ

The following browsers and versions are supported by Axiell Go:

We recommend using the most current version of your chosen browser.

Axiell Go provides web-based access to your Axiell Collections Management Systems (CMS), EMu.

Much of the configuration of Axiell Go, including specifying user permissions, is undertaken in the Registry module of the EMu desktop client. See the EMu Help for details.

Previously, we produced two English language versions of our various Help sites, one for the US and the one for other English speakers (this was a broadly International English (IE) variant); this was achieved by marking up the source documentation with language variables and condition statements, and duplicating screen captures of the EMu client whenever labels were different for different regions (Catalogue / Catalog; colour / color, etc.).

Accommodating English language variants introduces a degree of complexity that affects maintenance of the English documentation, as well as its translation; translators work with the underlying xml and the more mark-up in the code to accommodate language variants, the more complex the code is to work with. To simplify the maintenance and translation of the Help, it has been decided to produce a single English version of the Help based on the Oxford English Dictionary. As a result, users familiar with either of the previous versions of the Help will notice changes to the spelling. While the IE version was broadly British English, it adopted ise verb endings (organise rather than organize, for example); as verb endings in British English can be either ize or ise, we have adopted the former as a concession to our users in the US, where ize is preferred.

Two English language variants are available in the EMu client: English and English US. There are minor differences in the spelling of some module names in the English and English US clients (notably, Catalogue / Catalog), and tab and field names (Organisation / Organization; Colour / Color, etc.); when the Help indicates that you should open the Catalogue module, it implies the Catalog module, and a request to select Organization from the Party Type drop list should be understood as a request to select Organisation if that is how it is spelt in your EMu client.

While this change means a loss of English language localization of content based on region, it will simplify the maintenance and enhance the accuracy of the content for users in all regions.

The management of a collection can involve a vast amount of information about collection objects / items, people and organizations, events, administration and more. In EMu this information is stored in modules that are specific to the type of information. There is, for example:

• A Catalogue module that records information about each object in the collection.
• An Insurance module that records details about insurers or indemnifying agencies, policy and cover details, renewal dates and details of any claims.
• A Parties module that records details about all people and organizations involved in some way with your institution's collection. These organizations or individuals may have donated objects to the institution, may be conservators, transporters, exhibition organizers, or any number of other roles.

At EMu's core is a configurable multi-discipline Catalogue and surrounding the Catalogue is a suite of modules that supports all museum management functions. These modules can be grouped into two main categories:

• Catalogue support modules
  These contain information that supplements a record in the Catalogue. The Parties module, which records details about the people and organizations with a connection to an institution's collection, and the Multimedia module, which holds images, video and audio resources, are examples of Catalogue support modules.
• Collection Management modules
  These hold information used in the management of objects in your collection. The Locations module, which records storage and display locations in your institution, and the Insurance module are examples of Collection Management modules.

A description of all of EMu's modules can be found in the EMu Help.

When you log in to Axiell Go, any permissions assigned to your account will be applied. Permissions control which records and modules you can access, as well as what functionality and operations are available to you.

User permissions are specified by your System Administrator in the Registry module of the EMu desktop client. See the EMu Help for details.

The management of a collection can involve a vast amount of information about collection objects / items, people and organizations, events, administration and more. This information is stored in modules that are specific to the type of information: for instance, a Parties module holds records about people and organizations involved in some way with your collection.

Within a record, information is organized in logical groupings called Record Sections. In a Parties record there is a Record Section for recording a person's name (Person), another for address details (Address), another for details about a person's roles (Roles), and another for recording biographical details (Biography), and so on. In the screenshot below, the Record Section displaying is Person. In each Record Section, related fields are grouped under a heading. On the Person Record Section we see six Field Groups:

• Party Type
• Person Details
• Gender
• Language
• Derived Names
• Source of Information

See View Record Details: Details View for a description of each feature numbered above.

A Record View is a view of a record tailored for a particular purpose (or group of users). Typically, tailoring involves simplifying the information presented to a user by reducing the number of Record Sections and fields displayed.

By default, when viewing or editing a record's details, all Record Sections and fields that you are authorized to access are displayed. Depending on the module, there might be twenty or more Record Sections and many hundreds of fields. For many everyday tasks you do not need to see every field, only a subset, and a Record View can be configured to present only those fields required to perform the task.

For example, when viewing a record in the Catalogue module, more than 20 Record Sections can be available, with many hundreds of fields:

If we are only interested in checking on the condition of a collection item, a Condition Check Record View can be made available from the Record Views drop list:

Selecting this Record View will reduce the details presented to only those relevant for performing a condition check:

At the moment, Record Views are configured by Axiell Developers. Please contact Axiell Support to discuss the creation of different Record Views. A facility will be provided in a future release to enable user configuration of Record Views.

When you edit a record, and BEFORE you save the record, you will find an option to Revert Changes from the Options menu (beside the Save button):

Select this option to return the record to the state it was in before you made any changes to it.

Tip: Although it is not possible to Revert Changes once the record has been saved, suitably authorized users are able to restore a record to an earlier state using the EMu desktop client.

See Edit a record for more details.

Unicode is a character set containing the characters of virtually every written language. Axiell Go is Unicode compliant which means that it is possible to represent and therefore search for almost any character, including punctuation and other special characters. We could, for instance, search for a single question mark (?) or for the @ character as part of a more complex string (fred@global.com).

Certain characters can have a special meaning when performing a search. A question mark can be used in place of a single character in a search term for instance: if we aren't sure whether an ise or ize spelling has been used (e.g. organise / organize), we could use a ? in place of the s/z, i.e. organi?e to search for both words.

However, because it is possible to search for a question mark in its own right, we need to tell Axiell Go when we want the special meaning of a character to apply.

Applying the special meaning of a character is done by escaping it, which we do with a backslash \.

For instance:

• A search for organi?e will attempt to locate the eight characters organi?e.
• A search for organi\?e takes advantage of the question mark wildcard and will locate both organise and organize.