Article Index

The following features have been added or modified since the last major version of Max:

  • Fauna Names
    The new version of Max includes fauna names. In collaboration with the WA Museum and DEC's Species and Communities Branch, we are now able to provide WA vertebrate fauna with unique NameIDs as we do with flora. This ensures there will be no clash in combining flora and fauna data because all IDs are issued from the one number pool.

    By default all new databases use default master lists containing flora and fauna names. (For backwards compatibility, views containing just flora names are also implemented.) This means both flora and fauna names will appear in dropdown lists when adding new names. This is a new addition to Max and support for the new names is still limited. For example, Max will still only implement a flora collecting book. New fauna collecting books may be included in upcoming versions. A later version will include also filtering so that you only see the groups you want when adding records.

  • Family number is now deprecated
    Family number (e.g. 106A, field FAMILY_CODE) has been deprecated. FAMILY_CODE will be retained in the families table for backward compatibility, but will no longer be updated, and will be blank for new families. At a future date the field will be removed.

    Max is designed to support data standards implemented by the WA Herbarium. One recent change, as part of the move to the new Herbarium building, is the system used to identify and physically locate families. For many years family number (field FAMILY_CODE) has been used to uniquely identify families and has been cited in the literature. This field was also used to systematically sort families. However, since the implementation of NAME_IDs at all levels of the taxonomic hierarchy, family number has been effectively duplicating this function.

    As of Max Version 3.2 the identification and sorting functions have been separated. Families are now solely identified by NAME_ID. This field has been added to the families master list. In the species and genera master lists, the field is called FAMILY_NID to avoid clashing with the NAME_ID already in that table. Thus, you can make a join between the species and family lists by using FAMILY_NID (species or genera list) <-> NAME_ID (families list).

    To facilitate systematic sorting, a new field LINEAR_SEQUENCE now exists in the families table. All Max reports incorporating family information now use LINEAR_SEQUENCE for sorting. The contents of this field have no inherent meaning and are used solely as a sorting mechanism. The number itself is not guaranteed to remain the same and should not be cited.

  • Families table now includes higher order information
    The WA Herbarium now maintains higher order names for many taxa, from class through to kingdom. This information is now included in the families table in a simplified form, together with the NAME_IDs for each taxon name. Note that gaps exist for many names. These will be filled over time.

  • Genera table added to Max's master lists
    The Max master lists now include genus names.

  • GenusID is deprecated
    The field GENUS_ID in the species table has been historically used to uniquely identify genera. For reasons similar to family names, this field is now deprecated. Every genus has a unique NAME_ID and there is no need for the GENUS_ID field. It will be dropped in a future release of Max.