In DataSight, information is stored in nodes that help locate data to the exact second it was recorded. These nodes are called Levels.
Levels in DataSight are maintained in a hierarchical manner. Several lower levels combine to form a higher level. Before importing or entering data into DataSight database, it is important to decide on your Level 1, 2 and 3 node hierarchy. Level nodes are accessed and defined in the Levels Panel.
DataSight databases are configured in nodes consisting of:
|
Level 1 |
An appropriate Level 1 may be a geographic area, project name, client, catchment area, etc. |
Answering questions such as "what, how or why are you monitoring" |
|
Level 2 |
In the case of Level 2, a region within the geographic area, or type of data collected such as water quality data, weather station data, or a specific project under the Level 1 hierarchy. |
Answering questions such as "what, how or why are you monitoring" |
|
Level 3 |
The name or identification code relating to a particular monitoring site or location. For example, the monitoring station name. This Level is locked to the x,y,z properties or site locality in 3D. |
Answering questions such as "where your data set comes from" |
|
Date Levels |
Level 4 is automatically created by DataSight and is the year of a sample event. A sample event is an occurrence of sampling on a particular day, hence there is also a Level 5, which is the month of a sample event and is also automatically created; and a Level 6, for the exact date of the sample event and is also automatically created. Each sample event consists of a timestamp and data relating to each variable measured. |
Automatically created. See Time Dependent Levels. |
The DataSight Levels allow you to pre-filter your data according to broad groupings. This is helpful because:
This ability to quickly jump from one constructed filter to another is useful when visually comparing data, and when you perform relatively quick checks.
The decision on how to structure or group your data into Level 1 and 2 groupings often relates to an organisation's workflow. You may wish to interrogate these grouped data sets often during your daily work routine by simply clicking on them. However the list must also broadly communicate the relationships between your data set to anyone new to your database.
Whatever broad groupings you make for Level 1 and 2, you can still make Saved Views that allow finer groupings that are easily retrieved. You can use Saved Views to group and show data based on the type of variable monitored or specific methodology used.
While it is possible to identify a Level 3 as that other than a site locality, if you wish to undertake any spatial analysis of your data, then it is recommended that you choose to define the position of measurement of your field or sample data as a Level 3. Remember 3D = Level 3!
Most importantly, during your database setup, involve as many database stakeholders as possible, as you are then more likely to design a database structure that will survive the test of time.
See also: