Version 10 Highlights
February 2, 2024
“Clicker-type” Entry for Numeric Fields
The representation of numeric fields in web and mobile applications were extended to include a button to call “clicker” type dialog. Clicker dialog has two areas. Bigger area represented by the green “plus” button will increase the value of the property or result by 1 when tapped or clicked. The smaller area represented by the red “minus” button will decrease the value of the property or result by 1 when tapped or clicked.
Visualize Relationships
The new “Relations Path” concept is used to visualise relationships between objects in “Data Visualisation” application. Select “Directed Graph” chart type, pick Relations Path to use and starting object. The system will display a tree representation of relationships in the path. Different relationship are represented by different colours.
Relationships as Protocol Steps
Relationship types can now be added as protocol steps. When recording relationships using protocols users can record multiple related objects inside the same step. If multiple related objects were selected, the “Observation comments” information will be shared among all recorded relations.
Properties as Protocol Steps
Properties can now be added as protocol steps. Properties recorded using protocol will override the existing property value unless existing value was determined by another result recorded at a later date.
Calculated Properties and Results
There is a new Property and Result Type called “Formula”. These types of results and properties represent automatically calculated data entities. System will calculate values for such results and properties for all objects when property/result is created, or formula is updated. In addition, individual values will be re-calculated when properties or result types used in calculation have changed.
Object Tag Format Verification
It is possible to configure verification rules for tag types using regular expressions (PCRE). When defining a tag type users may specify multiple “Verification Rules”. The rules will be applied one by one to the tags being created. Tag must satisfy at least one verification rule to be accepted. If tag does not satisfy any rules, the tag will be rejected. When no rules are specified, all tags will be accepted.
Object Tag Format Verification
Not needed protocol steps must be marked as “Skipped”. Otherwise the system will demand an entry in the field.
Restrict Relationship Creation Based On The Relations Path
Relations paths can be used to restrict creation of relationships between objects. The restrictions can be configured as inclusive (Accept) or exclusive (Reject). If related object exists on the “Accept” path, the new relationship will be allowed. If related object exists on “Reject” path, the relationship will not be created and detailed error message will be displayed.
GPS Coordinates Are Not Mandatory For Static Object
It is possible to make GPS coordinates for static objects mandatory, optional or switch off them completely.
Inferred Relationships
When creating a relationship between objects, it is possible to create rules to infer additional relationship types which must be created when source object already has a specific relationship. For example, if two individuals are related as “mating pair” and “parent of” relationship is created for one of them to another individual, we might want another “parent of” relationship created from the second parent.
Relationships Marked As “Single”
The new flag “Only single occurrence is allowed” is introduced for relationship types. When set to “Yes”, system will not allow multiple occurrences of the relationship type to be created for an object. If, when creating a relationship, the relationship of the same type already exists on the source or destination object, the relationship will not be allowed, and error message will be presented.