Data Management
InfoAsset Manager is a workgroup based,
To facilitate both workgroup and standalone operation, InfoAsset Manager maintains data in a centralised, multi-user
Local working copies of parts of the data, (such as networks with changes that have not yet been committed), are stored in each users Local Working Folder.
Information that relates to the database, but is not stored in the database, such as ground model data, is stored in Remote Roots. The files containing this data can be very large so it is better to store them outside of the database.
Transportable databases are used to transfer information between databases.
See the File Locations topic for further details.
Managing database data
The
The top level of this hierarchical structure is the Asset Group. All data within the database must be contained in a Asset Group.
The Asset Group can contain the following:
- Other Asset Groups
- Version controlled items such as networks
- Non version controlled items such as selection lists
See Database Items for a full list of item types available in InfoAsset Manager.
The Asset Group is used to store all the data needed for managing network assets.
Data items of a particular type can be grouped together by storing them in Asset groups nested within the top level Asset Group.
Groups and items can be accessed and manipulated using a tree view. The Explorer window displays all the information about groups and items in the database. It can be docked at the side of the main InfoAsset Manager window so it is always visible.
See Working with Database Items and the other topics in the section for more details about working with groups and items.
Version control
The version control system maintains a complete and permanent record of all changes to your data. Version control supports multiple users editing the same network at the same time, and includes tools to resolve any conflicting changes that may occur.
Should errors be found in the data, you can track when the erroneous changes were made, and who made them. Branching is supported should you need to go back to an earlier version of a network and continue working from there.
See the Managing Version Controlled Items topic for more information.
