Organisation validation

Here is the list of validations running on a Organisation.

Validate that a certain date must be before the current date

Validate Dates

This validation ensures two things:

1. The endDate must be later than startDate;
2. The date format of endDate must be the same as startDate.

Validate the format of endDate and startDate

This validation is to ensure that the startDate and endDate formats match, for any blank node.

Validate dates and value items

This validation ensures that the number of items in value and dates are identical.

Validate blank node value between provided min and max

For any blank node, if the value is not between the min and max fields, an error will be given.

Validate blank node max is below provided min

For any blank node, if the max is not greater than the min field, an error will be given.

Validate blank node value between the lookup minimum and maximum

For some Terms, HESTIA has defined some minimum and maximum value. If the specified value does not fall within these, an error is raised.

Validate property value based on a lookup value

This validation checks if the property value provided is consistent with the value stored in a lookup table. For example, we can use the lookup region-liveAnimal-liveweightPerHead.csv file to determine if the liveweightPerHead value provided is within 75% of the high value contained in the lookup, for the country.

Validate duplicated nodes

This validation gives a warning when 2 identical nodes, with different id value`, are detected.

Validates the percentage of blank nodes

For all Terms that are in percentages, the value must be between 0 and 100.

Validate a group of blank nodes must sum to 100%

Some Terms are part of a group from the lookup sumIs100Group, meaning when summed up, their total value must be exactly 100% (with a 5% tolerance).

Validate the value of some blank nodes when the units is a percentage

For all Terms that are set as percentages, the value must be provided.

Validate the type of the value of blank nodes

Using the lookup "valueType", this validation will make sure the provided value is of the correct type. Example: a Term that should be either True or False will only accept True/False value.

Validate that some properties are specified for each blank nodes

Using the lookup recommendedPropertyTermIds on a blank node term, this validation will suggest the user to add any missing Property. These properties are necessary to run the models, and should be specified to prevent HESTIA from using default properties.

Validate that the region is not a Country

When using the region field, it must point to GADM Terms that are not countries. This can be identified with the gadmLevel field: it must be > 0 to be a region.

Validate that the region is within the country

When using both country and region, the region must be within the country specified.

Validate that the country is a Country

When using the country field, it must point to GADM Terms that are countries. This can be identified with the gadmLevel field: it must be == 0 to be a country.

Validate the coordinates are within the region or country

When providing longitude and latitude, the coordinates must fall within the region or country provided.

Validate area based on boundary

HESTIA will calculate the boundary area during upload, and this validation will show a warning when the area does not match. Please verify that the area provided is correct and in the correct unit.

Validate max boundary size

HESTIA will only gap-fill data from Geospatial datasets when the site area is less than 5000km2. If you see this warning, it means the calculation will be incomplete, and the measurements will need to be manually provided. Please provide a smaller polygon instead.

Validate max region/country size

HESTIA will only gap-fill data from Geospatial datasets when the site area is less than 5000km2. If you see this warning, it means the calculation will be incomplete, and the measurements will need to be manually provided. Please provide a smaller region/country instead.

Validates empty fields

This validation returns warnings when fields are added without a value (or using 'no data' for example).

Validate the privacy of 2 linked Nodes

When adding a Source to a Cycle or an ImpactAssessment, this validation ensures that the same level of privacy is used on both.

Example:

• if the Cycle is set as dataPrivate=true, the Source it is linked to must also be dataPrivate=true;
• if the Cycle is set as dataPrivate=false, the Source it is linked to must also be dataPrivate=false.

Validate private nodes are linked to a Source

It is recommended to always link a Cycle, Site, or ImpactAssessment, to a Source, even when private.

Validate a blank node value based on HESTIA's model

This validation will use the models library to recalculate the value of a blank node, and will give an error when the value too different from the models value. Note: the default tolerance is 5%, but we use the lookup valueToleranceToHestiaRecalculatedValue when available.

Validate multiple terms used with different units

Some of the terms in the Glossary have been added with different units, e.g., kg / kg N / kg VS. This validation returns a warning when those terms have been used together in the same Node.

Validate usage of "Other model"

The "Other model" Term has been added in the eventuality that HESTIA has not added the required model yet. However, to use this Term, the methodModelDescription must be set.

Validate when a non-indexed node references indexed nodes

When uploading Cycle, Site, etc., the referenced nodes must also be uploaded. Example:

• if the uploaded Cycle references an existing Site, a warning will be given;
• if the uploaded Cycle references an uploaded Site, no warning is given.